Repository navigation
Make first-use onboarding and the developer CI decision reproducible - #3
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0xaje
marked this pull request as ready for review
October 24, 2026 14:45
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.
Add a fresh installed-wheel consumer workflow and a separate gRPC range client. The walkthrough captures a compliant baseline, a fresh unchanged request and a changed request against actual local regtest blocks. It independently checks each delivered block against the node, asserts strict policy exits and recomputes baseline regressions. Existing evidence is preserved; offline verification starts no services.
Real onboarding run 40103273814 passed: 50 actual observer events, 47 canonical block responses, baseline/unchanged PASS, changed SC-001 FAIL and one SC-005 regression. Both consumer Actions executed; the negative case required exact exit 1 plus the expected findings. The original 56,714-byte CI archive was downloaded, SHA-256 checked, revalidated and committed under examples/range-client. The second real run 40103615123 also passed with the stricter offline verifier.
All 59 local unit/boundary checks pass, including replay of original real CI evidence and rejection of edited receipts/comparisons with updated inventory hashes, unknown manifest versions and hidden extra files. Missing Docker correctly blocks with exit 2. The external client executes outside the source checkout using the clean environment's installed package.
Add copyable Windows/Bash onboarding, expected outputs, troubleshooting, manual observer/consumer Action wiring, original proof provenance and an explicitly unperformed unfamiliar-reader exercise. Update README and the video prompt around the actual developer decision. Keep this declared completed-range example separate from the funded Zingo gate and document policy exceptions and bandwidth cost. This proves automated onboarding and useful CI behavior, not independent adoption or universal privacy.