fix: disclose clipped selected-project README context - #148
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Superseded by #150. That branch carries this work reconciled with the other two context-admission PRs, and #150's head is green on all 8 checks. Verified equivalence before closing: #150 retains 18/18 of #146's added tests, 6/6 of #147's, and 9/9 of #148's (one renamed). #146's head here never received the project-root-swap repair; #150 contains it, byte-identical to the reviewed local fix. This head is older than #150 and conflicts with it, so merging it would regress. Closing rather than merging. The branch is archived in a local git bundle and this PR can be reopened if #150 is ever abandoned. |
Project briefs now disclose when the selected README excerpt was clipped or lost to the final output budget. Compact text, hook JSON, and MCP carry the same coverage information so an assistant can recognize missing constraints before proposing work. Off and inferred Shared context make no coverage claim.
The implementation stays inside the existing context selector and operational envelope. Coverage has a separate fixed 512-character allowance, including the repeated hook notice; the current maximum is 485 characters. The visible budget, operational allowance,
budget.truncated, and MCPcompletekeep their existing meanings. No additional source reads, automatic expansion, durable writes, provider calls, or dependencies are added.Validation:
57b7da9dcb2d87b2fcc82f0c329e7c704c560c36.Before the behavior-preserving simplification, a disposable combination with #147 passed 191 focused checks and smoke. Two fresh agents also received actual compact/MCP payloads and scoped access to one synthetic README: both recovered a late constraint, rejected the wrong asset, and made the authorized proposal without clarification. These are limited synthetic observations, not proof of broad usability improvement; an earlier control also declined to invent missing information.
Related: #147. At release validation, check clipped and budget-omitted README cases across compact, hook, and MCP output, including matching coverage flags and unchanged budget/completion meanings.