Repository navigation
docs(v1): make stable @v1 the default for all new consumers - #188
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.
Scope and user intent
ExecSurface v1.0.0 is already published and qualified within its documented Linux x86_64/native-ptrace boundary. New customers should install and integrate this stable release, not Alpha.5/Alpha.6. The historical Alpha.5 recipe contributed in #128 remains immutable, properly scoped and credited; no stale test receipt has been re-labeled as a v1 test.
Changes
examples/github-action-consumer-v1.yml, usingAETHERXGLOBAL/execsurface@v1, independent native target-success gate, fail-on-review, read-only permissions, checkout credentials disabled, default no-public-evidence-upload, and mandatory externally trusted baseline/policy digest pins.@v1binary/Action across PASS, REVIEW, BLOCK, ERROR, pins policy and baseline, and checks baseline immutability. Must actually run before qualification, not just be named.examples/README.mdprominently directs users to v1 and makes the Alpha.5 Python/pytest contribution explicitly historical. Original independent contributor @astrogilda retains credit and frozen evidence.Gates (open until verified)
PASS / REVIEW / BLOCK / ERRORand correct target-verdict semanticsThis PR changes only onboarding docs, user examples and self-contained qualification tests; stable binaries, release tags and security claims are unchanged.