BT6 Release Validation
Validate an existing tag before publishing or promoting release artifacts. Apply
bt6-maintainer-guardrails. This workflow does not create, move, or delete tags
and does not publish a release without separate explicit authorization.
Required context
- Resolve the canonical repository, CI remote, base branch, profile, expected
actor, and release authority from project configuration and live state.
- Resolve the requested tag to an immutable commit and record whether the tag
is signed or annotated when repository policy requires it.
- Refuse an ambiguous, missing, moving, or policy-disallowed tag. Never validate
the working tree as a substitute for the exact tagged commit.
- Use an isolated checkout or worktree so validation does not overwrite local
work.
Required validation
- Run every repository-profile
validation.full command at the exact tagged
commit.
- Run applicable
documentation, researchIntegrity, and risk-surface checks.
- Run repository-defined source-snapshot integrity, compatibility, and
supported-platform checks. Verify the release ZIP comes from the tagged
source rather than an unrelated checkout; do not require a compiled package.
- Compare local evidence with CI for the same tag and commit. Record missing or
stale evidence as incomplete, not passing.
- Treat warnings, flakes, skips, coverage changes, and conditional-gate gaps
according to repository release policy; do not inherit the relaxed PR
turnaround budget as a release exemption.
- When
releaseEvidence is configured, verify every artifact against the
canonical checksum manifest, authenticate its SLSA/in-toto attestation,
validate the source-SBOM binding, and prove promotion uses the tested
snapshot-once ZIP bytes. A checksum without authenticated provenance is
incomplete evidence.
Decision
pass only when every required check succeeds for the exact tag commit.
fail for any failed required check or artifact/source mismatch.
hold when the tag, authority, profile, platform evidence, or required command
cannot be resolved safely.
Do not promote artifacts or describe the tag as released after fail or hold.
Use templates/bt6-release-validation-report.md and record the event that makes
the evidence stale.
1---2namespace: bt6-maintainer3name: bt6-release-validation4platforms: [all]5description: Validate an exact tagged BT6 release with the repository's exhaustive suite before artifacts are promoted.6triggers:7 - bt6 release validation8 - validate a tagged BT6 release9 - run the full BT6 release gate10requires:11 - tagged-reference: an existing tag resolvable to an exact commit12 - repository-context: canonical repository, CI remote, and validation profile resolvable from project state13ensures:14 - exact-tag-validated: report binds every check to the resolved tag and commit15 - full-suite-required: profile full commands and applicable release checks pass16 - no-promotion-on-failure: failed or incomplete validation blocks release artifacts17commandHint:18 argumentHint: "<tag> [--report-only]"19 allowedTools: Bash, Read, Grep20 model: sonnet21 category: release-management22 modelRole: reasoning23 modelTier: standard24metadata:25 source: https://skillmd.com/skills/elder-plinius/bt6-release-validation26---2728# BT6 Release Validation2930Validate an existing tag before publishing or promoting release artifacts. Apply31`bt6-maintainer-guardrails`. This workflow does not create, move, or delete tags32and does not publish a release without separate explicit authorization.3334## Required context35361. Resolve the canonical repository, CI remote, base branch, profile, expected37 actor, and release authority from project configuration and live state.382. Resolve the requested tag to an immutable commit and record whether the tag39 is signed or annotated when repository policy requires it.403. Refuse an ambiguous, missing, moving, or policy-disallowed tag. Never validate41 the working tree as a substitute for the exact tagged commit.424. Use an isolated checkout or worktree so validation does not overwrite local43 work.4445## Required validation46471. Run every repository-profile `validation.full` command at the exact tagged48 commit.492. Run applicable `documentation`, `researchIntegrity`, and risk-surface checks.503. Run repository-defined source-snapshot integrity, compatibility, and51 supported-platform checks. Verify the release ZIP comes from the tagged52 source rather than an unrelated checkout; do not require a compiled package.534. Compare local evidence with CI for the same tag and commit. Record missing or54 stale evidence as incomplete, not passing.555. Treat warnings, flakes, skips, coverage changes, and conditional-gate gaps56 according to repository release policy; do not inherit the relaxed PR57 turnaround budget as a release exemption.586. When `releaseEvidence` is configured, verify every artifact against the59 canonical checksum manifest, authenticate its SLSA/in-toto attestation,60 validate the source-SBOM binding, and prove promotion uses the tested61 snapshot-once ZIP bytes. A checksum without authenticated provenance is62 incomplete evidence.6364## Decision6566- `pass` only when every required check succeeds for the exact tag commit.67- `fail` for any failed required check or artifact/source mismatch.68- `hold` when the tag, authority, profile, platform evidence, or required command69 cannot be resolved safely.7071Do not promote artifacts or describe the tag as released after `fail` or `hold`.72Use `templates/bt6-release-validation-report.md` and record the event that makes73the evidence stale.