ci: Go build/vet/test + Python conformance gate#4
Merged
NetworkTheoryAppliedResearchInstitute merged 1 commit intoJul 13, 2026
Conversation
Two jobs on every PR and push to main: - test: gofmt cleanliness, go vet, go build, full go test (includes the vectors golden test, so any canon or field-order drift fails CI). - conformance: run testdata/reproduce_spec.py (stdlib-only Python, written from SPEC.md alone) against testdata/vectors.json. An independent implementation must reproduce every canonical byte sequence and verify every signature, or the build fails. This is the forkability guarantee executed as a check, not a promise. Least-privilege permissions (contents: read) per the CodeQL guidance already applied to SoHoLINK's workflow. Signed-off-by: Jodson Graves <info@ntari.org>
This was referenced Jul 10, 2026
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.
Adds the missing CI to the protocol repo (flagged 2026-07-09: two consumers, zero checks).
Two jobs on every PR / push to main:
go vet,go build, fullgo test ./...(includes the golden-vectors test, so any canon or field-order drift fails the build).testdata/reproduce_spec.py(stdlib-only Python, written from SPEC.md alone) againsttestdata/vectors.json; exits non-zero on any byte or signature mismatch. The forkability guarantee executed as a check: a non-Go implementation must always be able to reproduce our bytes from the spec.Least-privilege
permissions: contents: read.Suggested merge order: this PR FIRST, then #3 — that way the v0.2.0 wire change gets CI checks on its next synchronize. After both: tag v0.2.0.
Follow-up for repo admin (not in this PR): mark the two checks required in the ruleset once they've run green on main.
🤖 Generated with Claude Code