fix(recall,guard): actionable truncation markers; truncated demanded reads keep the gate armed (#239) - #248
Conversation
…reads keep the gate armed (#239) The marker now names the note and the exact recall-note follow-up call; a guard-demanded note that comes back truncated records as an incomplete consult that _has_consulted_git_rules refuses to credit, with the fix printed verbatim. Deterministic un-wedge: truncated:false, a section drill-down, or max_chars at the 8k API cap always counts. Non-demanded reads are never touched. Closes #239 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 29 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (9)
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 |
Implements #239 as specced: actionable marker in
compact_recall(names note + exactrecall-notecall), incomplete-consult tracking in guard (per-turn, cleared at turn start), detection inverify_consultoff the demanded-note path only, fail-open on any parsing surprise. Guard block message now asks formax_chars: 8000up front. Tests cover armed-until-full-read, the max_chars un-wedge, and non-demanded reads being untouched. 946 passed; ruff clean. Version 8.3.2.Closes #239
🤖 Generated with Claude Code