RT-184 (rt half): gate option descriptions and per-question context - #299
Merged
Merged
Conversation
…zation Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…xt under one context budget Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…batim passthrough Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… the input schema Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…to list --json Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 13 minutes. View limit detailsLimit details: You’ve used the included review currently available. Your 80 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (12)
Comment |
…ped gate context contextOmitted covers two different drops: the gate context itself over budget, or only the question contexts pushing the shared budget over (RT-184). The guard exempted on either, so a human-owned, non-exempt-kind gate with no gate context and oversized question contexts opened with no material anywhere instead of being refused. Only a dropped gate context now exempts the guard. RED: a new case in gate-ask-handler.test.ts (no gate context, non-exempt kind, question contexts alone over budget) failed before this change, matching a live probe against the PR head (contextOmitted: true, context: null, ok: true where it should have been refused). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
m4ttheweric
added a commit
that referenced
this pull request
Sep 17, 2026
…299) * rt-client: gate options carry an optional description through normalization Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * rt-client: GateQuestion carries an optional per-question context Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * gate:open/gate:ask: accept option descriptions and per-question context under one context budget Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * rt gate ask/list: pin option descriptions and question context as verbatim passthrough Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * mcp gate_ask: document option description and per-question context in the input schema Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * e2e: gate ask round-trips option descriptions and question context into list --json Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * gate:ask: exempt the human-owned MISSING_CONTEXT guard only on a dropped gate context contextOmitted covers two different drops: the gate context itself over budget, or only the question contexts pushing the shared budget over (RT-184). The guard exempted on either, so a human-owned, non-exempt-kind gate with no gate context and oversized question contexts opened with no material anywhere instead of being refused. Only a dropped gate context now exempts the guard. RED: a new case in gate-ask-handler.test.ts (no gate context, non-exempt kind, question contexts alone over budget) failed before this change, matching a live probe against the PR head (contextOmitted: true, context: null, ok: true where it should have been refused). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <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
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.
🤖 Generated with Claude Code