fix(routing): research before classifying subagent work - #53
Merged
Merged
Conversation
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
Follow-up to #52. The routing prompt previously treated uncertainty as difficult work, and missing classification metadata automatically selected Astra High. Require bounded research and focused clarification before classification, and assess reviewers independently from the completed diff and risk.
Default
uncertain_tiertoinherit: unclassified calls receive no model override or routing state. Preserve explicit choices, classified reviewer floors, model mappings, escalation limits, and existing explicitly configured tier fallbacks. Document how existing installations migrate their private policy and preserve custom app adapters.Validation
python3 scripts/validate_repo.pyquick_validate.py— not applicable; no skills changed.Additional checks:
ResourceWarningtreated as an error.git diff --check: passed.Safety and scope
No main-session model, permissions, or model-tier mapping changes. Inheritance leaves native model resolution intact and does not guarantee a cheaper model. Existing private YAML files must opt into
uncertain_tier: inherit; existing explicit fallback tiers remain compatible. Local app-adapter changes are outside this PR. Runtime activation and actual child-model selection are not tested by this repository change.Rollback: revert this PR or retain an explicitly configured fallback tier in the private policy.