v1.1.0

Changed

• Both plugins are pinned to a release tag (ref: v2.8.0, ref: v0.3.0) instead of resolving against whatever main held at install time. An update now gives you a version that was tagged and released.
  This adds a release step: a newly tagged plugin does not reach anyone until its version and ref are bumped here — and the new version check turns forgetting that into a CI failure rather than a silent no-op.

Added

• CI clones each git-subdir source at its pinned ref, checks the path exists, runs claude plugin validate --strict inside it, and asserts the tag, the catalog entry and the plugin's own plugin.json all name the same version. Validating this repo's manifest said nothing about whether the plugins it pointed at still existed — a renamed or deleted path would have kept CI green until someone hit the broken install.