[AUTOMATED] fix(captain): stop truncating the handoff note --status exists to deliver - #445
Merged
Merged
Conversation
…xists to deliver #438 put the round's notes into `--status` because nothing was delivering them to the next tick. It capped each at 700 chars, and I justified that in the commit as avoiding "a payload nobody finishes reading". That was a guess, and the round-4 captain measured it for me. Its own note reads: NEXT-TICK ORDERS (--status truncates at ~700 chars -- read the note above WHOLE from rounds/4/round.json before deciding anything) A cap that forces the reader to open the file anyway saves nothing and removes the point of the fix. The captain adapted by telling the next tick where to go, which works, but that is a workaround for my choice, not a resolution of it. The NEWEST note is now delivered whole -- it is the actual handoff, the one written specifically for the tick that reads it. Round 4's is 4,283 chars. Older notes are context rather than instructions and stay capped, at 2000 rather than 700, and say where the full text lives. The general shape is worth keeping in mind for this codebase: a truncation, a default, or a summary that drops the thing the reader needed is the same failure as not delivering it at all, and it is harder to notice because something did arrive. tools/repipe/smoke.sh 138/138. 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.
#438 put the round's notes into
--statusbecause nothing was delivering them to thenext tick. It capped each at 700 chars, and I justified that in the commit as avoiding
"a payload nobody finishes reading". That was a guess, and the round-4 captain measured
it for me. Its own note reads:
NEXT-TICK ORDERS (--status truncates at ~700 chars -- read the note above WHOLE
from rounds/4/round.json before deciding anything)
A cap that forces the reader to open the file anyway saves nothing and removes the
point of the fix. The captain adapted by telling the next tick where to go, which
works, but that is a workaround for my choice, not a resolution of it.
The NEWEST note is now delivered whole -- it is the actual handoff, the one written
specifically for the tick that reads it. Round 4's is 4,283 chars. Older notes are
context rather than instructions and stay capped, at 2000 rather than 700, and say
where the full text lives.
The general shape is worth keeping in mind for this codebase: a truncation, a default,
or a summary that drops the thing the reader needed is the same failure as not
delivering it at all, and it is harder to notice because something did arrive.
tools/repipe/smoke.sh 138/138.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
🤖 Generated with Claude Code
https://claude.ai/code/session_01YcFmfZndNjgfqLQVBZCdkY