Repository navigation
Identify installed capabilities and pin generated CI source - #51
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.
Consumer CI defaults to the published npm0.1.0 while current source includes later features. Add content-free installed build/capability inspection and an optional GitHub source channel pinned to a full reviewed commit; build and verify that identity before running verification. Keep default plan mode, the published pin and existing SARIF behavior; protect generated files against concurrent overwrite and links. No package publication.
Validation: 770 tests passed,1 existing optional Docker reference skipped; type-check, lint and build passed. Actual local tarball install matched its frozen source; executed the generated shell steps against the pinned remote commit, built it and produced SARIF. Also installed the real published npm0.1.0 consumer and produced SARIF; local candidate JUnit passed. All verification exits0, Skill script executions0 and report uploads0. Native shell evidence is macOS/Node24; hosted Linux CI remains separate.