This adds R341 to replays/register.go, the replay of novox/hq issue 341 under ADR 0323.
Kind: InRepository in mesh-controller, ./internal/builder, TestReplay341 (file internal/builder/replay341_test.go).
Fix and Before: Fix is 83a9cf6, the head of mesh-controller feat/341-a-merge-check-judges-the-merge. Before is 3cfc121, the main it branched from. Once the controller's pull request merges, set Fix to its merge and clear Before, as the register says.
Proved by hand: go run ./replays/cmd/prove --repos <clones> R341 answered R341 (issue 341): PROVED — before its fix fails, on its fix passes. Before the fix, #66's head was answered its merge-check.sh passed.
How it runs: the replay runs the builder's Check whole. It uses a container runtime on PATH that runs each container's command on the machine, the store and bus answering and the judge never built. The repository's own check is go build ./... on a two-commit miniature of the node-engine's store record of 2026-10-09.
replays/merge-check.sh passes: register, prover and tests.
This adds R341 to `replays/register.go`, the replay of novox/hq issue 341 under ADR 0323.
- **Kind**: `InRepository` in mesh-controller, `./internal/builder`, `TestReplay341` (file `internal/builder/replay341_test.go`).
- **Fix and Before**: Fix is `83a9cf6`, the head of mesh-controller `feat/341-a-merge-check-judges-the-merge`. Before is `3cfc121`, the main it branched from. Once the controller's pull request merges, set Fix to its merge and clear Before, as the register says.
- **Proved by hand**: `go run ./replays/cmd/prove --repos <clones> R341` answered `R341 (issue 341): PROVED — before its fix fails, on its fix passes`. Before the fix, #66's head was answered `its merge-check.sh passed`.
- **How it runs**: the replay runs the builder's `Check` whole. It uses a container runtime on PATH that runs each container's command on the machine, the store and bus answering and the judge never built. The repository's own check is `go build ./...` on a two-commit miniature of the node-engine's store record of 2026-10-09.
`replays/merge-check.sh` passes: register, prover and tests.
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go), asks/merge-check.sh …
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Transitions
2026-10-12 15:31 (new) → proposed (announced): novox/mesh-lab#86's head announced
2026-10-12 15:35 proposed → checked (checked): the verdict names this commit
2026-10-12 15:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 16:11 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 16:11 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-lab@79108a72a0df` — **delivered** since 2026-10-12T16:11:52Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `feat/341-a-merge-check-judges-the-merge`, in order: novox/hq@09916e2bbc07 → novox/mesh-controller@875ebc093e18 → novox/mesh-catalog@41b6e10077ef → novox/mesh-lab@79108a72a0df
- novox/mesh-controller@875ebc093e18 before novox/mesh-catalog@41b6e10077ef: built by
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Transitions**
- 2026-10-12 15:31 (new) → proposed (announced): novox/mesh-lab#86's head announced
- 2026-10-12 15:35 proposed → checked (checked): the verdict names this commit
- 2026-10-12 15:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 16:11 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 16:11 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This adds R341 to
replays/register.go, the replay of novox/hq issue 341 under ADR 0323.InRepositoryin mesh-controller,./internal/builder,TestReplay341(fileinternal/builder/replay341_test.go).83a9cf6, the head of mesh-controllerfeat/341-a-merge-check-judges-the-merge. Before is3cfc121, the main it branched from. Once the controller's pull request merges, set Fix to its merge and clear Before, as the register says.go run ./replays/cmd/prove --repos <clones> R341answeredR341 (issue 341): PROVED — before its fix fails, on its fix passes. Before the fix, #66's head was answeredits merge-check.sh passed.Checkwhole. It uses a container runtime on PATH that runs each container's command on the machine, the store and bus answering and the judge never built. The repository's own check isgo build ./...on a two-commit miniature of the node-engine's store record of 2026-10-09.replays/merge-check.shpasses: register, prover and tests.Delivery
novox/mesh-lab@79108a72a0df— delivered since 2026-10-12T16:11:52ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
feat/341-a-merge-check-judges-the-merge, in order: novox/hq@09916e2bbc → novox/mesh-controller@875ebc093e → novox/mesh-catalog@41b6e10077 → novox/mesh-lab@79108a72a0Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.