repin: product-lifecycle-templates v0.4.0 -> v0.5.0 - #97
Merged
Conversation
Registry 1.74.0 -> 1.75.0. Pins commit aaa1bc2, which is the commit the v0.5.0 annotated tag points at, not the tag object. v0.5.0 adds the `epic` bundle, the member's 27th and the first it built under its own maintainer-preference build order rather than from a plan. The entry description moves from 26 to 27 templates and names `epic`; the README row follows. Contract checked before pinning, not after: L1 through L4 are MUST and the pinned tree satisfies all four. L5 is not satisfied, deliberately noted rather than glossed: the member has no documentation site at all. It is a SHOULD on a path to MUST, so it does not block the listing. Also noted and NOT edited here: L5's prose still says "all four current members conform today" while this registry lists six. Correcting a contract clause inside a re-pin is the wrong place for it. validate-registry.mjs passes with a token. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017k2JQRLkypxTn46QQQBSZk
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.
Registry 1.74.0 -> 1.75.0. Pins
aaa1bc2, the commit thev0.5.0annotated tag points at (not the tag object, per the member's own release-process note that these differ and pins want the commit).Why now
product-lifecycle-templatesreleased v0.5.0 today, adding theepicbundle - its 27th, and the first template it built under its own maintainer-preference build order rather than from a plan. The release and this re-pin were done in one sitting, by hand rather than byrepin-watch.Section 7 checklist
library.jsonpins the Standard, tier Advanced. The member's CI self-hosts the conformance gate; it reports Tier Advanced, 0 errors, 0 warnings at the pinned commit.library.json, and every native manifest (.claude-plugin/plugin.json);CHANGELOG.mdcarries a[0.5.0]entry; a user-facing release note exists atdocs/releases/v0.5.0.md.validate-registry.mjspasses with a token.One thing for this repository, deliberately not fixed here
L5's prose reads "All four current members conform today." This registry now lists six. That sentence is this repo's to correct and correcting a contract clause inside a re-pin is the wrong place for it, so it is recorded in the changelog entry and left alone in the diff.
🤖 Generated with Claude Code
https://claude.ai/code/session_017k2JQRLkypxTn46QQQBSZk