Repository navigation
[CI-01] Select docs and affected package checks with an explicit CI gate - #598
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.
Documentation PR #596 ran all eight Rust/Python/platform jobs; backend-local edits also ran whole-workspace suites. This PR implements both parts of #597 together: a hosted docs-only route and dependency-aware package/consumer checks, with a versioned plan and always-evaluated
ci-requiredgate.Refs #597. Both implementation stages are in this one PR. Post-merge hosted timing/queue qualification remains explicitly unmeasured; the issue should stay open until those operational receipts are collected. No separate implementation PR is required.
The planner uses complete NUL-delimited Git diffs and locked Cargo metadata (including dev/build/optional/target consumers). Config/unknown changes fall back to full; main code pushes and nightly/manual audits stay full. Metal/CUDA plans include feature-enabled CLI/Python consumers; connected CPU/QEC/oracle changes legitimately stay broad. RTL is a selected reusable workflow with separate concurrency, avoiding redundant docs-main runs. Forks use hosted runners with fixed label choices and read-only credentials. Beta rows explicitly block the aggregate, matching the prior manual all-success policy.
Consumer validation caught an existing Metal CLI compile error: the parse-time argument was missing after the shared executor signature changed. Forward it through the Metal wrapper/stub (4 lines); no optimizer/kernel change or deferred #551 work is included.
Validation: 15 planner/gate/docs/security contracts (including >300 files, rename/deletion/symlink cases, real PR/push histories with an unusable Cargo executable, failed planning and selected-job failures); actionlint; 78 CLI tests; Metal-enabled CLI and Python consumer checks; workspace and Metal CLI all-target Clippy; rustfmt; changed local docs/JSON/checksum checks. Historical #596 diff replays to docs-only; focused backend/shared/config controls are retained with source fingerprints in docs/perf/data/ci-01/.
This policy-changing PR selects the full matrix. No hosted speedup or new physical GPU result is claimed from local routing/compile checks. The previous fixed eight/nine-check monitors are not waived retroactively, repository protection/settings and release/timed-benchmark policy are unchanged. Manual self-review found no remaining blocking findings; the current GitHub run must validate workflow integration before acceptance.