Summary
In scripts/ci/classify-changes.sh, the crates/graphforge-api/* | crates/graphforge-bindings-py/* | crates/graphforge-bindings-node/* arm precedes the Bazel-mapped test-data arm (crates/*/tests/*goldens/*, **/*.snap, fixtures, corpus). A change such as crates/graphforge-api/tests/fixtures/x.json currently sets only bindings=true and skips the authoritative Rust/Bazel suite.
Acceptance criteria
Non-goals
- Broader classifier redesign
- Suite-membership / pin / timeout work
Source
Devinfra Audit Recheck Wave E / PR-C
Validation
bash scripts/ci/test-classify-changes.sh
Summary
In
scripts/ci/classify-changes.sh, thecrates/graphforge-api/* | crates/graphforge-bindings-py/* | crates/graphforge-bindings-node/*arm precedes the Bazel-mapped test-data arm (crates/*/tests/*goldens/*,**/*.snap,fixtures,corpus). A change such ascrates/graphforge-api/tests/fixtures/x.jsoncurrently sets onlybindings=trueand skips the authoritative Rust/Bazel suite.Acceptance criteria
rust=trueandbazel=truebindings=truewhen appropriate (binding suites may consume it)scripts/ci/test-classify-changes.sh(at leastcrates/graphforge-api/tests/fixtures/x.json→ rust+bazel)Non-goals
Source
Devinfra Audit Recheck Wave E / PR-C
Validation
bash scripts/ci/test-classify-changes.sh