sprint-updatelisted

# Sprint Document Update Update the sprint doc at `docs/plans/<date>_Sprint.md` (or the most recent sprint file). ## Sprint doc structure The sprint doc uses **per-persona queues** (not wave tables). Each persona (Alice, Bob, Cindy, Dan, Elsa) has their own section with three tables: ```markdown ## <Persona> — <Domain> ### Active | Status | Issue | Repo | Description | Handoff | ### Queue | # | Priority | Issue | Repo | Description | ### Completed | Issue | Repo | PR | SHA | Wave | ``` ## What to update ### 1. Move merged items: Active → Completed When a PR merges, move its row from the persona's **Active** table to **Completed**: ```markdown ### Completed | Issue | Repo | PR | SHA | Wave | |-------|------|----|-----|------| | ~~#NNN~~ | repo | #PR | sha7 | — | ``` Get merge SHAs: ```bash gh pr view <num> --repo wrfcoin/<repo> --json mergeCommit --jq '.mergeCommit.oid' ``` ### 2. Promote next queue item: Queue → Active After clearing an Active slot, move the top Queue item to Active with status `next`: ```markdown ### Active | Status | Issue | Repo | Description | Handoff | |--------|-------|------|-------------|---------| | next | #NNN | core4 | Description | [handoff](path.md) | ``` Re-number the remaining Queue rows starting from 1. ### 3. Header counts Update the top-line counts: - Total PRs merged - Open PRs (check all repos) - Approximate open issues ### 4. Velocity table Update the sprint row with new PR count and key milestones. ### 5. Launch read