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]>
22 lines
1.4 KiB
Shell
22 lines
1.4 KiB
Shell
# step: live events · wai-rs and live_events_verify.py
|
|
# order: 100
|
|
# features: live_events
|
|
# paths: wai/extensions/live-events.md
|
|
# independent: live-events live python3 -I live-conformance/live_events_verify.py live-conformance/events
|
|
#
|
|
# wai.live.events (extensions/live-events.md): the reference module's unit tests and
|
|
# tests/live_events.rs (the committed corpus regenerates byte for byte from its fixed
|
|
# seeds, wai-rs gives every vector, policy case and binding case its stated outcome,
|
|
# the corpus covers every kind and reason, and §9 lists exactly the reference's
|
|
# codes); and, in the step of every independent verifier above, the corpus's second
|
|
# implementation, live_events_verify.py, written
|
|
# from the extension's text and sharing no code with wai-rs, which verifies the same
|
|
# cases with WAI's strict Ed25519 (claim-conformance/_ed25519.py) and BLAKE3
|
|
# (claim-conformance/_blake3.py), standard library only, run isolated (-I).
|
|
#
|
|
# The paths this step brings to the workflow's trigger, and why:
|
|
# wai/extensions/live-events.md: tests/live_events.rs requires this extension's §9 to list the
|
|
# codes the reference reports, 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 live_events::)
|
|
(cd wai-rs && cargo test --no-default-features --features "$WAI_FEATURES" --test live_events)
|