test(routing): run full benchmark through Bash router - #69
Merged
dhicoc merged 1 commit intoAug 11, 2026
Merged
Conversation
Collaborator
|
本地合并流程已完成:
说明:本机 Windows 无系统 Bash, |
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
The repository has two independent structured-router entrypoints that both read the same
routing.jsonSSoT:master-route.ps1master-route.shThe PowerShell path already runs the full 163-case
routing-benchmark.jsonin CI, while the Bash path currently checks only three hand-picked routes. That leaves room for semantic drift in Bash routing even when the shared route table itself is correct.This PR keeps the change test-only and bounded:
skills/scripts/test-routing.sh, which runs every case from the existingrouting-benchmark.jsonthroughmaster-route.shand compares the emittedprimaryroute with the shared expected value;case-init/case-guardregressions unchanged;Why
A recent macOS compatibility fix showed that the Bash path can fail independently of the PowerShell path. Running the same routing benchmark through both entrypoints turns the existing JSON benchmark into a true cross-entrypoint contract instead of validating only the PowerShell implementation.
Validation
The new runner is wired into the existing Ubuntu
sh-syntaxjob. It uses the same Python 3 dependency already required bymaster-route.shand reads the existing UTF-8 benchmark directly.Expected CI contract after this change: