Issue 1272. The seat verbs delivery-check and delivery-order re-execute the controller's own command line (seatverbs.go:411-418, selfexec.go) with the group's members JSON, every changed path included, as one --members argument. Design 47 R3c's group (1666 paths) made it over Linux's 128 KiB per-argument limit: "fork/exec /proc/self/exe: argument list too long", so the group's composed check was never asked and nothing said so.
membersFlags: up to 32 KiB the argument is as before; above it the JSON goes to members.json (0600) in a private mesh-members-* directory, named by --members-file, removed after the command; a file that cannot be written is the verb's error.
delivery check and delivery order read --members-file into the same members value; --members still works for a person.
Tests: 1272/AC1-AC3 in members_file_test.go (1666-path fixture, over 200 KB), each failed first on an assertion. Merge check passed 16:13 UTC (5m57s, 3544 integration tests). The end-to-end proof is R3c's group getting its composed check after this is delivered. Its delivery moves mesh-controller to novox. Leftovers (delivery-plan's and plans --what-if's path lists, a directory left on a handover refusal) are issue 1273.
Issue 1272. The seat verbs delivery-check and delivery-order re-execute the controller's own command line (seatverbs.go:411-418, selfexec.go) with the group's members JSON, every changed path included, as one --members argument. Design 47 R3c's group (1666 paths) made it over Linux's 128 KiB per-argument limit: "fork/exec /proc/self/exe: argument list too long", so the group's composed check was never asked and nothing said so.
- membersFlags: up to 32 KiB the argument is as before; above it the JSON goes to members.json (0600) in a private mesh-members-* directory, named by --members-file, removed after the command; a file that cannot be written is the verb's error.
- `delivery check` and `delivery order` read --members-file into the same members value; --members still works for a person.
Tests: 1272/AC1-AC3 in members_file_test.go (1666-path fixture, over 200 KB), each failed first on an assertion. Merge check passed 16:13 UTC (5m57s, 3544 integration tests). The end-to-end proof is R3c's group getting its composed check after this is delivered. Its delivery moves mesh-controller to novox. Leftovers (delivery-plan's and plans --what-if's path lists, a directory left on a handover refusal) are issue 1273.
Reviewed-by: review-1272@shanks at 540cda11dfd56967af6a18ccce0d302c89055324
mesh/merge-gate head 540cda11dfd5 merged into trunk ad753c70f6d4 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@540cda11dfd5 — delivered since 2026-10-19T16:19:00Z
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-19 16:07 (new) → proposed (announced): novox/mesh-controller#398's head announced
2026-10-19 16:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 16:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 16:17 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-19 16:17 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-19 16:19 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@540cda11dfd5` — **delivered** since 2026-10-19T16:19:00Z
**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-19 16:07 (new) → proposed (announced): novox/mesh-controller#398's head announced
- 2026-10-19 16:13 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 16:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 16:17 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-19 16:17 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-19 16:19 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 1272. The seat verbs delivery-check and delivery-order re-execute the controller's own command line (seatverbs.go:411-418, selfexec.go) with the group's members JSON, every changed path included, as one --members argument. Design 47 R3c's group (1666 paths) made it over Linux's 128 KiB per-argument limit: "fork/exec /proc/self/exe: argument list too long", so the group's composed check was never asked and nothing said so.
delivery checkanddelivery orderread --members-file into the same members value; --members still works for a person.Tests: 1272/AC1-AC3 in members_file_test.go (1666-path fixture, over 200 KB), each failed first on an assertion. Merge check passed 16:13 UTC (5m57s, 3544 integration tests). The end-to-end proof is R3c's group getting its composed check after this is delivered. Its delivery moves mesh-controller to novox. Leftovers (delivery-plan's and plans --what-if's path lists, a directory left on a handover refusal) are issue 1273.
Reviewed-by: review-1272@shanks at
540cda11dfDelivery
novox/mesh-controller@540cda11dfd5— delivered since 2026-10-19T16:19:00ZDelivery 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
540cda11Judged: head
540cda11dfd5merged into trunkad753c70f6d4; read beside it: mesh-cataloge8c3448797c7, mesh-controller-mainad753c70f6d4, mesh-host2474bf28330f, 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 ace as
build-1792426027904065765(builds --log build-1792426027904065765).