Falling-Metal-Interactive/Blacksite
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity
106d947c98
Blacksite/.agents/skills/blacksite-release-candidate/SKILL.md

1.2 KiB
Raw Blame History

name description
blacksite-release-candidate Nominate and verify one Blacksite candidate tree or commit, reuse still-valid selective verification evidence, run the remaining full release gates once, produce an evidence manifest, and hand results to Gitea synchronization.

Blacksite release candidate

Read .codex/workflow.toml and the release gates. Require stable scope, no pending major delta, and Candidate-ready session state.

  1. Record the candidate SHA or dirty-tree digest.
  2. Read the verification ledger and reuse every gate whose relevant input digest and lane signature remain valid.
  3. Run only missing/invalid release gates via verify.py candidate and managed candidate/package lanes.
  4. Preserve final binaries/package output and required native evidence before disposable-lane pruning.
  5. Write .codex/session/candidate-evidence.json with commands, digests, results, artifacts, screenshots, and documentation status.
  6. Run documentation integrity and hand a dry-run/authorized candidate update to blacksite-gitea-sync.

Do not push, close, or change tracker scope outside direct or configured authority. Run full workspace/all-feature tests and strict lint only once per candidate code digest.