Repository navigation
Compact maintenance docs and run CI only for changed risks - #302
Merged
Merged
Conversation
HTExplicit
enabled auto-merge
October 30, 2026 18:53
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.
Changes
Maintenance documentation repeated current behavior and retained obsolete recovery and testing instructions. Compact the downstream contracts and historical reviews, add a repository-local AGENTS entry, and make the developer guide select checks for the actual change.
Replace unconditional historical CI suites with one changed-risk plan and shared execution action. Keep all ten protected check names and the existing branch protection. Unknown executable inputs fail classification; required jobs report applicable execution, verified reuse, or explicit non-applicability. Receipt reuse verifies the complete tested tree, concrete targets, workflow definitions, environment and original successful execution. Preserve upstream dispatch, the macOS shell runner, scheduled security scans, and runtime checks when their actual inputs change. Release and production workflows are unchanged.
Validation