Prepare a release

Know what is verified locally and what a real release still needs.

Accept a release with evidence

Record the revision, environment and executed cases. Stale evidence or an untested recovery path leaves release requirements unmet. This exercise produces a decision; it does not deploy.

An intact box does not prove the correct item is inside.

Read the CLI result correctly

Process status, JSON envelope and review content are separate checks. Verify the revision and evidence too; a missing issues field does not mean zero issues.

An intact package does not prove the correct item is inside.

Practice

Prepare a local candidate report without deploying.

Read lab code/tests and write only release-note.md. Record actual commands/results, exercised UI, missing evidence, stop signals and a proposed rollback. Do not deploy, configure cloud services or claim production readiness.

Check your work

Evidence identifies the tested candidate.

Production gaps are explicit; nothing was deployed.

References