release: baton 1.3.1 — run-trail close-out count can't contradict its own lines#34
Merged
Conversation
… own lines Bumps 1.3.0 -> 1.3.1 (plugin.json, runtime/package.json, lockfile) + CHANGELOG 1.3.1 entry. Patch: the ledger close-out count now derives from ledger.py's own recorded lane lines (reconciled with the sibling lane_spawns.jsonl), so it can never read lower than the lines it displays. Trail-only; no enforcement/verdict change. Fix landed in #33. Co-Authored-By: Claude Opus 4.8 <[email protected]>
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. Version bump 1.3.0 → 1.3.1 (
plugin.json,runtime/package.json, lockfile) + CHANGELOG## 1.3.1section. Pushing thev1.3.1tag after merge triggersrelease.ymlto publish (notes from the CHANGELOG section).The fix itself landed in #33. This is the release cut.
What 1.3.1 fixes
A real integration test surfaced a consistency bug: the
Stopclose-out could printlanes recorded this session: 0directly above the lane lines it had just written — because the count read only the siblinglane_spawns.jsonl(a separate hook) and notledger.py's own lines. The count now derives from ledger.py's own recorded lane lines, reconciled with the sibling (the higher of the two), so it can never read lower than the lines shown.Trail-only — no change to any enforcement verdict, the disposition gate, or the frozen 1.0 contract.
🤖 Generated with Claude Code