references/release-evidence.md

# Engineering release handoff

Record code diff/commit, changed contracts, schema/runtime requirements, test output, build artifact checks, deployment preconditions, monitoring, rollback/forward fix and outstanding risks.

Release readiness is separate from implementation. A green unit test alone doesn't prove production safety. Mark incomplete or unexecuted checks clearly. Production deployment, merge, publish, payment, destructive schema changes and external notifications need explicit user authorization and available tools.

For feature flags and staged rollout, specify enable/disable action, health signals, gates and owners if known. Avoid asserting that changes are live when they were only built locally.