Week 3: Revision replay and context rebase enforcement

[Abiorh001]

Parent: #29

Why

Revision replay is the system memory for resubmissions. The roadmap says every prior high/medium finding must map to a fix, dispute, or not-applicable claim before review can continue.

Roadmap Source

• docs/operations_revision_replay.md
• docs/product_first_user_flows.md Flow 6
• docs/roadmap_day_by_day_execution_plan.md Day 14
• docs/risk_register.md R1A and R4

Scope

• Add RevisionReplay and RevisionFix persistence.
• Require replay rows for prior high/medium findings.
• Include worker claim status: fixed, disputed, not_applicable.
• Include reviewer closure status: closed_fixed, closed_rebutted, partially_closed, still_open, obsolete.
• Prepare revision context when guide/policy versions changed according to revision policy.

Acceptance Criteria

• Resubmission is blocked if required prior findings lack replay rows.
• Worker and reviewer packets show prior context, next context, and rebase reason when applicable.
• Reviewer can mark closure status per finding.
• Tests cover missing replay, disputed finding, closed finding, and stale/hidden-rule prevention.

Contributor Fit

High-value backend/research task. It directly addresses the Workstream emphasis on reliable contribution proof.