You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 2026-06-09 automation audit was supplemented on 2026-06-10 with three new artifacts and elevation of the operating principle into top-level docs. See:
actions-v1-tag-update.yml (originally Phase 1 of the roadmap) directly contradicts the existing hard rule in projectbluefin/actions/AGENTS.md:
@v1 tag moves require human authorization. Force-pushing the shared tag affects every consumer repo simultaneously. Do not initiate this as an agent action.
The actions-v1-tag-update.yml artifact in this audit was drafted before that rule was added (or in ignorance of it). Two possible resolutions, both human-decision territory:
Keep the rule, retire the artifact — accept that v1 tag advances stay manual; rely on Renovate to bump SHAs in consumers (which doesn't need a v1 move).
Relax the rule, ship the workflow — but only after a security review of who can trigger merges to actions/main (the human merge gate already exists, so the v1 move arguably becomes mechanical post-merge).
Filing as a separate design-decision issue would be appropriate; not doing it autonomously per the upstream-issue gate.
⏸ Deferred — needs paired consumer PR
The actions repo's consumer-validation.yml gate enforces real consumer PR + CI run URLs for any change to bootc-build/*/action.yml or .github/workflows/reusable-*.yml. The following audit artifacts can be split into two PR types:
Artifact
Where
Consumer-validation needed?
retry/action.yml
root of actions/
No (top-level composite, not under bootc-build/)
check-token-health/action.yml
root of actions/
No
.github/workflows/reusable-promote.yml
actions/
Yes — needs canary dakota draft PR
Recommended next session: open the actions PR with the two top-level composites (no consumer gate), then a separate canary PR pair (actions + dakota draft) for reusable-promote.yml.
❌ Out of scope (this rollout)
projectbluefin/iso — explicit user constraint. iso-auto-rebuild.yml and iso-dispatch-snippet.yml retained as proposals only.
Activity
castrojo commentedon Jun 10, 2026
Session execution report — 2026-06-10
✅ Landed
e10bb69onmain. 4 new artifacts + 3 mantra-elevation edits.projectbluefin/dakota#782(Phase 7).actions-v1-tag-update.yml(originally Phase 1 of the roadmap) directly contradicts the existing hard rule inprojectbluefin/actions/AGENTS.md:The
actions-v1-tag-update.ymlartifact in this audit was drafted before that rule was added (or in ignorance of it). Two possible resolutions, both human-decision territory:actions/main(the human merge gate already exists, so the v1 move arguably becomes mechanical post-merge).Filing as a separate design-decision issue would be appropriate; not doing it autonomously per the upstream-issue gate.
⏸ Deferred — needs paired consumer PR
The
actionsrepo'sconsumer-validation.ymlgate enforces real consumer PR + CI run URLs for any change tobootc-build/*/action.ymlor.github/workflows/reusable-*.yml. The following audit artifacts can be split into two PR types:retry/action.ymlactions/bootc-build/)check-token-health/action.ymlactions/.github/workflows/reusable-promote.ymlactions/Recommended next session: open the actions PR with the two top-level composites (no consumer gate), then a separate canary PR pair (actions + dakota draft) for
reusable-promote.yml.❌ Out of scope (this rollout)
projectbluefin/iso— explicit user constraint.iso-auto-rebuild.ymlandiso-dispatch-snippet.ymlretained as proposals only.docs(factory): refresh automation audit — drift verification
castrojo commentedon Jun 10, 2026
Drift-refresh finding tracked: #589 —
isoandbonediggerneedCODEOWNERS. Joins #584 / #585 / #586 as the live follow-up batch.castrojo commentedon Jun 10, 2026
Execution batch landed (4 PRs, lockstep with the audit-doc roadmap):
Remaining open from the audit: #584 (C1 reusable-promote — 1-day refactor, separate session).
feat(ci): add reusable-promote-squash.yml + release-state schema (C1/C5)
feat(ci): add reusable-promote-squash.yml + release-state schema (C1/…
feat(ci): supply chain hardening — keyless signing, SBOM, SLSA L2, Tr…
feat(ci): supply chain hardening — keyless signing, SBOM, SLSA L2, Tr…
feat(ci): add cache-warm scheduled workflow
feat(ci): add cache-warm scheduled workflow
feat(ci): add cache-warm scheduled workflow (#782)
chore(next): sync from main — bring next up to date with all main cha…