Repository navigation
feat(judge): per-node input cap, body trimming and missing-context - #166
Merged
Merged
Conversation
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 04:01
ce98970 to
3d597d9
Compare
mindsocket
force-pushed
the
issue-152-trim
branch
4 times, most recently
from
October 16, 2026 04:20
1644ab5 to
3c68fbd
Compare
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 04:46
6513f49 to
bd0038e
Compare
mindsocket
marked this pull request as ready for review
October 16, 2026 05:31
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 05:49
bd0038e to
26d9333
Compare
…rdict Cap one node's input (node plus related nodes) at 32k estimated tokens for every provider. Over the cap, cut related bodies by water-filling, then the evaluated node's body, ending each cut at whitespace with a [RULE_EVALUATION_CONTENT_TRIMMED n chars] marker. Input still over the cap reports a semantic evaluation error and skips the provider. Rules with semantic.scope or includeContent offer missing-context (warning by default). The validate summary and JSON report trimmed nodes and rules. Rename the Jev packing constants to request packing limit.
Adds a test that scans README, AGENTS, CLAUDE, top-level docs and plugin markdown for backticked repo paths and fails on any that do not resolve. Lines containing an example marker (e.g., eg, example) are skipped, as are placeholders and gitignored paths. Fixes the four stale paths it found.
Drop request grouping, packing and trimming mechanics from config.md and semantic-rules.md. Keep what a user acts on: that grouping saves cost and can shift verdicts, the per-node input cap, the trim marker and the errors.
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 05:56
26d9333 to
9958ed4
Compare
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 06:03
9958ed4 to
65e8415
Compare
mindsocket
force-pushed
the
issue-152-trim
branch
from
October 16, 2026 06:14
65e8415 to
2420e40
Compare
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.
Closes #152. Stacked on #165.
Summary
[RULE_EVALUATION_CONTENT_TRIMMED <n> chars].(Semantic evaluation error: input over the per-node cap after trimming content)for that node.missing-context: a reserved verdict, offered on every rule withsemantic.scopeorincludeContent. The model is told to use it only where a trim marker shows content was cut. Its default severity iswarning, andsemantic.severitycan override it.sctx validateprints "Context trimmed for N node(s) across rules X, Y." The result carriescontextTrimmedtoo. This is an additive public API field onValidationResult, agreed.docs/concepts.md. The Jev constants are renamed toJEV_REQUEST_PACKING_LIMIT_*.Tests
lint and typecheck clean;
bun run test779 pass, 15 skip, 0 fail. One shared test checks that all three renderers show the relation, the trim marker andmissing-context. No live test yet sends a scoped, over-cap node to a real provider.