chore: move heavy verification to GitHub - #14
Merged
Conversation
Make GitHub-hosted runners the default for resource-heavy gates, prevent superseded workflow duplication, and require bounded monitoring plus phase-boundary process and artifact cleanup. Add a narrow idempotent local cleanup command and persist the policy in project instructions and skills.
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.
Outcome
tools/clean-local.shcommand for known reproducible build, toolchain, and Python cache pathsAGENTS.md, both project execution skills, and engineering handoff guidesLightweight local validation
proceed-projectvalidverify-projectvalidHeavy validation
The GitHub-hosted four-preset matrix on this exact commit is the completion gate.