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]>
29 lines
2 KiB
Shell
29 lines
2 KiB
Shell
# step: fleet · wai-rs and fleet_verify.py
|
|
# order: 440
|
|
# features: fleet
|
|
# paths: wai/extensions/fleet.md
|
|
# independent: fleet live python3 -I live-conformance/fleet_verify.py live-conformance/fleet
|
|
#
|
|
# wai.delivery.fleet (extensions/fleet.md): the reference module's unit tests (the enrolment's
|
|
# rules, a summary line split only in the relay's form, a row summed across classes told from
|
|
# a wrong one, the four coverages) and tests/fleet.rs (vectors.json regenerates byte for byte
|
|
# from its seeds and the metering corpus and no other file is there; wai-rs gives every
|
|
# vector its stated outcome; every reason of §10 and every reused code refuses a vector; the
|
|
# accepted vectors state measured, unmetered and partial energy as §5.4 does; the week's
|
|
# records held as a service holds them sign the corpus's report byte for byte; §10 lists
|
|
# exactly the reference's codes); and, in the step of every independent verifier above, the
|
|
# corpus's second implementation, fleet_verify.py,
|
|
# written from the extension's text and sharing no code with wai-rs, which reads per-hop
|
|
# records with live_metering_verify.py, checks every signature with WAI's strict Ed25519
|
|
# rule, recomputes every line, row, unmetered count and citation, 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
|
|
# service and its smoke checks over HTTP run in wai-fleet.yml.
|
|
#
|
|
# The paths this step brings to the workflow's trigger, and why:
|
|
# wai/extensions/fleet.md: tests/fleet.rs requires this extension's §10 to list the codes the
|
|
# reference reports, fleet_verify.py reads that table, and the registry's wire identifiers test
|
|
# reads its sections. Its corpus is generated from the metering corpus, under the paths above.
|
|
set -euo pipefail
|
|
(cd wai-rs && cargo test --no-default-features --features "$WAI_FEATURES" --lib fleet::)
|
|
(cd wai-rs && cargo test --no-default-features --features "$WAI_FEATURES" --test fleet)
|