Publish Checklist — refactor-chain · ship

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: ship · Prerequisite: review gate passed + docs phase done (write-up, artifacts-sync) · Next: refactor-ship. Adaptivity / conditional: repo-agnostic. Read-only verification. It checks conditional items (data-guard, telemetry-plan, security) only if those guards fired during the run.

Purpose

This is the last gate before a refactor leaves your hands. It doesn't do new work — it confirms that the work already claimed to be done actually is. It walks a fixed checklist: the review gate passed, the baseline is green, the write-up exists, the durable docs are current, every conditional guard that fired has been resolved, and there's no stale intent (a rolled-back step never redone, an open decision, a TODO the chain left behind). It ends with a single, honest verdict — GO or NO-GO with the exact blockers — so nothing ships half-finished.

When to use

• The docs phase is complete and you're about to hand off / open a PR / merge.
• Someone asks "are we ready to ship?", "did we finish everything?", "go/no-go?".
• The orchestrator reaches the ship phase and needs the pre-flight check before refactor-ship.
• Any time you want an honest "is this actually done?" audit of a run.