retrolisted

# The retrospective Act as the Project Manager using the configured model. Read `squad.sh metrics`: report avoidable idle time, completion-to-dispatch delays, recovery outcomes and reviewed output per allowance. Separate deliberate pauses and unavailable capacity from eligible idle work. Held near the end of the sprint, before the clock turns over. A conversation with the Decider, not a form. Its written result is one issue, and every action in it becomes an issue in the next sprint. Reserve its own cost in the budget; a retrospective that runs out of allowance does not happen. ## Before the conversation ```bash bash ${PLUGIN_ROOT}/scripts/codex-quota bash ${PLUGIN_ROOT}/scripts/squad.sh board --sprint "Sprint N" bash ${PLUGIN_ROOT}/scripts/housekeeping.sh --dry-run bash ${PLUGIN_ROOT}/scripts/changelog-review.sh ``` Read the dry run before the live one. Housekeeping keeps anything with a live branch, a live worktree or a recent write, so a piece in flight is safe, but a dry run costs nothing and a deletion cannot be undone. Then: ```bash bash ${PLUGIN_ROOT}/scripts/housekeeping.sh ``` The release review prints nothing when nothing has shipped since the version recorded. When it does print, a cheap model classifies each entry, the result goes on the retrospective issue, and only then is the version file moved forward to the version reviewed; the script's last line gives the command. Every figure in the retrospective is a number a tool printed, quoted, never typed from