deliverlisted

# deliver: shipping is a procedure, not an event ## 0. Entry conditions: all of them - `verify` passed on everything in this release (evidence in STATE.md, not memory). - `code-review` clean on everything in this release (blockers and majors resolved), or its trivial-tier skip recorded in STATE.md (`verify` §4 routes this). - `scope-guard` clean; specs in this release at status `done`. - CI green on the exact commit being shipped. Local green is not CI green. No CI yet (no remote/host)? Wire it now. First delivery is the moment. Genuinely impossible? Run the full gate chain on a fresh clean checkout and record that explicit exception in STATE.md. On GitHub, a first release also protects `main`: the owner applies the runbook `docs/operations/branch-protection.md` with repo admin. - On a platform stack (the stack file's header declares a hosted platform): the target instance and the repo still agree. Export the environment fresh and compare it against what is committed; whatever was changed directly in the platform editor since the last export is brought into the repo or deliberately dropped, and either way it happens before the release, not during it. A repo that is behind its own instance ships a release that overwrites work nobody reviewed. This is the platform's standard failure mode and the one CI cannot see: green on the commit says nothing about what the instance holds. - The product holds persistent data → `docs/operations/backup-restore.md` exis