registry(1.77.0): re-pin product-lifecycle-templates to v0.6.0 (ca174fc) - #100
Merged
Merged
Conversation
The listing served v0.5.0 for five days after v0.6.0 released. The member tagged v0.6.0 on 2026-09-06 and this registry was never moved, so anyone installing in that window received a tree without the release's entire headline feature. repin-watch did not open this one; done by hand at the member maintainer's direction. sha aaa1bc2 -> ca174fc entry version 0.5.0 -> 0.6.0 metadata.version 1.76.0 -> 1.77.0 The description gains the MCP server, which is what v0.6.0 is for. The old text sold the 27-bundle Tier-1 floor alone and would have gone on describing a release behind the pinned one. L1-L4 verified AT THE TAG rather than at the member's main: native plugin at the root (.claude-plugin/plugin.json at 0.6.0), root library.json binding the Standard at advanced (standard 0.12), versions agreeing across the tag, library.json and the native manifest, and a CHANGELOG.md entry for the release. The pinned sha is the COMMIT the tag points at (ca174fc), not the annotated tag object (bf2ef73) - for this member those are two different objects. L5 is still not satisfied and is not treated as if it were. The member has no documentation site. It gained a ratified plan and an adopting decision record on 2026-09-11, which is a stated path and not a site. validate-registry.mjs passes against this exact tree with GITHUB_TOKEN set. Note that without a token it reports five sha-on-tag checks as 403 transient/infra, which is inconclusive rather than failing. This file jumps 1.75.0 to 1.77.0: metadata.version was bumped to 1.76.0 by the thinking-framework-skills re-pin and no [1.76.0] section was ever written. That gap is left for whoever made it rather than reconstructed here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013N7ZJx5Pk4z4nfwAyrxXLz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The gap this closes
The listing served
v0.5.0for five days afterv0.6.0released. The member taggedv0.6.0on 2026-09-06 and this registry was never moved, so anyone installing in that window received a tree without the release's entire headline feature - the MCP server.repin-watchdid not open this one. Done by hand at the member maintainer's direction.source.shaaaa1bc2ca174fcversion0.5.00.6.0metadata.version1.76.01.77.0descriptionThe description mattered more than it looks: the old text sold the Tier-1 floor alone and would have gone on describing a release behind the pinned one.
Contract check, verified at the tag
L1 through L4 are MUST and the pinned tree satisfies all four - checked against
v0.6.0itself, not the member'smain:.claude-plugin/plugin.jsonat0.6.0library.jsonbinding the Standard atadvanced(standard: 0.12)library.jsonand the native manifestCHANGELOG.mdentry exists for the releaseThe pinned
shais the commit the tag points at (ca174fc), not the annotated tag object (bf2ef73). For this member those are two different objects, so it is worth stating.L5 is still not satisfied and is not treated as if it were. The member has no documentation site. On 2026-09-11 it gained a ratified site plan and an adopting decision record, which is a stated path and not a site. L5 is a SHOULD on a stated path to MUST, so this does not block the listing and does not discharge the clause either.
Validation
validate-registry.mjspasses against this exact tree withGITHUB_TOKENset.Worth flagging for anyone running it locally: without a token it reports five
sha-on-tagchecks as403 transient/infraand printsregistry INVALID. That is inconclusive, not failing - and it is easy to misread as a real rejection.One thing this PR deliberately does not fix
metadata.versionwas bumped to1.76.0by thethinking-framework-skillsre-pin (#99) and no[1.76.0]section was ever written inCHANGELOG.md. So this file jumps1.75.0to1.77.0.That gap is left for whoever made it rather than reconstructed here from a commit title inside an unrelated re-pin. Related: issue #98 prepares an
agent-skills-toolkitre-pin that also claims1.76.0, which is now taken.🤖 Generated with Claude Code
https://claude.ai/code/session_013N7ZJx5Pk4z4nfwAyrxXLz