R305: a recheck left the old merge-check verdict standing on the forge. The replay is mesh-delivery's TestARecheck* in novox/mesh-catalog (fix 74f912e on fix/recheck-resets-the-merge-check).
A catalogue module is a Go module of its own, so the register gains Module (the directory go test runs in, within the repository) and the prover runs there; every existing replay leaves it empty and runs at the root as before.
go run ./cmd/prove --repos <clones> R305: PROVED — before its fix fails, on its fix passes. gofmt, vet and TestEveryReplayIsWhole pass.
R305: a recheck left the old merge-check verdict standing on the forge. The replay is mesh-delivery's `TestARecheck*` in novox/mesh-catalog (fix 74f912e on `fix/recheck-resets-the-merge-check`).
A catalogue module is a Go module of its own, so the register gains `Module` (the directory go test runs in, within the repository) and the prover runs there; every existing replay leaves it empty and runs at the root as before.
`go run ./cmd/prove --repos <clones> R305`: **PROVED — before its fix fails, on its fix passes.** gofmt, vet and `TestEveryReplayIsWhole` pass.
A catalogue module is a Go module of its own, so the prover runs a replay
in the directory its register entry names. R305 fails on the commit before
the fix and passes on it.
Deliverynovox/mesh-lab@09d347a045d8 — delivered since 2026-10-08T08:35:04Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 08:12 (new) → proposed (announced): novox/mesh-lab#62's head announced
2026-10-08 08:13 proposed → checked (checked): the verdict names this commit
2026-10-08 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 08:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 08:35 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@09d347a045d8` — **delivered** since 2026-10-08T08:35:04Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 08:12 (new) → proposed (announced): novox/mesh-lab#62's head announced
- 2026-10-08 08:13 proposed → checked (checked): the verdict names this commit
- 2026-10-08 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 08:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 08:35 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.
R305: a recheck left the old merge-check verdict standing on the forge. The replay is mesh-delivery's
TestARecheck*in novox/mesh-catalog (fix 74f912e onfix/recheck-resets-the-merge-check).A catalogue module is a Go module of its own, so the register gains
Module(the directory go test runs in, within the repository) and the prover runs there; every existing replay leaves it empty and runs at the root as before.go run ./cmd/prove --repos <clones> R305: PROVED — before its fix fails, on its fix passes. gofmt, vet andTestEveryReplayIsWholepass.Delivery
novox/mesh-lab@09d347a045d8— delivered since 2026-10-08T08:35:04ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.