Register the replays of issues 296, 299 and 300 (hq ADR 0237) #58

2026-10-07T21:44:13Z

mesh-admin commented

2026-10-07 21:44:13 +00:00

Adds R296, R299 and R300 to replays/register.go: tests in mesh-controller (TestReplay296, TestReplay299, TestReplay300, in cmd/mesh-controller/replays_test.go, added by novox/mesh-controller PR on branch replays/296-299-300, commit 7597294 as HomeRef — reachable once that PR merges with a merge commit).

Fix is each fix's merge in mesh-controller: 3808634 (#119), c37d774 (#121), e7dca6c (#122); the prover runs each on the merge's first parent and on the merge.

R296 (issue 296): PROVED — before its fix fails, on its fix passes
  before: replays_test.go:364: a plan in its tier since 19:48:41, read at 20:30:00 and saved 4s before, reads "novox/mesh-catalog 3ad22356 tier 1 of 1, building for 4s"
R299 (issue 299): PROVED — before its fix fails, on its fix passes
  before: replays_test.go:483: a holder serving none of a seat's optional verbs was said silent: node-catching-up's holder on laptop does not answer the bus ...
R300 (issue 300): PROVED — before its fix fails, on its fix passes
  before: replays_test.go:519: the merge adding modules/systemd-resolved asked the build seat for [], not [novox/mesh-catalog modules/systemd-resolved main]

Checks: gofmt, go vet, TestEveryReplayIsWhole pass. npm test has two failures locally (listing instances/networks fails rather than reporting none) that fail identically on main on this workstation — unrelated to this change, which touches only Go.

Merge the mesh-controller PR first, so HomeRef is on its main.

Adds R296, R299 and R300 to `replays/register.go`: tests in mesh-controller (`TestReplay296`, `TestReplay299`, `TestReplay300`, in `cmd/mesh-controller/replays_test.go`, added by novox/mesh-controller PR on branch `replays/296-299-300`, commit 7597294 as `HomeRef` — reachable once that PR merges with a merge commit). Fix is each fix's merge in mesh-controller: 3808634 (#119), c37d774 (#121), e7dca6c (#122); the prover runs each on the merge's first parent and on the merge. ``` R296 (issue 296): PROVED — before its fix fails, on its fix passes before: replays_test.go:364: a plan in its tier since 19:48:41, read at 20:30:00 and saved 4s before, reads "novox/mesh-catalog 3ad22356 tier 1 of 1, building for 4s" R299 (issue 299): PROVED — before its fix fails, on its fix passes before: replays_test.go:483: a holder serving none of a seat's optional verbs was said silent: node-catching-up's holder on laptop does not answer the bus ... R300 (issue 300): PROVED — before its fix fails, on its fix passes before: replays_test.go:519: the merge adding modules/systemd-resolved asked the build seat for [], not [novox/mesh-catalog modules/systemd-resolved main] ``` Checks: `gofmt`, `go vet`, `TestEveryReplayIsWhole` pass. `npm test` has two failures locally (`listing instances/networks fails rather than reporting none`) that fail identically on main on this workstation — unrelated to this change, which touches only Go. Merge the mesh-controller PR first, so HomeRef is on its main.

mesh-admin added 1 commit 2026-10-07 21:44:13 +00:00

Register the replays of issues 296, 299 and 300, each proved to fail before its fix and pass on it (hq ADR 0237)

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

mesh/delivery-group group replays/296-299-300 delivered: every member is delivered

Details

74c59661b1

mesh-admin commented

2026-10-07 21:44:51 +00:00

Delivery novox/mesh-lab@74c59661b1d2 — delivered since 2026-10-07T21:55:23Z

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

Group replays/296-299-300, in order: novox/mesh-controller@7597294ff8 → novox/mesh-lab@74c59661b1

Transitions

2026-10-07 21:44 (new) → proposed (announced): novox/mesh-lab#58's head announced
2026-10-07 21:45 proposed → checked (checked): the verdict names this commit
2026-10-07 21:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 21:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-07 21:55 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.

**Delivery** `novox/mesh-lab@74c59661b1d2` — **delivered** since 2026-10-07T21:55:23Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Group** `replays/296-299-300`, in order: novox/mesh-controller@7597294ff863 → novox/mesh-lab@74c59661b1d2 **Transitions** - 2026-10-07 21:44 (new) → proposed (announced): novox/mesh-lab#58's head announced - 2026-10-07 21:45 proposed → checked (checked): the verdict names this commit - 2026-10-07 21:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-07 21:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-07 21:55 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-admin merged commit a9c3bd8e6d into main

2026-10-07 21:55:20 +00:00

mesh-admin deleted branch replays/296-299-300

2026-10-07 21:55:20 +00:00

mesh-admin referenced this pull request

2026-10-07 22:16:54 +00:00

Check the Go replays in the Go toolchain, and register R301 and R302 (hq issues 301, 302) #59

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#58