Sweep remaining "tracked bounded read" claims (#597 follow-up)#598
Merged
Conversation
PR #597 removed the em-search --read body cap but swept only README, the scripts guide, and RFC-011. Three deployable surfaces still described the read as bounded: instructions/SKILL.md:52 — deploys to EVERY consuming project docs/USER_MANUAL.md:87 scripts/em-trigger-index.mjs:52 (comment) instructions/SKILL.md is the consequential one: install.mjs --update-consumers copies it into each registered project, so the stale claim propagated fleet-wide before this fix. Verified by an exhaustive grep across instructions/, docs/, scripts/, plugins/, and README.md. The only surviving matches are in docs/plans/, which are point-in-time records of work as it was planned and correctly describe the contract that existed then. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
lantiscooperdev
approved these changes
Jul 25, 2026
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
2 participants
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.
PR #597 removed the
em-search --readbody cap but swept onlyREADME.md,docs/EM_SCRIPTS_GUIDE.md, andRFC-011. Three deployable surfaces still described the read as bounded:instructions/SKILL.md:52install.mjs --update-consumersdocs/USER_MANUAL.md:87scripts/em-trigger-index.mjs:52read_commandpoints atinstructions/SKILL.mdis the consequential one. The post-merge consumer sync copied the stale claim into every registered project before this was caught, so those projects need a re-sync once this lands.How it was missed
The #597 sweep grepped for
49152andbody_truncated, then forboundedonly acrossREADME.md, the scripts guide, and the RFC.instructions/anddocs/USER_MANUAL.mdwere never in the grep path. The kimi reviewer caught the same class inside the RFC (finding F1) and I fixed those sites without widening the search to the rest of the tree.Verification
Exhaustive grep for
tracked bounded,bounded read, andbounded single-episodeacrossinstructions/,docs/,scripts/,plugins/, andREADME.md. The only surviving matches are indocs/plans/(rfc-009-p4, rfc-011-p1, RFC-007-P2), which are point-in-time plan records that correctly describe the contract as it existed when they were written, plusbp1-rfc-scan.mjswhere "bounded read" refers to its own file-read buffer and is unrelated.Deliberately unchanged: the "bounded" at
RFC-011:90,:110,:124,README:255,:849,GUIDE:190,GUIDE:1480, which bind to the preference file, the body-excerpt deferral, the build report, telemetry, lesson pointers, and RFC-009 R7 respectively.🤖 Generated with Claude Code