chore(001): bump the spec-spine pin to 0.14.0 - #4
Merged
Conversation
Every site that states the pin (govern.yml, AGENTS.md, README.md, the setup skill, the architect agent) moves from 0.11.0 to 0.14.0, with the reason recorded as spec 001 D-4. Corpus verified byte-compatible first; regenerated shards restale only via the hashed harness inputs.
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.
What
Bumps the
spec-spinepin from 0.11.0 to 0.14.0 in every site that states it (govern.yml,AGENTS.md,README.md,/setup, the architect agent). Recorded as spec 001 D-4.The corpus was verified byte-compatible first: 0.14.0's
compile --checkandindex checkboth report fresh against the shards 0.11.0 wrote. The regenerated shards in this PR restale only because the harness files are hashed inputs; content is unchanged apart from the pin.What the bump buys here:
registry plan(038),--jsonverdicts on the gate verbs (037),layout.state_dir(039),depends_oncycle refusal (033), and the lifecycle fixes 041/044/045. Notespec-spine indexnow prints theW-001warnings it always recorded: on a corpus with pending specs that is one line per not-yet-written unit and is the expected state.Follow-ons (add
registry planto the init reads, retire the Python in/next, declaredata/asstate_dir) are their own change.Testing
Run with the 0.14.0 binary from the branch head:
compile --checkfresh,index checkfresh,lint --fail-on-warnclean,couple --base origin/main --head HEADno drift, no waiver.