417847daab
The change of wai/conform-output, on current main, without its wai doctor: main's doctor, its tests, its catalogue entry, its MCP tool and its changelog entry stand as they are, and this change's copies of them are gone, with the lines dev.rs held for them. wai/README.md, which had no line for main's doctor, gains one in its first commands and `toolchain_doctor` in the core tools. - wai conform --format text|json|junit|html, reports made from the signed records. - --independent beside a kind holds the corpus's independent verifier to the same cases; alone, it runs every corpus's verifier, a record each, from one table. - wai-rs/build.rs reads that table from the `# independent:` lines of the step files (.github/wai-conformance/verifiers/), which take the verifiers' command lines out of the steps' bodies. scripts/wai-conformance-lists.py reads and checks the same lines. - wai-conformance.yml runs the union as wai conform --independent --format junit. - wai mcp's conformance tools read the table. - wai-release.yml runs the quickstart from each archive as a new user runs it (clean-machine.sh, its PowerShell twin clean-machine.ps1), held by check-wai-release-quickstart.py. clean-machine.ps1 keeps clean-machine.sh's contents step and its check of WAI Studio. Each leg keeps main's archive_doctor.py check; the step's own wai hello, verify and dev --check are clean-machine.sh's now. - check-wai-ops-doors.py reads VERBS and NEAR_SYNONYMS from catalogue.rs and keeps no list, and the verb-list test reads what that check reads. - The catalogue's export and Studio's actions hold the new operations. Co-Authored-By: Claude Opus 5.5 <[email protected]>
30 lines
2 KiB
Shell
30 lines
2 KiB
Shell
# step: delivery settlement · wai-rs and settlement_verify.py
|
|
# order: 390
|
|
# features: settlement
|
|
# paths: wai/extensions/settlement.md
|
|
# independent: settlement live python3 -I live-conformance/settlement_verify.py live-conformance/settlement
|
|
#
|
|
# wai.delivery.settlement (extensions/settlement.md): the reference module's unit tests
|
|
# (range proofs over every range around every chunk boundary of objects of many lengths
|
|
# against BLAKE3's own root, tampered proofs refused, the group tree of jwp-receipts §2.2,
|
|
# records and item lists read and refused, amounts rounded down per line) and
|
|
# tests/settlement.rs (vectors.json regenerates byte for byte from its fixed seeds and no
|
|
# other file is there, wai-rs gives every statement and range proof its stated outcome, §11
|
|
# lists exactly the reference's codes, each of which the corpus gives, beside every code it
|
|
# reuses); and, in the step of every independent verifier above, the corpus's second
|
|
# implementation, settlement_verify.py, written from the
|
|
# extension's text and sharing no code with wai-rs, which verifies range proofs over
|
|
# BLAKE3's chunk tree with claim-conformance's BLAKE3, reads rooms, grants and proofs with
|
|
# live_rooms_verify.py and per-hop records with live_metering_verify.py, checks signatures
|
|
# with WAI's strict Ed25519 rule, recomputes every figure of every statement, reads the
|
|
# extension's reason table, requires every mutated copy of the corpus to fail, and drops
|
|
# each of its own checks in turn and requires the corpus to catch the weakened verifier;
|
|
# standard library only, run isolated (-I).
|
|
#
|
|
# The paths this step brings to the workflow's trigger, and why:
|
|
# wai/extensions/settlement.md: tests/settlement.rs requires this extension's §11 to list the
|
|
# codes the reference reports, settlement_verify.py reads that table, and the registry's wire
|
|
# identifiers test reads its sections.
|
|
set -euo pipefail
|
|
(cd wai-rs && cargo test --no-default-features --features "$WAI_FEATURES" --lib settlement::)
|
|
(cd wai-rs && cargo test --no-default-features --features "$WAI_FEATURES" --test settlement)
|