This PR: carried() reads non-terminal standard input up to the bound and asks with cli.AskWith; the usage says it. Tests: a pipe's input reaches the engine whole and is not printed; a terminal is not read; over the bound is refused with nothing asked; the other tests read their standard input as a terminal so a runner's open pipe never hangs them. mesh-sdk at f047d0a until its tag.
MESH_CHECK_MODULES=mesh-cli sh merge-check.sh passes locally. Do not merge without review.
**Reviewers' checklist (the same on all four PRs)**
- Standard input is bounded at 64 KiB; over it mesh-cli refuses before asking anything.
- Only a pipe or a file is read; a terminal (or /dev/null) never is, so an interactive line asks as before.
- Nothing carried is printed.
- The controller gives it to a terminal line alone and keeps it nowhere (its PR); the engine forwards it with the line alone (its PR).
**Use**: `mesh-cli secret accept <node> <module> <name> --from - < file`, or `read -rs v; printf %s "$v" | mesh-cli secret accept …`.
**This PR**: `carried()` reads non-terminal standard input up to the bound and asks with `cli.AskWith`; the usage says it. Tests: a pipe's input reaches the engine whole and is not printed; a terminal is not read; over the bound is refused with nothing asked; the other tests read their standard input as a terminal so a runner's open pipe never hangs them. mesh-sdk at f047d0a until its tag.
`MESH_CHECK_MODULES=mesh-cli sh merge-check.sh` passes locally. Do not merge without review.
mesh/merge-gate pass: builds mesh-cli → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
So a secret reaches the controller's terminal without standing on a command line:
mesh-cli secret accept <node> <module> <name> --from - < file. A terminal is never read, more than the
bound is refused before anything is asked, and nothing carried is printed. mesh-sdk moves to f047d0a.
Deliverynovox/mesh-catalog@f3dcb9dc5a1e — delivered since 2026-10-09T16:03:29Z
Delivery plan — builds mesh-cli → ace, g14, novox, shanks; no bus step
tier 0: mesh-cli
ace: receives mesh-cli
g14: receives mesh-cli
novox: receives mesh-cli
shanks: receives mesh-cli
Machines
mesh-cli on ace: passed — healthy 3 times over 2m33s
mesh-cli on the rest running it: sent
Transitions
2026-10-09 14:51 (new) → proposed (announced): novox/mesh-catalog#164's head announced
2026-10-09 14:53 proposed → checked (checked): the verdict names this commit
2026-10-09 14:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 15:59 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 15:59 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:03 delivering → delivered (done): its walk is done: 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-catalog@f3dcb9dc5a1e` — **delivered** since 2026-10-09T16:03:29Z
**Delivery plan** — builds mesh-cli → ace, g14, novox, shanks; no bus step
- tier 0: mesh-cli
- ace: receives mesh-cli
- g14: receives mesh-cli
- novox: receives mesh-cli
- shanks: receives mesh-cli
**Machines**
- mesh-cli on ace: passed — healthy 3 times over 2m33s
- mesh-cli on the rest running it: sent
**Transitions**
- 2026-10-09 14:51 (new) → proposed (announced): novox/mesh-catalog#164's head announced
- 2026-10-09 14:53 proposed → checked (checked): the verdict names this commit
- 2026-10-09 14:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 15:59 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 15:59 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:03 delivering → delivered (done): its walk is done: 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds mesh-cli → ace, g14, novox, shanks; no bus step
tier 0: mesh-cli
ace: receives mesh-cli
g14: receives mesh-cli
novox: receives mesh-cli
shanks: receives mesh-cli
Run by the build seat on shanks as build-1791557507574159524 (builds --log build-1791557507574159524).
--- the gate: mesh-cli
mesh-cli: ok
long-running resources without health: 0
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-09T14:42: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:42:25Z
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 1 module(s) in 1 tier(s): mesh-cli
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 35272 strings of 615 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/mesh-cli
ok mesh-cli/cmd/mesh-cli 1.013s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `f3dcb9dc`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds mesh-cli → ace, g14, novox, shanks; no bus step
- tier 0: mesh-cli
- ace: receives mesh-cli
- g14: receives mesh-cli
- novox: receives mesh-cli
- shanks: receives mesh-cli
Run by the build seat on shanks as `build-1791557507574159524` (`builds --log build-1791557507574159524`).
```
--- the gate: mesh-cli
mesh-cli: ok
long-running resources without health: 0
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-09T14:42: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:42:25Z
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 1 module(s) in 1 tier(s): mesh-cli
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words, none in the 35272 strings of 615 files
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/mesh-cli
ok mesh-cli/cmd/mesh-cli 1.013s
--- its merge-check-typescript.sh (typescript toolchain)
```
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)
Use:
mesh-cli secret accept <node> <module> <name> --from - < file, orread -rs v; printf %s "$v" | mesh-cli secret accept ….This PR:
carried()reads non-terminal standard input up to the bound and asks withcli.AskWith; the usage says it. Tests: a pipe's input reaches the engine whole and is not printed; a terminal is not read; over the bound is refused with nothing asked; the other tests read their standard input as a terminal so a runner's open pipe never hangs them. mesh-sdk at f047d0a until its tag.MESH_CHECK_MODULES=mesh-cli sh merge-check.shpasses locally. Do not merge without review.Delivery
novox/mesh-catalog@f3dcb9dc5a1e— delivered since 2026-10-09T16:03:29ZDelivery plan — builds mesh-cli → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
f3dcb9dcmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-cli)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds mesh-cli → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791557507574159524(builds --log build-1791557507574159524).