Release Readiness

Repo-Pack GA means the flow mechanism is safe to install into other repositories, not only usable inside this source repository.

This playbook is for the source repository that publishes the repo pack. Installed-binary consumer repositories do not need to vendor top-level tools/** or flow/live-sandbox*.yml.

Current GA Status

As of April 25, 2026, Repo-Pack GA readiness is evidence-driven: the current release evidence is green only when the latest local release check and latest canonical live sandbox proof pass on the current source HEAD with the first-class repo-pack bootstrap path.

• Current required local gate: tools/flow-release-check; use .salp/flow/tmp/release-check/latest.json for the latest recorded verdict.
• Machine-checkable HEAD-bound readiness: flow manage release-status --json.
• Current blocker inside that gate: none known.
• Current canonical live proof verdict: follow the latest canonical entry in .salp/flow/tmp/live-sandbox/index.json; any verdict other than pass keeps GA blocked, with component details in .salp/flow/tmp/live-sandbox/latest.md.
• Freshness gate after any release-affecting change: rerun tools/flow-live-sandbox-check --config flow/live-sandbox.yml.
• Current proof index: .salp/flow/tmp/live-sandbox/index.json
• tools/flow-live-sandbox-check --config flow/live-sandbox.mock.yml and tools/flow-live-sandbox-check --config flow/live-sandbox.codex.yml remain support signals only and do not satisfy the GA proof requirement.

Update this dated status block whenever the local release gate, current blocker, canonical live proof source, or proof index changes.

GA Scorecard

• Local-only checks: required
• Live GitHub-backed proof: required
• Repo-Pack GA: only when both are complete

Check	What it proves	Status needed for GA
tools/flow-release-check	Local code, packaging, and consumer-smoke validation	Pass
tools/flow-live-sandbox-check --config flow/live-sandbox.mock.yml	Optional zero-cost confidence on the compound runner model	Support signal only
tools/flow-live-sandbox-check --config flow/live-sandbox.codex.yml	Optional Codex parity signal on the GitHub-visible slice	Support signal only
tools/flow-live-sandbox-check --config flow/live-sandbox.yml	Canonical compound fresh proof on the disposable sandbox repo	Pass every required component in one run

Local-only green is not enough. The only GA-grade live proof is the canonical compound sample described in flow/playbooks/live-sandbox-validation.md when it passes under flow/live-sandbox.yml.

Repeatable Local-Only Check

Run:

tools/flow-release-check

That procedure always stops at local code, packaging, and consumer-smoke validation. It is necessary, but it is not the live GA gate.

Next Required GA Step

After tools/flow-release-check passes, the next required step is the canonical live sandbox gate:

tools/flow-live-sandbox-check --config flow/live-sandbox.yml

Do not call the flow production-ready until the canonical sandbox evidence covers the full compound sample:

• flow-not-configured bootstrap
• installed repo-pack bootstrap
• local-private task lifecycle
• worktree happy path
• blocked commit before local review
• successful commit after local review
• blocked push before fresh second review
• successful push after the second review
• local strict acceptance and finalize
• GitHub-visible issue and branch lifecycle
• PR creation and binding
• actionable remote review, repair, rereview, and clean follow-up
• strict PR acceptance and finalize
• merge and pr reconcile --strict

Current Interpretation

• tools/flow-release-check protects local code and repo-pack portability.
• tools/flow-release-check also verifies the tracked support policy is present and freshly reviewed before the repo pack is considered locally releasable.
• tools/flow-live-sandbox-check --config flow/live-sandbox.yml proves the bounded end-to-end sandbox lifecycle only when all required components pass in one run and the proof is recorded in .salp/flow/tmp/live-sandbox/index.json.
• The mock and Codex tiers remain non-blocking support signals.
• When either the local-only gate or the canonical live proof is unresolved, the correct answer is “not Repo-Pack GA yet.”