Roam Release Readiness

Roam release readiness

Determine what can advance, what remains unverified, and the next authorized operation for each requested surface. A readiness review is not publication; publication on one surface is not evidence for the others.

Bind the candidate and authority

Read current AGENTS.md, docs/repository-maintenance.md, and the relevant release owner: docs/releases.md for packages or docs/website-maintenance.md for Pages. Read docs/containers.md only when an image is requested, and docs/concepts/verification-evidence.md when assessing proof bundles, verdicts or review receipts. Use internal/EXECUTION-SEQUENCE.md for the active cursor when present; otherwise consult internal/INDEX.md and existing release-driver phase records without inventing a replacement board. Missing private context is a named limit, not an automatic veto of sufficient public release evidence. Treat earlier artifacts as dated context, not live facts. Follow the user's specific scope; a skill does not grant release approvals or alter policies.

Inventory HEAD/upstream, staged and unstaged changes, untracked files, relevant worktrees/stashes and remote/server state before synchronization or cleanup. Record exact identities and preserve unique work. A clean branch relationship does not prove a worktree or server is clean. Stage only reviewed explicit paths; never absorb unrelated edits, rewrite published history or move a release tag. For index-only executable-bit changes, follow AGENTS.md's Windows commit-pathspec exception and verify the staged set and resulting commit, not just command success.

Distinguish candidate contents, installed editable version, release tag, registry artifact, CI commit, review subject, server revision and Pages deployment. Check current state when a decision depends on it. Keep a compact per-surface record linking required evidence to its exact source and operation; do not reduce these identities to one green label.

Qualify the change that will actually land

Derive checks from the complete candidate, not the last small edit or commit message. Include relevant untracked files in the review packet and test scope. The venv roam --json verification-contract --files-from <list> can suggest obligations; inspect current help, its inspected denominator and skips. It does not replace the project release rules or expert review of the diff.

FAST/FULL structural gates are not the release-sized suite. An accumulated release-sized batch needs scripts/prepush_check.py --release with a bounded worker budget in the locked venv. Read that run's actual coverage note rather than copying a stale list of unproven CI lanes. Capture start, command, selected scope, final exit and test outcomes. For long runs use a durable runner supported by the host with an explicit completion marker; a launched or abandoned process is pending, not green. Avoid concurrent heavy gates on a constrained workstation.

Bind independent review to the same artifact and requested model/effort when specified. A prompt, dispatch, tool-read count or schema-valid receipt is not a completed review. Preserve actual output, identity evidence and every finding's disposition. Editorial review does not approve runtime changes. Changed bytes need appropriate requalification; do not relabel an earlier verdict or accept residual risk on the owner's behalf. Skips and missing baselines stay explicit.

For material product-copy changes, record factual support, product-meaning review and owner acceptance separately from technical gates. Tests and browser checks cannot establish that the page communicates the intended product. Recheck current owner direction: an unresolved positioning objection is not superseded by a prior editorial label or a green suite. Keep the affected publication pending while advancing independent qualification; do not invent a new approval gate for typos.

Require the normal local gates before push and required CI on the exact pushed commit before tagging or production deployment. Local success does not predict all CI lanes. Do not bypass a failed gate or approve a protected older release just because the user wants the current website live.