retrospectivelisted

## Inputs - state.json → phase: sprint_review - improvements.json (existing improvements + last_consolidation_sprint) - sprint.json (Sprint id) ## Outputs - improvements.json → entries[] appended; every 3 Sprints the consolidation pass archives stale entries (see Step 4) - state.json → phase: retrospective - sprint.json → status: "complete" - `.scrum/framework-issues/<sprint-id>-NN.md` (+ `.meta` sidecar) — only when Step 4b fires; the `.md` is the postable body and nothing is published without a human's explicit permission ## Preconditions - state.json phase: "sprint_review" - sprint.json exists ## PO Mode (po_mode: "agent") When `.scrum/config.json.po_mode == "agent"`, every PO-approval prompt below re-targets to the `product-owner` teammate per `../../rules/scrum-context.md` § PO seat resolution; the ceremony shape is unchanged. Skill-specific: with no human at the keyboard, the Step 7 "recommend `/clear` or session restart to the user" line cannot be acted on by anyone in-session (human mode keeps that recommendation bit-for-bit). Overrides in agent mode: - **Sprint-continuation handshake (replaces Step 7).** Skip the user-facing `/clear` recommendation. The retrospective is **not** the end of the workflow — leaving `state.json.phase` at `retrospective` is a dead end: nothing advances it, and the autonomy watchdog reads an unchanged phase as `no_progress` and trips the failure circuit breaker. After the retrospective Exit Criteria are met, the S