Remove the cold-build workflow: Yocto builds on the build host only

The yocto-cold-build workflow and its kas/ci.yml overlay built the release image on a hosted runner as a reproducibility probe. It never ran to completion, its first dispatch (2026-09-09) stopped on the runner's user-namespace rule, and a probe nobody runs is a trap. Every Yocto build, the release included, runs on the build host; the release proof is the local pipeline (release.sh) and the bench campaign. The pre-publish checklist loses its self-containment line to match.
2026-09-27 08:41:13 -07:00 · 2026-09-09 13:28:05 -04:00
parent 867b1938e4
commit 0107c2cad4
3 changed files with 0 additions and 95 deletions
@@ -369,7 +369,6 @@ cat <<EOF
 Pre-publish checklist (docs.forgefirm.org, Developers, "Release flow"):
  - meta-openglow pushed; kas config flipped to the pinned-remote block
  - kas lock refreshed
-  - self-containment proven from a fresh clone
  - forgefirm-docs current for this release (the currency rule) and pushed

 Publish (from a directory with an authenticated gh):