feat(ai): make adaptive orchestration the planning default - #529
feat(ai): make adaptive orchestration the planning default#529seonghobae wants to merge 25 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. 📝 WalkthroughWalkthroughProduction planning-analysis 요청이 Changes자동 오케스트레이션 기본값
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change makes adaptive orchestration the planning default while preserving the existing transport and validation behavior; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|
@coderabbitai review |
|
|
@coderabbitai review |
|
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
@opencode-agent review Please submit a formal review for exact current head |
|
@coderabbitai review |
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Superseded by the older canonical transport owner in #496 after exact overlap analysis. Both PRs independently modified the same Unique #529 behavior has been preserved on #496's current combined line rather than discarded:
The preserved combined owner is #496 head |
Summary
orchestration_mode: "auto"from the current protected-developcontextual-orchestrator client;SCOPEWEAVE_DEV=1development-only deterministic adapter;CHANGELOG.md.TDD and branch safety
The original feature branch was two protected-
developcommits behind and contained a branch-local self-modifying workflow that staged tests, mutated source, deleted itself, and pushed with write credentials. Continuing from that stale tree would have overwritten already-shipped orchestrator hardening. The unsafe workflow and helper scripts were removed, its old run31945254038completed as failed, and the branch was reconciled non-destructively with protecteddevelop@28420da358f57be5e85be3660251e39b85e1cc94before product work resumed.On the reconciled current-base code:
177e2a12e1f6be32c5a9b91379f92cf1170a71c8updates the existing canonicaltests/unit/orchestrator.test.mjsrequest-body expectation to requireorchestration_mode: "auto".5a6afdd9f26994987e3d9ba3b85a8dd95f06a7e7adds only that field to the existing validated production request body.Dependency contract
The current protected
ContextualWisdomLab/contextual-orchestratormainrevision verified for this change is6841b71935e0b7cb98fb52bcb4709cc5100c8d87. Its/v1/chat/completionscontract acceptsorchestration_modeand currently permitsauto,route, andconduct. ScopeWeave selectsautobut does not freeze or claim a particular provider, worker count, topology, verifier strategy, or cost heuristic; those remain contextual-orchestrator authority.Verification
Exact-current-head CI/security/review evidence is authoritative. Predecessor-head successes are not carried forward. The PR must not merge until all applicable current-head required checks, security/review gates, unresolved-thread requirements, and qualifying independent approval required by live repository governance pass on the unchanged head.
Summary by CodeRabbit
새 기능
auto오케스트레이션 모드를 사용하도록 개선되었습니다.문서
테스트
auto모드가 포함되는지 검증하도록 테스트를 보강했습니다.