release: 0.1.1 - #23
Merged
Merged
Conversation
The only change since 0.1.0 is the Codex trust diagnostic, which fixes a demonstrated silent failure: --check-hooks reported a healthy registration while Codex, having never been told to trust the project, loaded no hooks at all. Bumping VERSION is what makes that reachable. The installed copy reports its own release through --check-hooks, so leaving it at 0.1.0 while shipping 0.1.1 would recreate the exact problem the file was added to solve. The coexistence test now reads VERSION instead of hardcoding it, so a future bump is one file rather than two. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016cCs5DdUjLDkP8V3Z5x6XH
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.
Patch release for one user-facing fix.
What is in it
The Codex trust diagnostic (#22).
--check-hooksreported a healthy registration on a project Codex had never been told to trust, whilehooks/listreturned zero hooks — a silent failure where the user waits for a hook that will never fire.That is the whole diff since v0.1.0.
Why the VERSION bump matters here
The installed copy reports its own release through
--check-hooks. Shipping 0.1.1 with the file still reading 0.1.0 would recreate exactly the problem that file was added to solve.The coexistence test now reads
VERSIONinstead of hardcoding it, so the next bump is one file rather than two.Unchanged
merge-guardis still not implemented and will not be: a guard that actually blocks would take away something the user can do today, and a guard that can be worked around is a reminder, which the prompts already provide. Everything here should stay something the user can bypass.The continuity compact validation debt is still open. Triggering compact needs an interactive session, and manufacturing a substitute path would produce evidence about the substitute rather than about compact.
🤖 Generated with Claude Code
https://claude.ai/code/session_016cCs5DdUjLDkP8V3Z5x6XH