fix(router): stop bare 'review' from forcing research routing - #81
Merged
Conversation
A lone "review" token in research keywords was enough to reclassify software/PR work as research and switch Dorry off GPT-5.6 Sol onto GLM. Disambiguate the overloaded keyword: - software/PR/security/CI collocates attribute "review" to code - literature/paper/evidence collocates keep research - bare/ambiguous "review" no longer scores either lane Parity fix lands in both the OpenClaw TS classifier and Hermes Python adapter, with focused regressions covering the live incident shape.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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
reviewkeyword so software/PR/security review no longer routes as research.review.Why
Live Dorry incident: a PR-status reply containing “review” was classified
zeroapi:research:keyword:review, switchedgpt-5.6-sol → glm-5.2, then later fell back to Grok after Z.AI 429. That first hop was a bad route decision, not a GPT outage.Test plan
npm --workspace zeroapi test -- __tests__/classifier.test.ts(30/30)python3 -m unittest discover -s integrations/hermes -p 'test_router.py'(54/54)npm run test:hermes(237/237)npm run test:plugin(319/319)code, bare review →default, literature review →research