Issue 1146, found live after mesh-delivery #2 merged at 00:35: the approved merge into mesh-delivery, a repository the mesh builds nothing from, asked the first build of mesh-delivery-view (mesh-controller #386), and the guard of a build through a verb refused it (verbMayAsk, ADR 0266), so the view was never built.
The controller's first-build ask carries a warrant in its context (withFirstBuildWarrant), set only by askFirstBuilds after it checked the operator's Approve of the merged head (ADR 0432), and covering only that repository on the git seat and the module paths the merge holds. verbMayAsk lets exactly that through; every other ask through a verb is judged as before.
A merge's ask that fails is kept under notAskedID: a module at the repository's root was kept as "not-asked--.", a key the bus refuses, so the failure was not even recorded.
Issue 1169: the system-exports reload test waited for the first connect event and sometimes read the watchman's own; it now waits for the one naming the user it connected (a flaky test of milestone R1b, found by this branch's try).
The AC7 integration test no longer stubs the ask: it runs the real ask, guard and build queue (with the identity store), and reads what its wrapper records under a lock.
Tests: 1146/AC9 (TestTheApprovedFirstBuildPassesTheGuardOfAVerbAndIsQueued, integration: a real bus, the queue holds the one first build; without the warrant, and for a path the merge does not hold, refused), 1146/AC7 un-stubbed, TestTheFirstBuildWarrantCoversOnlyItsRepositoryAndItsModulePaths (unit), TestTheIdOfABuildNotAskedIsAKeyTheBusTakes (unit, failed first). Try build-1792364822881770455 passed in 4 m 0 s at ec85cdf7.
Delivery: the controller to novox. The next merge into mesh-delivery (milestone R2b's group) then asks the first builds of mesh-delivery-view and mesh-delivery-watchman.
Issue 1146, found live after mesh-delivery #2 merged at 00:35: the approved merge into mesh-delivery, a repository the mesh builds nothing from, asked the first build of mesh-delivery-view (mesh-controller #386), and the guard of a build through a verb refused it (verbMayAsk, ADR 0266), so the view was never built.
- The controller's first-build ask carries a warrant in its context (withFirstBuildWarrant), set only by askFirstBuilds after it checked the operator's Approve of the merged head (ADR 0432), and covering only that repository on the git seat and the module paths the merge holds. verbMayAsk lets exactly that through; every other ask through a verb is judged as before.
- A merge's ask that fails is kept under notAskedID: a module at the repository's root was kept as "not-asked-<commit>-.", a key the bus refuses, so the failure was not even recorded.
- Issue 1169: the system-exports reload test waited for the first connect event and sometimes read the watchman's own; it now waits for the one naming the user it connected (a flaky test of milestone R1b, found by this branch's try).
- The AC7 integration test no longer stubs the ask: it runs the real ask, guard and build queue (with the identity store), and reads what its wrapper records under a lock.
Tests: 1146/AC9 (TestTheApprovedFirstBuildPassesTheGuardOfAVerbAndIsQueued, integration: a real bus, the queue holds the one first build; without the warrant, and for a path the merge does not hold, refused), 1146/AC7 un-stubbed, TestTheFirstBuildWarrantCoversOnlyItsRepositoryAndItsModulePaths (unit), TestTheIdOfABuildNotAskedIsAKeyTheBusTakes (unit, failed first). Try build-1792364822881770455 passed in 4 m 0 s at ec85cdf7.
Delivery: the controller to novox. The next merge into mesh-delivery (milestone R2b's group) then asks the first builds of mesh-delivery-view and mesh-delivery-watchman.
Reviewed-by: reviewer-r12@shanks at ec85cdf70c07a71f0805528def9887886c65577d
mesh/merge-gate head ec85cdf70c07 merged into trunk cec26d859695 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@ec85cdf70c07 — delivered since 2026-10-18T23:22:53Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-18 23:12 (new) → proposed (announced): novox/mesh-controller#387's head announced
2026-10-18 23:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 23:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 23:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 23:20 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-18 23:22 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@ec85cdf70c07` — **delivered** since 2026-10-18T23:22:53Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-18 23:12 (new) → proposed (announced): novox/mesh-controller#387's head announced
- 2026-10-18 23:19 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-18 23:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-18 23:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-18 23:20 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-18 23:22 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
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.
Issue 1146, found live after mesh-delivery #2 merged at 00:35: the approved merge into mesh-delivery, a repository the mesh builds nothing from, asked the first build of mesh-delivery-view (mesh-controller #386), and the guard of a build through a verb refused it (verbMayAsk, ADR 0266), so the view was never built.
Tests: 1146/AC9 (TestTheApprovedFirstBuildPassesTheGuardOfAVerbAndIsQueued, integration: a real bus, the queue holds the one first build; without the warrant, and for a path the merge does not hold, refused), 1146/AC7 un-stubbed, TestTheFirstBuildWarrantCoversOnlyItsRepositoryAndItsModulePaths (unit), TestTheIdOfABuildNotAskedIsAKeyTheBusTakes (unit, failed first). Try build-1792364822881770455 passed in 4 m 0 s at
ec85cdf7.Delivery: the controller to novox. The next merge into mesh-delivery (milestone R2b's group) then asks the first builds of mesh-delivery-view and mesh-delivery-watchman.
Reviewed-by: reviewer-r12@shanks at
ec85cdf70cDelivery
novox/mesh-controller@ec85cdf70c07— delivered since 2026-10-18T23:22:53ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
ec85cdf7Judged: head
ec85cdf70c07merged into trunkcec26d859695; read beside it: mesh-catalogb4527d9091e9, mesh-controller-maincec26d859695, mesh-host89025ad004d4, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on shanks as
build-1792365134692618208(builds --log build-1792365134692618208).