po-acceptancelisted

## Inputs - `mode` — one of `demo` | `uat` (required, passed by the SM in the `PO_DECISION_REQUEST` envelope). - `<sprint-id>` — current sprint id (from `.scrum/sprint.json.id`). - **demo mode:** - List of completed PBI ids for this Sprint (from `.scrum/sprint.json.developers[].current_pbi` plus `.scrum/backlog.json` items with `status == done` and `sprint_id == <sprint-id>`). - For each PBI: `acceptance_criteria` array from `.scrum/backlog.json.items[]`. AC ids are **1-based positional indices** into that array (AC #1 = first element). - **uat mode:** - `docs/requirements.md` — the FR/NFR set from which user stories are exhaustively derived (every release-relevant Functional Requirement traces to ≥1 user story). - `docs/product/vision.md` release-criteria section (cross-check; the brief is the fallback when vision.md is absent). A release criterion with no covering story → add a story before the walkthrough. - `.scrum/test-results.json` from the latest `smoke-test` + `integration-tests` runs (precondition: combined `overall_status ∈ {passed, passed_with_skips}`). ## Outputs - **demo mode:** one transcript per PBI at `.scrum/po/acceptance/<sprint-id>/<pbi-id>.md`. One `kind=demo_acceptance` decision per PBI in `.scrum/po/decisions.json` (recorded via `.scrum/scripts/append-po-decision.sh`), with `evidence` pointing to the transcript path. - **uat mode:** - User-story inventory at `.scrum/po/uat-stories