feat: consume gates in advance-pipeline smoke path - #27
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.
What
Adds the first gate-consuming
scripts/advance-pipeline.pyimplementation and a greenfield smoke fixture.Why
Completes the next M6/M5 slice after PR #26: gates now have a script consumer, and
examples/greenfield-cli-toolproves a RESEARCH to SPEC transition updates bothSTATE.jsonandSTATUS.md.How
STATE.json,STATUS.md,templates/gates/<phase>.yaml, and.sdd/gates/<phase>.jsonevidence.STATE.jsonand appends aSTATUS.mdhistory row on pass.BLOCKEDafter repeated gate failures.tests/scripts/and a greenfield example fixture.Scope check
tests/scripts/Notes
Local shell commands are still blocked in this environment by
bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted, so validation is expected from CI.