### Every `wai.quantum.*` string is registered, listed with what it names, or a schema's name

- **The registry lists the quantum labels no revision registers**
  ([REGISTRY.md](REGISTRY.md)). Beside the receipt kinds wai-quantum seals, its unregistered
  labels now hold the modules of wai-quantum (`wai.quantum.toolchain`, the
  `wai.quantum.cal.*` family and the rest), the names a record's members carry, the kernels
  and corpora a fabric member's certificate names (`wai.quantum.circuit/apply`,
  `wai.quantum.sv/run-wide`), the revision a circuit contract names in its `ext`
  (`wai.quantum.circuit2/1`, quantum-sim §2.1), the documents the quantum crates write that
  have no schema file, the domains a digest starts with, and the strings the tests and the
  provider conformance corpus give a reader to see it refuse them. Each says what it names,
  in a group of the strings it is like.
- **A document's name is its schema file.** `wai.quantum.<document>/<major>` is accounted for
  when a quantum crate keeps its schema as `schemas/<document>.v<major>.json` with that name
  as its `title` (wai-quantum/VERSIONING.md), and so is a name such a schema gives as the
  `const` of a member, so a new document adds its file and no line in the registry.
- **CI: the repository checks fail on a string not accounted for.**
  `scripts/check-wai-quantum-names.py` reads the registry export and the schema files, and
  every text file but the changelog, and names the file and line of a `wai.quantum.*` string
  neither accounts for, a `wai.quantum.<prefix>.*` pattern that matches none, a schema file
  whose `title` is not the name its file name gives, a quantum label nothing outside the
  registry uses, and a string the registry holds twice. Its self-test plants each in a
  scratch repository and requires the check to fail, naming it.
