Week 3: Human needs-revision flow and feedback history

[Abiorh001]

Parent: #29

Why

Checker-caused needs_revision already exists as outcome_source = auto_checker. Week 3 must add human-review needs_revision with review decision provenance and clear feedback history.

Roadmap Source

• docs/spec_week2_checker_framework.md User-Facing Outcome Boundary
• docs/roadmap_day_by_day_execution_plan.md Day 13
• docs/operations_reviewer_workflow.md

Scope

• Implement review_pending -> needs_revision from human review.
• Store outcome_source = human_review, review_decision_id, and finding history.
• Unlock or prepare the task for worker revision according to revision policy.
• Ensure checker-caused and human-review revision stay distinct internally while sharing user-facing language.

Acceptance Criteria

• Human needs-revision creates a review decision record.
• Worker can retrieve prior findings and required fixes.
• Worker cannot resubmit without required revision replay once replay is implemented.
• Tests prove auto-checker revision and human-review revision provenance differ.

Contributor Fit

Good follow-on task after structured review decisions land.