Repository navigation
fix(jev): apply initial effort to native Chat dispatch - #6750
geunwoojun99 wants to merge 5 commits into
Conversation
Apply the existing validated first JEV decision on the native lane and handle initial null without force-default exceptions. Preserve downstream pins, caps, ordinary force validation and original-request fallback policy. Add wire regressions across the existing three backends and synchronize effort contracts. Extracted independently onto current dev without level-routing features. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (4)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe initial JEV effort decision now applies to the first native Chat and Responses Combo children. Request shaping, effort labels, fallback behavior, tests, and documentation reflect this handling. ChangesInitial JEV effort handling
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant Combo
participant JEV
participant ChildDispatch
participant Provider
Combo->>JEV: Request initial effort decision
JEV-->>Combo: Return selected effort or null
Combo->>ChildDispatch: Apply decision to first child request
ChildDispatch->>Provider: Send shaped request
Possibly related PRs
Merge Risk: ⚪ Minimal · up to Initial JEV effort, including null, is applied to the first child while downstream and later-target behavior remain intact. No actionable merge-blocking risk was found. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
✅ Deterministic PR hygiene checks passed. |
⏳ DRAFT
What to do
Review readiness checklist
0/4 boxes ticked. This PR stays in draft until every box above is ticked. |
|
@coderabbitai review @codex review The PR intentionally remains draft while independent review and broad validation are pending. |
|
To use Codex here, create a Codex account and connect to github. |
✅ Action performedReview finished.
|
Address the pre-merge docstring coverage warning without changing request behavior, test assertions, or review thresholds. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
Addressed the pre-merge docstring warning in 193b35d.
@coderabbitai review Please refresh the pre-merge docstring check for the new head. |
✅ Action performedReview finished.
|
Co-Authored-By: Claude Code <noreply@anthropic.com>
Co-Authored-By: Claude Code <noreply@anthropic.com>
Carry of #6750 onto current dev with review fixes. A validated JEV choice now owns the first native Chat dispatch, including an explicit no-effort choice; provider pins, caps and wire normalization still apply downstream, and later targets do not ask the judge again. Review fixes on top of the contributor's change: - collapse adjacent identical segments in the Combo requested-effort label, so a provider pin that kept the JEV effort no longer logs high->low->low - assert the native lane actually ran in the initial-effort wire matrix Supersedes #6750 Co-authored-by: GeunwooJun <313474999+geunwoojun99@users.noreply.github.com>
|
Thank you, @geunwoojun99! This change landed on |
Summary
Verification
[executed] Current head:
72d5fc78e4a1522014c7b6c087fb2835ad016bab. Additively merged latestdev(68c9d354574ed240c17805493409f8c589682b91); no conflicts, history rewrite, or force push. The merge brings in unrelated upstream changes (170 files changed relative to the previous head); the PR's own diff againstdevis still the same 16 files (+353/-37). Six of those 16 files (scripts/test-layout/layout.json,tests/fixtures/test-layout-expected.json, and fourstructure/documents) also gained upstream entries in the merge; the other ten are byte-identical to the previous head.[executed] Validation used checksum-verified Bun 1.4.0, an isolated clone at this exact head, private dependency copies verified with
bun install --frozen-lockfile --ignore-scripts, synthetic homes/configuration, repository preload, and bounded commands. No shared dependencies or installed runtime were modified. Documentation dependencies were independently installed with the frozen lockfile.[executed] All commands below passed. Focused wire/native/Combo regression selection: 131 pass / 0 fail, seven files (including the 42-case initial-effort wire regression). Adjacent JEV decision/provider/backend/log selection: 68 pass / 0 fail, four files. Layout/ratchet/structure/Core-Lab tests: 104 pass / 0 fail, five files. Counts describe separate selections, not full-suite coverage.
[executed] The adjacent selection is exactly the four existing files listed above; the earlier non-existent
tests/routing/jev-service-exchange.test.tsargument was dropped, and no exchange-test coverage is claimed. Production typecheck and both additional CI TypeScript compiler configurations passed using the locked compiler. Both Bun-hosted and supported-Node documentation builds passed: 569 pages / 79,215 internal links.[not checked] Full
bun run testand import-connectedbun run test:changedwere not run. Under the explicit AGENTS.md/CONTRIBUTING.md resource exception, focused real-wire regressions plus adjacent routing/logging and source-oracle guards were used: the checkout has over 2,000 tracked test files and this environment is shared with concurrent agent/runtime work. A full run is disproportionate for this two-production-file fix in that shared environment. Remaining coverage includes unrelated/import-connected regressions, full wrapper orchestration, and cross-platform execution; these remain for hosted CI, not claimed passing.[executed] Review inspection found zero review threads, no actionable CodeRabbit findings, and 100% docstring coverage on
193b35db5e31f034deec6825ea1acfae8eca4df0(CodeRabbit summary comment #6750 (comment)). CodeRabbit's summary comment covers a1dd3cd..72d5fc7: the recent review (after which CodeRabbit auto-paused reviews on this PR) reports no actionable comments, and 5/5 pre-merge checks passed, including docstring coverage 100%. The additive base-only refresh does not alter that feature diff (re-checked: same 16 files). All known correct findings are addressed. [not checked] Independent Codex approval is not claimed.[code read] Readiness gate source treats local validation as an author attestation with the documented full-suite exception; recent-dev means at most ten behind; findings means no unresolved correct bot findings; the final box confirms review readiness. Hosted CI approval is not a prerequisite for these boxes, but successful required current-head CI remains mandatory before merge.
[executed] At the current head
72d5fc7, PR hygiene passed. Administrative gates re-run on each push and body edit, and some runs are cancelled and superseded; their live state is the source of truth, and no result is claimed for runs still queued. [not checked] Cross-platform CI and React Doctor reportaction_requiredawaiting workflow approval, not passing runtime validation, so no runtime-CI result is claimed. This is ready for review, not merge approval. No merge was performed.Checklist
Review readiness checklist
This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:
Required local validation passed; commands, results, and any full-suite exception are documented.
I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
I resolved all correct Codex and CodeRabbit findings.
My PR is ready for review.
Summary by CodeRabbit
🤖 Generated with Claude Code