Release v0.1.7: claim → edition linkage in the annotation - #13
Merged
Conversation
session-budget and consumer-subscriptions-incompatible derive from the maintainer's deployment experience, not from any source edition — session-budget cites framework telemetry in its own prose. So they get no `editions:` entry and no OKF `sources` key, which is the design working rather than a gap in it: attribution tops out at 4 of 6 across both instances and that is the honest number. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Ships the optional `editions:` annotation field — recorded claim→edition linkage, which the OKF export cites instead of guessing — together with the parser fix that motivates releasing it rather than sitting on it. The pin bump is the point of the release. An engine older than this parses a four-field annotation with the extra field absorbed into `status`, silently: an overturned claim then exports as OKF `status: stable`. So instances cannot safely be handed prose carrying the new field until they are pinned here, and the backfill across both instances is gated on this tag existing. Bumps every `#v0.1.6` pin — the five scaffold workflow lines, their two test expectations, and the invocation examples in cli.md / adopting.md, including the two that quote a version in prose rather than in a command. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Cuts v0.1.7, which exists so the instances can be pinned to an engine that reads the new annotation field safely.
Why now rather than later
An engine older than #12 parses a four-field annotation with the extra field absorbed into
status, silently — an overturned claim then exports as OKFstatus: stable. So the backfill across both instances is gated on this tag existing, and the pin bump is the substance of the release rather than routine housekeeping.Contents
package.json→0.1.7.#v0.1.6pin →#v0.1.7: the five scaffold workflow lines, their twoscaffold.test.tsexpectations (the pair that must move together), and the invocation examples indocs/cli.md+docs/adopting.md— including the two that quote a version in prose rather than inside a command, which a grep for the npx line alone would have missed.b7542e8, a one-paragraph doc commit that was pushed to feat: record claim → edition linkage in the annotation #12's branch after that PR had already been merged and so never reachedmain: it records thatsession-budgetandconsumer-subscriptions-incompatibleget noeditions:entry, because both derive from deployment experience rather than a source edition.docs/superpowers/plans/still mentions#v0.1.6and is deliberately untouched — it is a historical plan record, not a pin.Verification
npm run check— 237 tests pass. After merge I'll tag the merge commit and verify the public path (npx --yes github:norabble/continuous-research#v0.1.7 --version) before touching either instance.🤖 Generated with Claude Code
https://claude.ai/code/session_01Wt7EGVdsJMSSF2nnWmrWra