BT6 Release Readiness
Prepare a release candidate after normal pull requests have passed the bounded
validation.quick contributor gate. Apply bt6-maintainer-guardrails. This
workflow may improve code, tests, documentation, and repository-owned release
policy when the operator authorizes implementation. It does not create or
promote a tag.
Required context
- Resolve the canonical repository, base branch, CI remote, profile, candidate
commit, comparison base, and current authorization.
- Require a clean or explicitly understood working tree. Preserve unrelated
work and use an isolated checkout when validation could overwrite it.
- Inventory merged changes since the previous release or configured comparison
base. Map production changes to behavior tests, ownership, and risk surfaces.
- Treat PR acceptance as evidence of reviewability only. Do not infer release
readiness from quick checks, aggregate coverage, or merge status.
Hardening loop
- Run
validation.full plus applicable documentation, research-integrity,
risk-surface, packaging, compatibility, supply-chain, repeat, mutation, and
conditional-platform checks that can run before tagging.
- Measure repository line and branch coverage, configured mature/critical
scope, changed or touched-module regression, and new-module floors. Record
skipped, unavailable, or stale evidence explicitly.
- Prioritize failures and coverage gaps by release risk, recent change, public
contract, trust boundary, and defect history—not by raw uncovered-line count.
- For each blocking gap, add outcome-oriented tests and correct the underlying
implementation or policy defect. Never weaken a release threshold to make a
candidate pass.
- Re-run focused checks after each repair, then re-run the complete applicable
pre-tag gate. Stop when all locally executable hard gates pass or a required
external/platform gate remains unresolved.
- When
releaseEvidence is configured, require one deterministic source ZIP
of the tested commit, a canonical SHA-256 manifest, a bound source SBOM,
SLSA/in-toto provenance, and the configured signature mechanism. Do not
compile or publish installable packages unless a repository explicitly
overrides the source-snapshot policy. Downstream gates must consume the same
ZIP bytes rather than recreating them.
Decision
ready-to-tag only when every applicable pre-tag hard gate passes and all
unavailable evidence is intentionally deferred to an exact-tag hosted gate.
not-ready when any required check fails or a correctness, security,
integrity, compatibility, or coverage gap remains.
hold when the candidate, comparison base, authority, profile, or required
environment cannot be resolved safely.
Use templates/bt6-release-readiness-report.md. A ready-to-tag result becomes
stale on any candidate commit, dependency lock, policy, test, platform, or
release-configuration change. After tagging, always run bt6-release-validation
against the exact immutable tag; readiness is never release certification.
1---2namespace: bt6-maintainer3name: bt6-release-readiness4platforms: [all]5description: Harden an untagged BT6 release candidate to the exhaustive release bar after pull requests were accepted through the bounded contributor gate.6triggers:7 - prepare a BT6 release8 - harden a BT6 release candidate9 - audit merged PRs for release10 - improve coverage before release11requires:12 - candidate-reference: an exact candidate commit and comparison base13 - repository-context: canonical repository, CI remote, and validation profile resolvable from project state14ensures:15 - release-gaps-audited: merged behavior and risk surfaces are checked against the full release policy16 - maintainer-gaps-repaired: authorized test and correctness gaps are fixed before tagging17 - candidate-not-certified: readiness evidence never substitutes for exact-tag validation18metadata:19 source: https://skillmd.com/skills/elder-plinius/bt6-release-readiness20---2122# BT6 Release Readiness2324Prepare a release candidate after normal pull requests have passed the bounded25`validation.quick` contributor gate. Apply `bt6-maintainer-guardrails`. This26workflow may improve code, tests, documentation, and repository-owned release27policy when the operator authorizes implementation. It does not create or28promote a tag.2930## Required context31321. Resolve the canonical repository, base branch, CI remote, profile, candidate33 commit, comparison base, and current authorization.342. Require a clean or explicitly understood working tree. Preserve unrelated35 work and use an isolated checkout when validation could overwrite it.363. Inventory merged changes since the previous release or configured comparison37 base. Map production changes to behavior tests, ownership, and risk surfaces.384. Treat PR acceptance as evidence of reviewability only. Do not infer release39 readiness from quick checks, aggregate coverage, or merge status.4041## Hardening loop42431. Run `validation.full` plus applicable documentation, research-integrity,44 risk-surface, packaging, compatibility, supply-chain, repeat, mutation, and45 conditional-platform checks that can run before tagging.462. Measure repository line and branch coverage, configured mature/critical47 scope, changed or touched-module regression, and new-module floors. Record48 skipped, unavailable, or stale evidence explicitly.493. Prioritize failures and coverage gaps by release risk, recent change, public50 contract, trust boundary, and defect history—not by raw uncovered-line count.514. For each blocking gap, add outcome-oriented tests and correct the underlying52 implementation or policy defect. Never weaken a release threshold to make a53 candidate pass.545. Re-run focused checks after each repair, then re-run the complete applicable55 pre-tag gate. Stop when all locally executable hard gates pass or a required56 external/platform gate remains unresolved.576. When `releaseEvidence` is configured, require one deterministic source ZIP58 of the tested commit, a canonical SHA-256 manifest, a bound source SBOM,59 SLSA/in-toto provenance, and the configured signature mechanism. Do not60 compile or publish installable packages unless a repository explicitly61 overrides the source-snapshot policy. Downstream gates must consume the same62 ZIP bytes rather than recreating them.6364## Decision6566- `ready-to-tag` only when every applicable pre-tag hard gate passes and all67 unavailable evidence is intentionally deferred to an exact-tag hosted gate.68- `not-ready` when any required check fails or a correctness, security,69 integrity, compatibility, or coverage gap remains.70- `hold` when the candidate, comparison base, authority, profile, or required71 environment cannot be resolved safely.7273Use `templates/bt6-release-readiness-report.md`. A `ready-to-tag` result becomes74stale on any candidate commit, dependency lock, policy, test, platform, or75release-configuration change. After tagging, always run `bt6-release-validation`76against the exact immutable tag; readiness is never release certification.