Cull Release Publish
Authority
An explicit “Release Cull patch|minor|major” or direct “Publish prepared Cull
release X.Y.Z” request authorizes publication. Do not ask for another confirmation
after gates pass. That authority does not waive or bypass any gate.
Implicit invocation is disabled. Without that explicit authority, stop before any
tag, push, workflow dispatch, release, or tap mutation.
Publish
- Resolve the Cull checkout and parse one JSON envelope from
npm run release:cull -- state show --version "$VERSION" --json.
- Require state
prepared, exact metadata, a clean release commit already pushed
on main, green required checks, active branch/tag protection, publication
enablement, and no conflicting tag.
- Create one annotated tag for the prepared commit and push that tag normally.
Never move, replace, or force-push a tag.
- Watch the tag-bound GitHub release workflow. Never substitute a local build.
- Require the secret-free verifier's exact artifact inventory, signatures,
notarization, checksums, and provenance before automatic publication.
- Wait for checksum-pinned Homebrew promotion and its audit/install/launch proof.
- Record evidence transitions through
published and homebrew-promoted using
the repository CLI's state commands.
Tag-time anchor and race rules (required)
- The release workflow gate requires the tagged SHA to be at-or-ahead of
origin/main and to carry the bumped version files. Only the release PR's
merge commit satisfies both. The record's
releaseCommit (written by
prepare as the pre-prepare tip) does not — re-anchor the record's
releaseCommit to the merge commit (external-evidence cache repair) after the
release PR merges, then pass that SHA to --expected-source.
- Immediately before tagging:
git fetch origin main and verify the tip still
equals the merge commit and no auto-merge PR is mid-flight. A single dependabot
commit landing after the tag push burns the tag (STALE_RELEASE_SOURCE; tags
are immutable) — recovery is a deeper version, not a tag move.
- Watch the run's gate step first; only then do the longer build/notarize steps
matter. If the gate fails, stop and route through cull-release-recover.
On failure, use cull-release-recover. Never delete or rewrite a tag, delete a
release, replace published assets, bypass verification, or force workflow state.
1---2name: cull-release-publish3description: Use when the user explicitly asks to publish or complete a prepared Cull release, or when the authorized cull-release orchestrator reaches publication after every repository and artifact gate passes.4metadata:5 source: https://skillmd.com/skills/glebis/cull-release-publish6---78# Cull Release Publish910## Authority1112An explicit “Release Cull patch|minor|major” or direct “Publish prepared Cull13release X.Y.Z” request authorizes publication. Do not ask for another confirmation14after gates pass. That authority does not waive or bypass any gate.1516Implicit invocation is disabled. Without that explicit authority, stop before any17tag, push, workflow dispatch, release, or tap mutation.1819## Publish20211. Resolve the Cull checkout and parse one JSON envelope from22 `npm run release:cull -- state show --version "$VERSION" --json`.232. Require state `prepared`, exact metadata, a clean release commit already pushed24 on `main`, green required checks, active branch/tag protection, publication25 enablement, and no conflicting tag.263. Create one annotated tag for the prepared commit and push that tag normally.27 Never move, replace, or force-push a tag.284. Watch the tag-bound GitHub release workflow. Never substitute a local build.295. Require the secret-free verifier's exact artifact inventory, signatures,30 notarization, checksums, and provenance before automatic publication.316. Wait for checksum-pinned Homebrew promotion and its audit/install/launch proof.327. Record evidence transitions through `published` and `homebrew-promoted` using33 the repository CLI's state commands.3435## Tag-time anchor and race rules (required)3637- The release workflow gate requires the tagged SHA to be at-or-ahead of38 origin/main **and** to carry the bumped version files. Only the release PR's39 **merge commit** satisfies both. The record's `releaseCommit` (written by40 prepare as the pre-prepare tip) does not — re-anchor the record's41 `releaseCommit` to the merge commit (external-evidence cache repair) after the42 release PR merges, then pass that SHA to `--expected-source`.43- Immediately before tagging: `git fetch origin main` and verify the tip still44 equals the merge commit and no auto-merge PR is mid-flight. A single dependabot45 commit landing after the tag push burns the tag (STALE_RELEASE_SOURCE; tags46 are immutable) — recovery is a deeper version, not a tag move.47- Watch the run's gate step first; only then do the longer build/notarize steps48 matter. If the gate fails, stop and route through cull-release-recover.4950On failure, use cull-release-recover. Never delete or rewrite a tag, delete a51release, replace published assets, bypass verification, or force workflow state.