release: 0.1.3 - #32
Merged
Merged
Conversation
Four merged PRs since 0.1.2, all from real usage feedback rather than anticipated need, closing issues #25, #26 and #27. Planning documents now default to staying out of version control, with the two recommended .gitignore lines stated where a reader is deciding. .structured-coding/standards.md is the deliberate exception, because whether Git tracks it is exactly what standards.py reads to decide whether a declared command needs approval. Sessions are routed through the entrypoint before they act on the workflow. Rule 5 covers a session that is new, replacing another, or a delegated agent; the phase table is stated to be the required resource list; a compliance claim requires having read the rule it cites. The continuity preset names the installed SKILL.md by absolute path at session start, and verify_skill now treats the entrypoint files as part of a complete installation. Endpoint authority is an explicit, sourced decision in the contract. Implementation, semantic commits, branch push, PR creation, CI repair and merge are separate lines, each with its shipped default and where its decision came from. A restriction with no source is not a project decision and no longer overrides the defaults, which is what let an agent present its own caution as the operator's boundary. An overall must enumerate every step it can currently identify before the first freeze, and completing a PR does not complete its overall. Post-merge backward propagation has a named owner, recorded in the contract, with an explicit handoff between the implementation and planning sessions. Nothing new blocks anything, and no mechanical enforcement is claimed for any of it. Runtime behavior changes only in the continuity SessionStart message content and in what verify_skill requires. Co-Authored-By: Claude Opus 5 (1M context) <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.
Version bump only —
structured-coding/VERSIONand the two rebuilt packages. No specification, prose, or runtime change beyond what is already merged.What 0.1.3 contains
Four PRs since 0.1.2, all from real usage feedback rather than anticipated need, closing #25, #26 and #27.
d1c8e14.structured-coding/standards.mdis the deliberate exception9f8ac137848faa76cf3a0Only three of the four issues' root causes were "the agent did not read it". The other three were read-and-misapplied, each with a different mechanism — a missing field, a sentence that let an unsourced restriction win, two claims that could share one sentence, and an undecided
the agent. Those were fixed by changing the shape of the artifact, not by asking for more reading.Runtime surface
Behaviour changes in exactly two places, both from #29: the
continuitypreset's SessionStart message content, and whatverify_skillrequires of an installed skill. Nothing new blocks anything, and no mechanical enforcement is claimed for any of the specification changes.Validation
Ran 171 tests ... OK (skipped=1)--checkvalidations PASSVERSIONreads0.1.3in the source tree and in both distributionsOpen debts, unchanged and not hidden by this release
PostToolUsedelivery under an authenticated turn is registered, parsed and budgeted, but not directly observed.merge-guardis decided against, not pending.🤖 Generated with Claude Code