feat(gui): add routing profiles and why-this-route views - #1018
Draft
Wibias wants to merge 12 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Collaborator
Author
|
RI-10 UI screenshot (attached) |
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.
Summary
RI-10 - the final PR of the Router Intelligence / Routing Control Plane
programme. Adds the dashboard surfaces (routing profiles, dry-run
evaluation, routing analytics, why-this-route in the Logs detail) plus the
documentation set across all locales.
GUI surfaces
#routing,gui/src/pages/RoutingProfiles.tsx):limits, unknown-evidence policy;
POST /api/routing-profiles/dry-runwith a candidate/eligibility/exclusions/score table - the selected candidate is marked;
/api/routing-analytics: requests, successand fallback rates, p50/p95/p99, cooldown failures, confidence, explicit
truncated-history indicator, and the provider/model breakdown.
trace inline (route kind, profile + revision, selected candidate + reason,
candidate eligibility marks); pre-trace rows show an honest empty state.
evidence exists, and the analytics panel carries the confidence label.
the
TKeyset is compile-checked.aria-pressed, keyboard-operableprofile selection.
Docs
reference/configuration/routing.md(all five locales) now covers:routingProfilesschema, alias/collision rules, dry-run + evaluate CLI,the combos-vs-profiles distinction, the request-history/routing-analytics/
route-decision APIs, and migration notes (disposable index, no
auto-tuning).
Design notes
.page-head,.panel,.card,.badge,.btn,.table); no enterprise redesign.styles.css):.tableand.checkboxfollow theexisting
.tblgrammar.Privacy / security
credentials, or raw responses.
bun run privacy:scanpasses.Compatibility
/api/*contractsunchanged.
Dependency
feat(routing): add cost-aware policy scoring and limits #1015, feat(control-plane): expose route decision explanations #1016). Branch base:
feat/ri-09-route-explainability-apihead6e69a4a68.Non-goals
Local verification (exact)
bun x tsc --noEmit-> PASSED (0 errors)bun run lint:gui-> PASSED (0 errors)bun run build:gui-> PASSED (production build + prepare:package)bun run test(12 routing suites) -> 258/258 passbun run privacy:scan-> passedbun run build-> 216 pages, PASSEDreal profile + history (see top of this description)