Register R614: a new SDK planned alone, rebuilding neither its toolchain nor its bundles (hq issue 614) #100

2026-10-13T09:10:17Z

mesh-admin commented

2026-10-13 09:10:17 +00:00

What: a register entry for the replay of issue 614. The replay is a test-only file in the controller (cmd/mesh-controller/replay614_test.go, mesh-controller #296), done the same way as R348 and R349.

Why: issue 614 is a core issue (mesh-controller). On 2026-10-13 mesh-sdk 0.1.14 planned "builds mesh-sdk, sent nowhere" because a built manifest carries no build.

Fix is the branch with Before origin/main until #296 merges. Then Fix becomes the merge commit and Before is set to "".

How tested: go run ./cmd/prove R614 with a store printed "PROVED — before its fix fails, on its fix passes" (before: plans mesh-sdk). merge-check.sh passed.

For issue 614.

What: a register entry for the replay of issue 614. The replay is a test-only file in the controller (cmd/mesh-controller/replay614_test.go, mesh-controller #296), done the same way as R348 and R349. Why: issue 614 is a core issue (mesh-controller). On 2026-10-13 mesh-sdk 0.1.14 planned "builds mesh-sdk, sent nowhere" because a built manifest carries no `build`. Fix is the branch with Before origin/main until #296 merges. Then Fix becomes the merge commit and Before is set to "". How tested: `go run ./cmd/prove R614` with a store printed "PROVED — before its fix fails, on its fix passes" (before: plans [[mesh-sdk]]). merge-check.sh passed. For issue 614.

mesh-admin added 1 commit 2026-10-13 09:10:17 +00:00

Register R614: a new SDK planned alone, rebuilding neither its toolchain nor the bundles in it (hq issue 614)

mesh/merge-gate out of date: judged against trunk f71250c3ddd5, the trunk is now d7098c4b2781; judged again on a recheck or when it is merged

Details

mesh/repo-check out of date: judged against trunk f71250c3ddd5, the trunk is now d7098c4b2781; judged again on a recheck or when it is merged

Details

mesh/delivery superseded: a newer head of the same pull request

Details

7806a42c45

Its replay (mesh-controller #296) holds the plan of 2026-10-13, "builds mesh-sdk, sent
nowhere", against the fix that reads a built module's build edges from what is kept of it.
Proved: fails on main, passes on the fix.

mesh-admin commented

2026-10-13 09:10:56 +00:00

Delivery novox/mesh-lab@9deefc637065 — delivered since 2026-10-13T09:40:36Z

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

Transitions

2026-10-13 09:36 (new) → proposed (announced): novox/mesh-lab#100's head announced
2026-10-13 09:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-13 09:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-13 09:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-13 09:40 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@9deefc637065` — **delivered** since 2026-10-13T09:40:36Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-13 09:36 (new) → proposed (announced): novox/mesh-lab#100's head announced - 2026-10-13 09:40 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-13 09:40 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-13 09:40 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-13 09:40 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 reviewed

2026-10-13 09:35:06 +00:00

mesh-admin left a comment

Verdict: approve at 7806a42c45

Independent review for issue 614. The statuses at this head are: mesh/merge-gate success ("head 7806a42c45 merged into trunk f71250c3dd — pass: the change touches no module of the mesh's graph"), mesh/repo-check success ("head 7806a42c45 merged into trunk f71250c3dd — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…") and mesh/delivery success ("ready: it delivers once merged").

I ran go run ./cmd/prove R614 on g14 against fresh HTTPS clones, with a throwaway store, and it printed "R614 (issue 614): PROVED — before its fix fails, on its fix passes". The failure before the fix was "a new SDK plans mesh-sdk, want mesh-sdk] [mesh-tools] [minio umami".

The entry is correct for now. Fix names the branch fix/614-a-built-module-keeps-its-build-edges, which resolves to e658a14296f9c86938f38a0a1f6727bfa7ac48fe, the head of mesh-controller #296. Before is "origin/main", following the R236 precedent for a fix still on its branch. Package, Test and Files match the test file in #296. No Home is needed, because the replay file lives in the fix's own commit.

This entry must be updated after #296 merges. Fix becomes the merge commit of #296 and Before becomes "". The branch name is not a stable reference once the branch is deleted, and after the merge the commit's first parent is the main it replays against. Unlike R348 and R349 it needs no Home or HomeRef, because the merge commit contains the replay file. The description already says this, and the comment in the entry says it too.

Verdict: approve at 7806a42c45f72996789793a1f0bc62844f0185e9 Independent review for issue 614. The statuses at this head are: mesh/merge-gate success ("head 7806a42c45f7 merged into trunk f71250c3ddd5 — pass: the change touches no module of the mesh's graph"), mesh/repo-check success ("head 7806a42c45f7 merged into trunk f71250c3ddd5 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…") and mesh/delivery success ("ready: it delivers once merged"). I ran `go run ./cmd/prove R614` on g14 against fresh HTTPS clones, with a throwaway store, and it printed "R614 (issue 614): PROVED — before its fix fails, on its fix passes". The failure before the fix was "a new SDK plans [[mesh-sdk]], want [[mesh-sdk] [mesh-tools] [minio umami]]". The entry is correct for now. Fix names the branch fix/614-a-built-module-keeps-its-build-edges, which resolves to e658a14296f9c86938f38a0a1f6727bfa7ac48fe, the head of mesh-controller #296. Before is "origin/main", following the R236 precedent for a fix still on its branch. Package, Test and Files match the test file in #296. No Home is needed, because the replay file lives in the fix's own commit. This entry must be updated after #296 merges. Fix becomes the merge commit of #296 and Before becomes "". The branch name is not a stable reference once the branch is deleted, and after the merge the commit's first parent is the main it replays against. Unlike R348 and R349 it needs no Home or HomeRef, because the merge commit contains the replay file. The description already says this, and the comment in the entry says it too.

jschoubben added 1 commit 2026-10-13 09:36:38 +00:00

R614's fix is the merge of mesh-controller #296 (hq issue 614)

mesh/merge-gate head 9deefc637065 merged into trunk d7098c4b2781 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 9deefc637065 merged into trunk d7098c4b2781 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript)…

Details

mesh/delivery delivered

Details

9deefc6370

Proved against the merge: fails on its first parent, passes on it.

mesh-admin reviewed

2026-10-13 09:38:08 +00:00

mesh-admin left a comment

Verdict: approve at 9deefc6370

The diff from 7806a42c to this head changes only what review 186 asked for. In R614, Fix changes from the branch name to 404b4409e70ed7365bb8a53862e4b197deb0bdc6, Before "origin/main" is removed (so it is now empty), and the comment line becomes "Fix is the merge of its pull request." Nothing else in the repository changed.

I checked the merge commit. 404b4409 is the merge of mesh-controller #296. Its first parent is 1826b68 (main before the merge) and its second parent is e658a142 (the head I reviewed). So the replay fails on the first parent and passes on the fix.

go run ./cmd/prove R614, run on g14 against fresh clones with a throwaway store, printed "R614 (issue 614): PROVED — before its fix fails, on its fix passes". The failure on the first parent was "a new SDK plans mesh-sdk, want mesh-sdk] [mesh-tools] [minio umami".

The statuses at this head were still pending when I posted this: mesh/merge-gate said "building on ace since 11:36" and mesh/delivery said "checking". mesh/repo-check had not reported yet. Merge only once both required checks are green.

Verdict: approve at 9deefc637065bf59a02128184bd1b01ddafbb030 The diff from 7806a42c to this head changes only what review 186 asked for. In R614, Fix changes from the branch name to 404b4409e70ed7365bb8a53862e4b197deb0bdc6, Before "origin/main" is removed (so it is now empty), and the comment line becomes "Fix is the merge of its pull request." Nothing else in the repository changed. I checked the merge commit. 404b4409 is the merge of mesh-controller #296. Its first parent is 1826b68 (main before the merge) and its second parent is e658a142 (the head I reviewed). So the replay fails on the first parent and passes on the fix. `go run ./cmd/prove R614`, run on g14 against fresh clones with a throwaway store, printed "R614 (issue 614): PROVED — before its fix fails, on its fix passes". The failure on the first parent was "a new SDK plans [[mesh-sdk]], want [[mesh-sdk] [mesh-tools] [minio umami]]". The statuses at this head were still pending when I posted this: mesh/merge-gate said "building on ace since 11:36" and mesh/delivery said "checking". mesh/repo-check had not reported yet. Merge only once both required checks are green.

mesh-admin merged commit a8d86bb10b into main

2026-10-13 09:40:22 +00:00

mesh-admin deleted branch fix/614-replay

2026-10-13 09:40:22 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#100