docs(reference): document the advisor route type in the TOML schema - #625
Conversation
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe documentation adds the ChangesAdvisor Route Documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This change documents advisor-route configuration and session-scoped review-budget fallback behavior. No current merge-readiness risk remains. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
Signed-off-by: zengyuanl <zengyuanl@nvidia.com>
What
advisorsection to the TOML schema reference: every other route type (noop,passthrough,random,prefill_router,llm_classifier,stage_router,composite) was already documented there, but the advisor review gate's keys were not.proxy_x_session_idheader, then the session id resolved from harness headers, then one scope per server), and the page previously omitted the middle tier.Why
The advisor route is configured through the same TOML deployment file as every other route type; operators looking up keys in the schema reference found nothing for it. Key names, defaults, and validation rules in the new table were verified against
AlgorithmSpec::AdvisorandAdvisorGate::new.Validation
cd docs && make publish(strict MkDocs build) passesuv run ruff check .anduv run pytest tests/pass🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
advisorrouting mode, which can review terminal or pattern-matching turns, approve output, or request a retry with feedback.Documentation