Release: recall 0.19.1 - #999
Merged
Merged
Conversation
Two defects in the journal store, both of which fail toward looking fine. WRITE. The three journal fields were each split on ";", so a semicolon used as ordinary punctuation fragmented a sentence and stripped its subject. The result reads as a list of terse notes rather than as damage, which is why it survived: nothing looks broken. Measured on a real entry, one field produced seven items, six of which began mid-sentence, and one read in full as "the fix on grip dev is 4d11834e" -- true, unattached, meaningless to the reader it was written for. Splitting now prefers newlines and falls back to semicolons only when the text has none. That is how these fields are actually written -- one item per line -- and it keeps every existing single-line caller working unchanged, so `--done "a; b; c"` behaves exactly as before. A single-line field containing prose semicolons is still ambiguous by construction; the fallback is what preserves the documented CLI convention, and that trade is deliberate. The split also existed in six places across two modules, which is its own latent defect: fixing one path would have left the other mangling prose. It is now one function, called from both. READ. The session-start read is BOUNDED, and it rendered Done, then Decisions, then Next -- so completed work consumed the window before open threads were reached. Ordering is not a matter of taste on a truncated surface; whatever leads is what survives. Open threads now lead. Completed work is recoverable from git and the board; an unrecorded open question is recoverable from nowhere. The unbounded display is reordered to match. Nothing forces it there, but two surfaces that teach different priorities are their own defect, and a human reading a full entry also reads top-down and stops. DOCUMENTATION. The author-facing text said "Semicolon-separated list" in six places -- three in the MCP tool description and three in CLI help -- and after this change that is wrong for the multi-line case and right for the single-line one. A half-true rule is worse than the original defect, because it is confidently wrong in one direction. Both surfaces now state the real behaviour at the point of writing, along with the fact that the session-start read is truncated and leads with next_steps, since that changes how an author composes an entry. The two genuinely semicolon-delimited options elsewhere are left alone. Both witnesses assert what the READER RECEIVES rather than what was written, which is the only form that catches this class -- the same move as verifying a published artifact against what the server serves rather than against what was uploaded. Each is killed by exactly one mutation: reversing the ordering tuple reddens the ordering witness alone, and restoring the semicolon-only split reddens the prose witness alone. Co-Authored-By: Claude <noreply@anthropic.com>
fix(journal): keep prose whole on write, lead with open threads on read
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Promote dev to main for the recall 0.19.1 release.
Contents: the journal fix and the version bump to 0.19.1.
Closes #997
Promote-branch pattern: the head is
promote/v0.19.1(neverdev), merged as a regular merge commit.