Registers R314 for hq issue 314: InRepository, mesh-controller ./internal/link, TestReplay314, file internal/link/replay314_test.go, Fix 4b43115 (novox/mesh-controller #138; its first parent is the controller's main).
go run ./replays/cmd/prove R314: R314 (issue 314): PROVED — before its fix fails, on its fix passes. Before the fix: an answer of about 3145728 bytes did not arrive: replay-314 did not answer conditions within 5s.
sh merge-check.sh: passes (typecheck, unit suite, replays register tests).
Merge after novox/mesh-controller #138, so Fix names a commit on its main. #138 is one commit, merged as it stands.
Registers R314 for hq issue 314: InRepository, mesh-controller `./internal/link`, `TestReplay314`, file `internal/link/replay314_test.go`, Fix `4b43115` (novox/mesh-controller #138; its first parent is the controller's main).
`go run ./replays/cmd/prove R314`: `R314 (issue 314): PROVED — before its fix fails, on its fix passes`. Before the fix: `an answer of about 3145728 bytes did not arrive: replay-314 did not answer conditions within 5s`.
`sh merge-check.sh`: passes (typecheck, unit suite, replays register tests).
Merge after novox/mesh-controller #138, so `Fix` names a commit on its main. #138 is one commit, merged as it stands.
Deliverynovox/mesh-lab@d452a47be012 — delivered since 2026-10-08T11:10:12Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 11:08 (new) → proposed (announced): novox/mesh-lab#66's head announced
2026-10-08 11:09 proposed → checked (checked): the verdict names this commit
2026-10-08 11:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 11:10 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 11:10 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@d452a47be012` — **delivered** since 2026-10-08T11:10:12Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 11:08 (new) → proposed (announced): novox/mesh-lab#66's head announced
- 2026-10-08 11:09 proposed → checked (checked): the verdict names this commit
- 2026-10-08 11:09 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 11:10 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 11:10 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.
Registers R314 for hq issue 314: InRepository, mesh-controller
./internal/link,TestReplay314, fileinternal/link/replay314_test.go, Fix4b43115(novox/mesh-controller #138; its first parent is the controller's main).go run ./replays/cmd/prove R314:R314 (issue 314): PROVED — before its fix fails, on its fix passes. Before the fix:an answer of about 3145728 bytes did not arrive: replay-314 did not answer conditions within 5s.sh merge-check.sh: passes (typecheck, unit suite, replays register tests).Merge after novox/mesh-controller #138, so
Fixnames a commit on its main. #138 is one commit, merged as it stands.Delivery
novox/mesh-lab@d452a47be012— delivered since 2026-10-08T11:10:12ZDelivery 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.7f67fea9c2to28dda6197728dda61977tod452a47be0