open-standards/.github
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science d0b23afcba
All checks were successful
WAI conformance / does this change touch it (pull_request) Successful in 7s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 8s
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 25s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 27s
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 15s
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 1m9s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 34s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m45s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 2m0s
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 7m52s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 15m9s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 16m51s
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 49m29s
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 2m4s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 27s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 15m25s
wai-conformance: the differentials run against both builds; features-alone on linux-arm64
The last step of the independent verifiers ran differential.py, the chain and gap
differentials and `signer_verify.py verdicts` against target/debug's wai_claim_vectors,
wai_jwp_vectors and wai_signer_vectors. Each `cargo test --test` writes those copies
again (cargo builds every binary for integration tests), so the build those
differentials tested was whichever wrote last: on main, the hybrid signatures step's
`pq_signatures` build. The step's comment names the key-discovery build.

Now neither depends on build order. The first step builds the three explicitly twice:
once with the union's features (key_discovery, no pq_signatures) and once with the
hybrid signatures' features. It copies them to $RUNNER_TEMP/wai-bins/union and
$RUNNER_TEMP/wai-bins/pq, beside the other tools the steps run. The last step runs
each differential against both copies, each in its own labelled group of the log.

features-alone is a set of `cargo check` runs, so any architecture serves. It moves
from `linux`, which has a long queue, to `linux-arm64`, and stays a job of its own.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-26 06:28:35 -04:00
..
workflows wai-conformance: the differentials run against both builds; features-alone on linux-arm64 2026-10-26 06:28:35 -04:00