v1.5.5

Fixed

• Recovery guidance for a broken release was wrong and would have destroyed
  a version number: GitHub permanently retires the tag name of a deleted
  immutable release, so release-guard and CONTRIBUTING now say to bump to
  the next patch instead of deleting and retrying the tag.

Changed

• The weekly compatibility job covers every CLI grammar agent mcp depends
  on. Qwen Code and Amp were named in the contract but never checked, and
  the checked CLIs asserted one representative flag rather than all of
  them. Every flag and subcommand agent-sync passes is now asserted
  individually, and a package that cannot be installed after three attempts
  fails the job rather than being skipped, since a renamed or withdrawn
  package is itself a compatibility break.
• release-guard now requires both release assets, verifies the published
  binary's build-provenance attestation, and checks SHA256SUMS against
  the binary it ships with. Asset presence alone said nothing about where
  the binary came from.

Changes since v1.5.4

• fix: correct release recovery guidance; complete compat coverage (#14) (a22b224)

6 files changed, 176 insertions(+), 55 deletions(-)

Full diff: v1.5.4...v1.5.5