Issue 1311: the seat verb delivery-check parses the child's whole standard output as JSON; with one member, delivery check printed the plan text and an 'asked … as' line before its answer, so the answer carried no data and mesh-delivery read an empty id ('asked as', 'held no id: taken as refused', re-asked every minute). It held mesh-sdk#43 since 2026-10-19 20:39 UTC and mesh-controller#402's re-check.
pullUpdated writes its prose to a writer and returns the request id it asked.
The one-member branch (recheckOneHead) points standard output at standard error while the check runs, then answers {"asked": , "rechecked": } alone on standard output; askGroupCheck's cyclic verdict also goes to standard error.
Tests: delivery_check_answer_test.go (answerOf parses only the clean answer; sayChecked writes to its writer) and TestOneHeadRecheckLeavesStandardOutputTheAnswerAlone (real pipes, stray prints land on standard error).
The branch name is reused: the earlier feat/no-terminal merged as #402; this branch holds only 1311's two commits on main 40350d82. mesh-delivery's side (ignoring an empty answer) goes into the gate in R3e. Tried: build-1792450332497011631 pass.
Issue 1311: the seat verb delivery-check parses the child's whole standard output as JSON; with one member, `delivery check` printed the plan text and an 'asked … as' line before its answer, so the answer carried no data and mesh-delivery read an empty id ('asked as', 'held no id: taken as refused', re-asked every minute). It held mesh-sdk#43 since 2026-10-19 20:39 UTC and mesh-controller#402's re-check.
- pullUpdated writes its prose to a writer and returns the request id it asked.
- The one-member branch (recheckOneHead) points standard output at standard error while the check runs, then answers {"asked": <request id>, "rechecked": <member id>} alone on standard output; askGroupCheck's cyclic verdict also goes to standard error.
- Tests: delivery_check_answer_test.go (answerOf parses only the clean answer; sayChecked writes to its writer) and TestOneHeadRecheckLeavesStandardOutputTheAnswerAlone (real pipes, stray prints land on standard error).
The branch name is reused: the earlier feat/no-terminal merged as #402; this branch holds only 1311's two commits on main 40350d82. mesh-delivery's side (ignoring an empty answer) goes into the gate in R3e. Tried: build-1792450332497011631 pass.
Reviewed-by: review-1311@shanks at 202b453de1a484bbe13d8d5b59ce706172042712
Deliverynovox/mesh-controller@202b453de1a4 — delivered since 2026-10-19T23:40:42Z
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 22:58 (new) → proposed (announced): novox/mesh-controller#403's head announced
2026-10-19 23:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-19 23:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-19 23:38 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 23:38 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 23:40 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@202b453de1a4` — **delivered** since 2026-10-19T23:40:42Z
**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 22:58 (new) → proposed (announced): novox/mesh-controller#403's head announced
- 2026-10-19 23:10 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-19 23:10 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-19 23:38 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 23:38 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 23:40 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`.
Out of date when it landed: out of date: judged against trunk 40350d82fa, the trunk is now 70cb217601f9; judged again on a recheck or when it is merged
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 1311: the seat verb delivery-check parses the child's whole standard output as JSON; with one member,
delivery checkprinted the plan text and an 'asked … as' line before its answer, so the answer carried no data and mesh-delivery read an empty id ('asked as', 'held no id: taken as refused', re-asked every minute). It held mesh-sdk#43 since 2026-10-19 20:39 UTC and mesh-controller#402's re-check.The branch name is reused: the earlier feat/no-terminal merged as #402; this branch holds only 1311's two commits on main
40350d82. mesh-delivery's side (ignoring an empty answer) goes into the gate in R3e. Tried: build-1792450332497011631 pass.Reviewed-by: review-1311@shanks at
202b453de1delivery checkstandard output the answer alone and answer the request id asked (issue 1311) 7a0b275020delivery checkruns, so its answer is the only JSON (issue 1311)Delivery
novox/mesh-controller@202b453de1a4— delivered since 2026-10-19T23:40:42ZDelivery 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
202b453dJudged: head
202b453de1a4merged into trunk40350d82fa20; read beside it: mesh-catalogc0880c4dc271, mesh-controller-main40350d82fa20, 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-1792450727568903094(builds --log build-1792450727568903094).Merge check at
202b453dJudged: head
202b453de1a4merged into trunk40350d82fa20; read beside it: mesh-catalogc0880c4dc271, mesh-controller-main40350d82fa20, 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-1792451146420076155(builds --log build-1792451146420076155).Out of date when it landed: out of date: judged against trunk
40350d82fa, the trunk is now 70cb217601f9; judged again on a recheck or when it is merged