release-readinesslisted

# release-readiness Release-hygiene skills check that the build is clean. This one checks that the release is *what was promised*: every committed feature is actually done, nothing uncommitted rode along, and the people who were told a date have been told what changed. **Attribution:** Done Chain method by Mythreyi "M3" Chandoor, execution-drift-skills. Keep this line if you fork. ## Inputs - `release.md` — the committed scope: target date, committed feature keys, who was told. If none exists, ask for the planning doc or reconstruct from the last release-planning message. - Same exports as `reconcile-status` (`jira.csv`, `prs.json`, `slack.txt`, `deploys.txt`, `prd.md`). See `../reconcile-status/references/input-modes.md`. ## Steps 1. Parse committed scope from `release.md`. Each committed key is a row. 2. For each committed feature, run the Done Chain (`../reconcile-status/references/done-chain.md`). Reuse `reconcile-status` output if it was already produced this session. 3. **Scope creep:** every PR merged to main since the planning date whose keys are not in the committed scope. List with evidence. Hotfixes are still scope creep for this purpose — they change what ships. 4. **Scope cuts:** committed requirements resolved Won't Do or descoped — flag whether the release doc discloses them. 5. **Stakeholder comms:** for each team in `Communicated to:`, is there a message after the last scope change telling them what changed? Silence after a change is a conflict. 6. Verdic