Replay the core incidents, and prove each fails before its fix and passes on it (hq to-be 45 §9)

Phase 5 is done when the replays of 236, 262, 263 and 266 fail on the commit before their fix and
pass after. The register names every replay with its issue and fix; the bus replay (266) runs a
consumer filtered like the controller's against a bus of a given release, the resolver replay (262)
renders the catalogue's machine list and asks every machine's name by getaddrinfo under musl and
glibc, and the prover runs each at both commits: all five (236, 262, 263, 266, 273) proved.

README.md

@@ -406,3 +406,20 @@ That suite earned itself on its first run: it found that a snapshot of a running
 miss a file written seconds earlier — not stale, **absent** — because the write was still in
 the guest's page cache. The design had listed that as an open question. The test answered it,
 and `snapshot` now flushes first.
+
+## The replays (`replays/`)
+
+Every core incident, replayed (novox/hq to-be 45 §9, M9) — in Go, a module of its own. `register.go`
+names each replay, its issue, its fix and how it is run; a replay of one component's logic is a test in
+that component's repository (the controller's `replays_test.go`), and a replay of what the mesh runs —
+the bus server's release, the resolver the catalogue configures under musl and glibc — is here.
+
+```
+cd replays
+MESH_TEST_NATS=nats://… go test ./...       the bus and resolver replays (the resolver's needs a container runtime)
+go run ./cmd/prove [R262 …]                 each replay on the commit before its fix (must fail) and on it (must pass)
+```
+
+The prover finds the core repositories beside this one, as the beds do. The build seat runs the bus and
+resolver replays before every core and catalogue merge, against the bus of the release the mesh runs and
+the change's own catalogue.