[alebgl77]

Summary

The v0.4.0 tag backfill (manual run of tag-release.yml on 9a44528) cannot succeed on main today, for two reasons:

• it runs today's CI against a commit whose files predate it (ROADMAP.md, diagrams, …);
• the release step requires core/engine/version.js and scripts/sbom.js, which that commit does not have.

Changes:

• Backfill verification. A manual (dispatch) run now checks the CI already recorded on the target commit: every check run must be completed with success, skipped, or neutral. A push to main still runs the full suite, as before.
• Release workflow. release.yml takes a verified input, so a tag-release run no longer repeats the full CI. It skips the version.js coherence check on tags that predate that file, and it takes the SBOM script from the workflow's own commit.
• The coherence checks on CHANGELOG, CITATION.cff, install.sh and package.json are unchanged.

actionlint passes on both workflows.

Type of change

• Adapter (new or updated adapters/ folder)
• Docs (README, CONTRIBUTING, adapter READMEs)
• Core spec (core/SPEC.md rubric or protocol)
• Fix (corrects wrong or misleading behaviour)
• Chore (CI, assets, housekeeping)

Contribution checklist

• Every SPEC §5 integrity invariant still holds after this change (CI only)
• No invented benchmarks, fake numbers, or decay curves that don't come from a real ledger.
• README / docs updated if behaviour changed (CHANGELOG Unreleased).

🤖 Generated with Claude Code

https://claude.ai/code/session_01PLrdn9WeCR69ebp67qYCtm

---

Generated by Claude Code