Phase 5: replay the core incidents, and prove each fails before its fix (hq ADR 0237) #52

2026-10-06T19:18:22Z

mesh-admin commented

2026-10-06 19:18:22 +00:00

hq to-be 45 §9 (M9), Phase 5 done-when. A Go module, replays/:

register.go: R236, R262, R263, R266, R273 — issue, fix, outcome asserted, how run.
TestReplay266… (bus): the controller's 7-filter consumer under the mesh's traffic shape, against MESH_TEST_NATS, under a prefix of its own.
TestReplay262… (resolver, musl + glibc): renders the catalogue's node-zones machine list, runs the distribution's dnsmasq with it on the default bridge, and asks every machine by getaddrinfo from python:alpine (musl) and python:slim (glibc). Docker Engine API over the socket (no CLI needed in the toolchain).
cmd/prove: each replay at fix^1 (must fail; for the gate, not build) and at the fix (must pass); the bus replay runs the very image digest the catalogue pinned at each commit.

Prover output: R236 PROVED (before: the check did not exist; on the gate: passes); R262 PROVED (before: musl fails to resolve, glibc resolves); R263 PROVED; R266 PROVED (before: 21 of 381 followed events never handed over, on 2.10.29); R273 PROVED.

The build seat runs these replays (from main) in every check (mesh-controller #96). After the controller PRs merge: set R236's Fix to #96's merge commit (drop Before) and R263/R273's HomeRef to main.

hq to-be 45 §9 (M9), Phase 5 done-when. A Go module, `replays/`: - `register.go`: R236, R262, R263, R266, R273 — issue, fix, outcome asserted, how run. - `TestReplay266…` (bus): the controller's 7-filter consumer under the mesh's traffic shape, against `MESH_TEST_NATS`, under a prefix of its own. - `TestReplay262…` (resolver, musl + glibc): renders the catalogue's `node-zones` machine list, runs the distribution's dnsmasq with it on the default bridge, and asks every machine by getaddrinfo from python:alpine (musl) and python:slim (glibc). Docker Engine API over the socket (no CLI needed in the toolchain). - `cmd/prove`: each replay at fix^1 (must fail; for the gate, not build) and at the fix (must pass); the bus replay runs the very image digest the catalogue pinned at each commit. **Prover output**: R236 PROVED (before: the check did not exist; on the gate: passes); R262 PROVED (before: musl fails to resolve, glibc resolves); R263 PROVED; R266 PROVED (before: 21 of 381 followed events never handed over, on 2.10.29); R273 PROVED. The build seat runs these replays (from main) in every check (mesh-controller #96). After the controller PRs merge: set R236's Fix to #96's merge commit (drop Before) and R263/R273's HomeRef to main.

mesh-admin added 1 commit 2026-10-06 19:18:22 +00:00

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

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.

mesh-admin merged commit 8962454530 into main

2026-10-06 19:19:21 +00:00

mesh-admin deleted branch feat/replays

2026-10-06 19:19:21 +00:00

mesh-admin commented

2026-10-06 23:10:58 +00:00

Delivery novox/mesh-lab@8962454530da — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#52 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-lab@8962454530da` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#52 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

jschoubben referenced this issue from a commit

2026-10-21 08:55:28 +00:00

Register R1439: the SDK took names with digits for secrets (issue 1439)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#52