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]>
19 lines
1.2 KiB
Shell
19 lines
1.2 KiB
Shell
# step: end-to-end encrypted rooms · e2ee_verify.py
|
|
# order: 650
|
|
# paths: wai/extensions/confidentiality.md
|
|
# independent: e2ee live python3 -I live-conformance/e2ee_verify.py live-conformance/e2ee
|
|
#
|
|
# wai.live.e2ee (extensions/confidentiality.md): the corpus's second implementation,
|
|
# e2ee_verify.py, written from the extension's text and the documents it reads and
|
|
# sharing no code with the reference (joule-moq's secure_objects and joule-moq-mls,
|
|
# whose own checks run in joule-code-conformance.yml). Standard library only, run
|
|
# isolated (-I): AES, AES-GCM and RFC 9605's counter mode written from their
|
|
# specifications for test vectors only, HKDF and HMAC from the standard library,
|
|
# BLAKE3 and strict Ed25519 from claim-conformance. It checks every vector RFC 9605
|
|
# and draft-ietf-moq-secure-objects-01 publish, every record, key schedule, sealed
|
|
# object and room of vectors.json (taking each epoch's application secret as given,
|
|
# §14), and requires every mutated copy of the corpus to fail.
|
|
#
|
|
# The paths this step brings to the workflow's trigger, and why:
|
|
# wai/extensions/confidentiality.md: e2ee_verify.py reads this extension's §13 table, and the
|
|
# registry's wire identifiers test reads its sections.
|