Standard input is bounded at 64 KiB (link.CLIMaxStdin): over it the request is refused and nothing runs.
It is given only to a line that runs as the controller's terminal (runForMeshCLI); an ordinary call carrying any is refused, and nothing runs.
Never in the calls record: answerCLI records cliRecorded(msg.Data), which drops it and keeps only stdin-given: true; kept also replaces a stdin key, so neither path can keep it. Never in the journal (the line's first word only, as before), never in an answer.
On the bus: the one core request on mesh.control.<node>.cli. The CONTROL stream names mesh.control.*.report and mesh.control.enrol only, so nothing persists it; only the controller is granted mesh.control.>; each hop is TLS to the pinned bus certificate. Not sealed end to end: the bus server holds it in memory while routing. Sealing would need a controller key every engine knows; none exists today.
No vendored change: the controller has its own copy of the request's fields (link.CLIAsked), held to the engine's by the field-name tests on both sides.
Tests
TestStandardInputReachesSecretAcceptAtTheTerminalAndNowhereElse (cmd): the test binary runs as secret accept <node> <module> <name> [--from -] and reads its value with valueFor, exactly as secret accept does, comparing a digest; both forms read what mesh-cli carried; with no input it reads nothing; an ordinary line carrying input is refused and runs nothing; neither the answer nor the journal holds the value.
TestAMeshCLIRecordNeverKeepsItsStandardInput (link): no form of the value in the record, by either path; the record still decodes as the request so the asker can follow its call.
The field-name test gains stdin.
merge-check: targeted tests pass locally; the full suite with -race is running and its result is posted here. Do not merge without review. Order: mesh-sdk #15 (tag), then this, mesh-host #73 and mesh-catalog #164 in any order (each alone is inert: without the engine's forwarding no input arrives; without this, input arriving is not given to the line — as today).
**Reviewers' checklist (the same on all four PRs)**
- Standard input is bounded at 64 KiB (`link.CLIMaxStdin`): over it the request is refused and nothing runs.
- It is given only to a line that runs as the controller's terminal (`runForMeshCLI`); an ordinary call carrying any is refused, and nothing runs.
- Never in the calls record: `answerCLI` records `cliRecorded(msg.Data)`, which drops it and keeps only `stdin-given: true`; `kept` also replaces a `stdin` key, so neither path can keep it. Never in the journal (the line's first word only, as before), never in an answer.
- On the bus: the one core request on `mesh.control.<node>.cli`. The CONTROL stream names `mesh.control.*.report` and `mesh.control.enrol` only, so nothing persists it; only the controller is granted `mesh.control.>`; each hop is TLS to the pinned bus certificate. **Not sealed end to end**: the bus server holds it in memory while routing. Sealing would need a controller key every engine knows; none exists today.
- No vendored change: the controller has its own copy of the request's fields (`link.CLIAsked`), held to the engine's by the field-name tests on both sides.
**Tests**
- `TestStandardInputReachesSecretAcceptAtTheTerminalAndNowhereElse` (cmd): the test binary runs as `secret accept <node> <module> <name> [--from -]` and reads its value with `valueFor`, exactly as `secret accept` does, comparing a digest; both forms read what mesh-cli carried; with no input it reads nothing; an ordinary line carrying input is refused and runs nothing; neither the answer nor the journal holds the value.
- `TestAMeshCLIRecordNeverKeepsItsStandardInput` (link): no form of the value in the record, by either path; the record still decodes as the request so the asker can follow its call.
- The field-name test gains `stdin`.
merge-check: targeted tests pass locally; the full suite with -race is running and its result is posted here. Do not merge without review. Order: mesh-sdk #15 (tag), then this, mesh-host #73 and mesh-catalog #164 in any order (each alone is inert: without the engine's forwarding no input arrives; without this, input arriving is not given to the line — as today).
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
A secret given at the controller's terminal through mesh-cli (secret accept … --from -) never reached the
line: every line ran with no standard input. A line that runs as the terminal now reads what mesh-cli
carried (at most 64 KiB); an ordinary call carrying any is refused and nothing runs; the calls record keeps
only that some was given, the journal and the answer nothing of it.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on novox: judging — 0 healthy judging(s) so far
Transitions
2026-10-09 15:10 (new) → proposed (announced): novox/mesh-controller#184's head announced
2026-10-09 15:17 proposed → checked (checked): the verdict names this commit
2026-10-09 15:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 16:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 16:10 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
2026-10-09 16:11 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@07e59c535e7c` — **superseded** since 2026-10-09T16:11:00Z
**Covered**: delivered after its walk was superseded: the walk plan-1791562260243950312, which took its walk plan-1791562212728626197 over, ended done
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Group** `feat/a-terminal-line-takes-standard-input`: novox/mesh-controller@07e59c535e7c, novox/mesh-host@4ea6a2f04e2c, novox/mesh-sdk@f047d0a4a970
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on novox: judging — 0 healthy judging(s) so far
**Transitions**
- 2026-10-09 15:10 (new) → proposed (announced): novox/mesh-controller#184's head announced
- 2026-10-09 15:17 proposed → checked (checked): the verdict names this commit
- 2026-10-09 15:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 16:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 16:10 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
- 2026-10-09 16:11 delivering → superseded (superseded): a newer delivery to the same trunk took over its walk
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as build-1791558145538913925 (builds --log build-1791558145538913925).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T14:52:25Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T14:52:25Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 190.267s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.051s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.056s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/route-proxy 1.156s
ok github.com/novox/mesh-controller/internal/artifacts 1.086s
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.62s)
genesis_template_test.go:37: the installer's user list does not let the controller publish [$KV.mesh-controller_asked.> mesh.seat.mesh-controller.tool.plans mesh.seat.mesh-delivery.tool.release mesh.seat.mesh-delivery.tool.stop mesh.seat.node-launcher.tool.secret.* mesh.seat.node-service-manager.tool.restart.*] — it would come up and be refused on the first thing it tried
genesis_template_test.go:41: the installer's user list does not let the controller subscribe [mesh.seat.operator-channel.event.decided.mesh-controller]
FAIL
FAIL github.com/novox/mesh-controller/internal/broker 1.630s
ok github.com/novox/mesh-controller/internal/builder 1.860s
ok github.com/novox/mesh-controller/internal/catalogue 4.453s
ok github.com/novox/mesh-controller/internal/conditions 2.465s
ok github.com/novox/mesh-controller/internal/envfile 1.065s
ok github.com/novox/mesh-controller/internal/facts 1.061s
ok github.com/novox/mesh-controller/internal/identity 4.149s
ok github.com/novox/mesh-controller/internal/inventory 72.726s
ok github.com/novox/mesh-controller/internal/lease 17.696s
ok github.com/novox/mesh-controller/internal/licences 3.795s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.050s
ok github.com/novox/mesh-controller/internal/link 51.443s
ok github.com/novox/mesh-controller/internal/lint 2.033s
ok github.com/novox/mesh-controller/internal/outward 1.092s
ok github.com/novox/mesh-controller/internal/overlay 1.081s
ok github.com/novox/mesh-controller/internal/secrets 1.427s
ok github.com/novox/mesh-controller/internal/store 3.313s
ok github.com/novox/mesh-controller/internal/testbus 1.241s
ok github.com/novox/mesh-controller/internal/token 1.017s
FAIL
**Merge check** at `ba97297f`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.62s)
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on ace as `build-1791558145538913925` (`builds --log build-1791558145538913925`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T14:52:25Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T14:52:25Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 190.267s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.051s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.056s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/route-proxy 1.156s
ok github.com/novox/mesh-controller/internal/artifacts 1.086s
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.62s)
genesis_template_test.go:37: the installer's user list does not let the controller publish [$KV.mesh-controller_asked.> mesh.seat.mesh-controller.tool.plans mesh.seat.mesh-delivery.tool.release mesh.seat.mesh-delivery.tool.stop mesh.seat.node-launcher.tool.secret.* mesh.seat.node-service-manager.tool.restart.*] — it would come up and be refused on the first thing it tried
genesis_template_test.go:41: the installer's user list does not let the controller subscribe [mesh.seat.operator-channel.event.decided.mesh-controller]
FAIL
FAIL github.com/novox/mesh-controller/internal/broker 1.630s
ok github.com/novox/mesh-controller/internal/builder 1.860s
ok github.com/novox/mesh-controller/internal/catalogue 4.453s
ok github.com/novox/mesh-controller/internal/conditions 2.465s
ok github.com/novox/mesh-controller/internal/envfile 1.065s
ok github.com/novox/mesh-controller/internal/facts 1.061s
ok github.com/novox/mesh-controller/internal/identity 4.149s
ok github.com/novox/mesh-controller/internal/inventory 72.726s
ok github.com/novox/mesh-controller/internal/lease 17.696s
ok github.com/novox/mesh-controller/internal/licences 3.795s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.050s
ok github.com/novox/mesh-controller/internal/link 51.443s
ok github.com/novox/mesh-controller/internal/lint 2.033s
ok github.com/novox/mesh-controller/internal/outward 1.092s
ok github.com/novox/mesh-controller/internal/overlay 1.081s
ok github.com/novox/mesh-controller/internal/secrets 1.427s
ok github.com/novox/mesh-controller/internal/store 3.313s
ok github.com/novox/mesh-controller/internal/testbus 1.241s
ok github.com/novox/mesh-controller/internal/token 1.017s
FAIL
```
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
The repo-check reads the installer's user list at the pinned commit, and the old pin predated mesh-host
#59 and #68: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose failed on main's own grants.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791558643202596388 (builds --log build-1791558643202596388).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T15:04:05Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T15:04:05Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 244.264s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.064s
ok github.com/novox/mesh-controller/internal/broker 8.942s
ok github.com/novox/mesh-controller/internal/builder 3.285s
ok github.com/novox/mesh-controller/internal/catalogue 4.951s
ok github.com/novox/mesh-controller/internal/conditions 2.514s
ok github.com/novox/mesh-controller/internal/envfile 1.032s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 11.381s
ok github.com/novox/mesh-controller/internal/inventory 96.916s
ok github.com/novox/mesh-controller/internal/lease 17.681s
ok github.com/novox/mesh-controller/internal/licences 10.866s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.012s
ok github.com/novox/mesh-controller/internal/link 57.720s
ok github.com/novox/mesh-controller/internal/lint 2.156s
ok github.com/novox/mesh-controller/internal/outward 1.032s
ok github.com/novox/mesh-controller/internal/overlay 1.025s
ok github.com/novox/mesh-controller/internal/secrets 2.444s
ok github.com/novox/mesh-controller/internal/store 6.711s
ok github.com/novox/mesh-controller/internal/testbus 1.224s
ok github.com/novox/mesh-controller/internal/token 1.016s
**Merge check** at `07e59c53`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791558643202596388` (`builds --log build-1791558643202596388`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T15:04:05Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T15:04:05Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 244.264s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.064s
ok github.com/novox/mesh-controller/internal/broker 8.942s
ok github.com/novox/mesh-controller/internal/builder 3.285s
ok github.com/novox/mesh-controller/internal/catalogue 4.951s
ok github.com/novox/mesh-controller/internal/conditions 2.514s
ok github.com/novox/mesh-controller/internal/envfile 1.032s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 11.381s
ok github.com/novox/mesh-controller/internal/inventory 96.916s
ok github.com/novox/mesh-controller/internal/lease 17.681s
ok github.com/novox/mesh-controller/internal/licences 10.866s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.012s
ok github.com/novox/mesh-controller/internal/link 57.720s
ok github.com/novox/mesh-controller/internal/lint 2.156s
ok github.com/novox/mesh-controller/internal/outward 1.032s
ok github.com/novox/mesh-controller/internal/overlay 1.025s
ok github.com/novox/mesh-controller/internal/secrets 2.444s
ok github.com/novox/mesh-controller/internal/store 6.711s
ok github.com/novox/mesh-controller/internal/testbus 1.224s
ok github.com/novox/mesh-controller/internal/token 1.016s
```
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.
Reviewers' checklist (the same on all four PRs)
link.CLIMaxStdin): over it the request is refused and nothing runs.runForMeshCLI); an ordinary call carrying any is refused, and nothing runs.answerCLIrecordscliRecorded(msg.Data), which drops it and keeps onlystdin-given: true;keptalso replaces astdinkey, so neither path can keep it. Never in the journal (the line's first word only, as before), never in an answer.mesh.control.<node>.cli. The CONTROL stream namesmesh.control.*.reportandmesh.control.enrolonly, so nothing persists it; only the controller is grantedmesh.control.>; each hop is TLS to the pinned bus certificate. Not sealed end to end: the bus server holds it in memory while routing. Sealing would need a controller key every engine knows; none exists today.link.CLIAsked), held to the engine's by the field-name tests on both sides.Tests
TestStandardInputReachesSecretAcceptAtTheTerminalAndNowhereElse(cmd): the test binary runs assecret accept <node> <module> <name> [--from -]and reads its value withvalueFor, exactly assecret acceptdoes, comparing a digest; both forms read what mesh-cli carried; with no input it reads nothing; an ordinary line carrying input is refused and runs nothing; neither the answer nor the journal holds the value.TestAMeshCLIRecordNeverKeepsItsStandardInput(link): no form of the value in the record, by either path; the record still decodes as the request so the asker can follow its call.stdin.merge-check: targeted tests pass locally; the full suite with -race is running and its result is posted here. Do not merge without review. Order: mesh-sdk #15 (tag), then this, mesh-host #73 and mesh-catalog #164 in any order (each alone is inert: without the engine's forwarding no input arrives; without this, input arriving is not given to the line — as today).
Delivery
novox/mesh-controller@07e59c535e7c— superseded since 2026-10-09T16:11:00ZCovered: delivered after its walk was superseded: the walk plan-1791562260243950312, which took its walk plan-1791562212728626197 over, ended done
Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Group
feat/a-terminal-line-takes-standard-input: novox/mesh-controller@07e59c535e, novox/mesh-host@4ea6a2f04e, novox/mesh-sdk@f047d0a4a9Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
ba97297fmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.62s)Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791558145538913925(builds --log build-1791558145538913925).Merge check at
07e59c53mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791558643202596388(builds --log build-1791558643202596388).