Bump coherence-harness to v0.31.0: the pinned v0.27.0 predates the hook binary - #22
Draft
tieguy wants to merge 1 commit into
Draft
Bump coherence-harness to v0.31.0: the pinned v0.27.0 predates the hook binary#22tieguy wants to merge 1 commit into
tieguy wants to merge 1 commit into
Conversation
…ook binary The .claude/coherence-hook launcher execs node_modules/.bin/coherence-hook, but that binary first shipped in v0.28.0 — eight minutes after the v0.27.0 pin was adopted. So every lifecycle hook (SessionStart/Stop/PostToolUse/ Subagent*) has been exiting 127 "target missing" on every checkout since. Bump straight to latest (v0.31.0) and regenerate the launcher via `coherence hooks install --host claude` (v0.31 adds a drift fingerprint to the launcher; the hand-authored one registers as DRIFTED). Docs artifacts regenerated with the new harness so the freshness gate compares like with like. hooks-check now reports launcher READY; suite, freshness gate, and all four ratchets green under 0.31.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rf5RTB7iigiMpoArYzdUKN
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.
While setting up my instance, my bot noticed the Claude Code lifecycle hooks failing with "coherence hook target missing" on a fresh checkout.
Root cause:
.claude/coherence-hookexecsnode_modules/.bin/coherence-hook, but that binary first shipped in coherence v0.28.0 — and the repo pins v0.27.0, adopted (going by the timestamps) about eight minutes before v0.28.0 landed. So the hooks have been silently dead on every checkout since: the launcher exits 127, non-blocking, easy to never notice.This bumps straight to latest (v0.31.0) and regenerates the launcher with
coherence hooks install --host claude— v0.31 stamps a drift fingerprint into the launcher, so the hand-authored one registers as DRIFTED otherwise. Docs artifacts regenerated with the new harness.hooks-checknow reports the launcher READY; suite, freshness gate, and all four ratchets green under 0.31.0.Heads up that v0.28→0.31 also brings the decision journal and the anti-entropy regulator, which start injecting instructions into agent sessions once the hooks actually fire — that's a behavior change for anyone working in the repo, and worth a deliberate yes from you.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Rf5RTB7iigiMpoArYzdUKN