Add critical cell reparse comparison review

docs/player_gm_ux_redesign_plan.md

@@ -507,6 +507,7 @@ The following groundwork is already implemented in the web app as of March 15, 2
 - the critical table browser is framed for play use rather than import administration
 - critical cells support re-parse from shared parser logic
 - advanced diagnostics have been separated from the primary editing flow
+- advanced curation now includes a generated-versus-current comparison view for re-parse review
 
 These changes are real and complete, but they are no longer the active roadmap because the detailed acceptance checklist still has unfinished items.
 
@@ -575,6 +576,17 @@ Acceptance criteria:
 
 ### Phase 4: Compare and review workflow
 
+Status:
+
+- implemented in the web app on March 15, 2026
+
+Implemented model:
+
+- re-parse now returns the freshly generated parser output alongside the merged editor state
+- the editor captures the pre-reparse card as a review baseline before applying the merged state
+- advanced curation shows side-by-side cards for the prior edit, the fresh generated parse, and the merged post-reparse result when available
+- diff summary chips call out result-text, base-effect, and condition changes without requiring raw JSON inspection
+
 Scope:
 
 - add a clear comparison surface for generated result versus current edited result
@@ -641,4 +653,4 @@ Mitigation:
 
 ## Recommended Next Step
 
-Implement the new Phase 3 next. The remaining structural gap is generated-versus-overridden state, so re-parse and future import refreshes can preserve intentional curation instead of treating all edited values the same.
+Implement Phase 5 next. The remaining cleanup is to tighten the boundary between compact curation tools and engineering diagnostics so ordinary correction workflows stay user-facing while deeper diagnostics remain available behind an explicit advanced surface.