Repository navigation
Make smart-routing reasons easier to read - #1177
Merged
Merged
Conversation
JJ27
marked this pull request as ready for review
October 16, 2026 22:49
JJ27
force-pushed
the
JJ27/readable-routing-reasons
branch
from
October 16, 2026 22:59
6da31c4 to
7164168
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.
What did you change, and why?
Translate existing task profiles into short routing explanations, addressing this review feedback. For example,
Routed to Low because its task-only profile is low: ...becomesThis task has a clear target and limited scope.Preserve availability and fallback explanations, custom gateway notices, and unrecognized responses. Diagnostic records keep the displayed explanation inrationaleand the original gateway text inraw_rationale.How do you know it works?
Two direct formatter tests cover readable wording and preservation of unknown responses. All 217 focused routing and integration-contract tests pass. A direct filesystem check verifies both diagnostic fields for summarized, unchanged, and empty reasons. Ruff lint, formatting, and type checks pass. The live integration checks will rerun in CI.