Follow-up to #69 (hq ADR 0272, second confirmation review).
The engine reads the asking process's cgroup (/proc/<pid>/cgroup, unified line) and sends its login session's scope — session-<id>.scope directly under the account's own user-<uid>.slice — as session, or nothing: a service under system.slice (the tool runner), a unit of the account's user manager (user@<uid>.service/...), another account's session, anything below a scope. The controller (mesh-controller follow-up feat/272-the-terminal-said-explicitly) makes no other line the terminal.
session is carried on follows too; field-name test updated (the controller's side holds the same list).
SDK pinned at the tag go/v0.1.9 (cd01c370, #14's merge).
README: only a login session can be the terminal.
Tests.TestTheLoginSessionAskingIsReadFromTheKernel: seven cgroup shapes (session scopes, user@ unit, system service, another uid's session, a path below a scope, empty) and the session sent for the test process as the kernel says it; fails before (no Session). merge-check.sh passes locally (throwaway nats-server).
Order. Either order with the controller follow-up: an older controller ignores session (unknown JSON field), and an older engine sends none, so the newer controller makes nobody the terminal until this engine is live — fails closed.
Follow-up to #69 (hq ADR 0272, second confirmation review).
- The engine reads the asking process's cgroup (`/proc/<pid>/cgroup`, unified line) and sends its login session's scope — `session-<id>.scope` directly under the account's own `user-<uid>.slice` — as `session`, or nothing: a service under `system.slice` (the tool runner), a unit of the account's user manager (`user@<uid>.service/...`), another account's session, anything below a scope. The controller (mesh-controller follow-up `feat/272-the-terminal-said-explicitly`) makes no other line the terminal.
- `session` is carried on follows too; field-name test updated (the controller's side holds the same list).
- SDK pinned at the tag `go/v0.1.9` (cd01c370, #14's merge).
- README: only a login session can be the terminal.
**Tests.** `TestTheLoginSessionAskingIsReadFromTheKernel`: seven cgroup shapes (session scopes, user@ unit, system service, another uid's session, a path below a scope, empty) and the session sent for the test process as the kernel says it; fails before (no `Session`). `merge-check.sh` passes locally (throwaway nats-server).
**Order.** Either order with the controller follow-up: an older controller ignores `session` (unknown JSON field), and an older engine sends none, so the newer controller makes nobody the terminal until this engine is live — fails closed.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
A service running as the operator — the tool runner, a unit of the
account's user manager — shares the operator's user id, and was as much the
terminal on the control-node as a person typing. The engine now reads the
asking process's cgroup and sends its login session's scope
(session-<id>.scope under the account's own user-<uid>.slice), or nothing;
the controller makes nothing else the terminal. The SDK is pinned at its
tag now that go/v0.1.9 exists.
Deliverynovox/mesh-host@4a5dcb0209ff — delivered since 2026-10-09T11:59:44Z
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Machines
mesh-host on ace: passed — healthy 3 times over 2m38s
mesh-host on novox: judging — carried by release-1791546985187428623
mesh-host on the rest running it: sent
Transitions
2026-10-09 11:43 (new) → proposed (announced): novox/mesh-host#70's head announced
2026-10-09 11:48 proposed → checked (checked): the verdict names this commit
2026-10-09 11:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 11:55 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 11:55 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 11:59 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-host@4a5dcb0209ff` — **delivered** since 2026-10-09T11:59:44Z
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m38s
- mesh-host on novox: judging — carried by release-1791546985187428623
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-09 11:43 (new) → proposed (announced): novox/mesh-host#70's head announced
- 2026-10-09 11:48 proposed → checked (checked): the verdict names this commit
- 2026-10-09 11:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 11:55 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 11:55 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 11:59 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-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on novox as build-1791546239078055755 (builds --log build-1791546239078055755).
--- the gate: mesh-host
mesh-host: 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-09T11:35:23Z 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-09T11:35:23Z
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-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.9
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 6.430s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.076s
ok github.com/novox/mesh-host/internal/apply 27.483s
ok github.com/novox/mesh-host/internal/bootstrap 2.714s
ok github.com/novox/mesh-host/internal/bundle 1.021s
ok github.com/novox/mesh-host/internal/declaration 1.065s
ok github.com/novox/mesh-host/internal/firewall 1.896s
ok github.com/novox/mesh-host/internal/identity 1.666s
ok github.com/novox/mesh-host/internal/image 1.024s
ok github.com/novox/mesh-host/internal/inventory 1.023s
ok github.com/novox/mesh-host/internal/link 10.363s
ok github.com/novox/mesh-host/internal/liveness 2.458s
ok github.com/novox/mesh-host/internal/meshcli 1.329s
ok github.com/novox/mesh-host/internal/network 1.050s
ok github.com/novox/mesh-host/internal/outward 1.014s
ok github.com/novox/mesh-host/internal/profile 1.482s
ok github.com/novox/mesh-host/internal/reachable 1.011s
ok github.com/novox/mesh-host/internal/store 2.003s
ok github.com/novox/mesh-host/internal/system 1.011s
ok github.com/novox/mesh-host/internal/tunnel 1.015s
ok github.com/novox/mesh-host/internal/units 1.007s
ok github.com/novox/mesh-host/internal/upgrade 1.719s
ok github.com/novox/mesh-host/internal/witness 30.227s
ok github.com/novox/mesh-host/packaging 1.008s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.007s
**Merge check** at `4a5dcb02`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on novox as `build-1791546239078055755` (`builds --log build-1791546239078055755`).
```
--- the gate: mesh-host
mesh-host: 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-09T11:35:23Z 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-09T11:35:23Z
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-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.9
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 6.430s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.076s
ok github.com/novox/mesh-host/internal/apply 27.483s
ok github.com/novox/mesh-host/internal/bootstrap 2.714s
ok github.com/novox/mesh-host/internal/bundle 1.021s
ok github.com/novox/mesh-host/internal/declaration 1.065s
ok github.com/novox/mesh-host/internal/firewall 1.896s
ok github.com/novox/mesh-host/internal/identity 1.666s
ok github.com/novox/mesh-host/internal/image 1.024s
ok github.com/novox/mesh-host/internal/inventory 1.023s
ok github.com/novox/mesh-host/internal/link 10.363s
ok github.com/novox/mesh-host/internal/liveness 2.458s
ok github.com/novox/mesh-host/internal/meshcli 1.329s
ok github.com/novox/mesh-host/internal/network 1.050s
ok github.com/novox/mesh-host/internal/outward 1.014s
ok github.com/novox/mesh-host/internal/profile 1.482s
ok github.com/novox/mesh-host/internal/reachable 1.011s
ok github.com/novox/mesh-host/internal/store 2.003s
ok github.com/novox/mesh-host/internal/system 1.011s
ok github.com/novox/mesh-host/internal/tunnel 1.015s
ok github.com/novox/mesh-host/internal/units 1.007s
ok github.com/novox/mesh-host/internal/upgrade 1.719s
ok github.com/novox/mesh-host/internal/witness 30.227s
ok github.com/novox/mesh-host/packaging 1.008s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.007s
```
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.
Follow-up to #69 (hq ADR 0272, second confirmation review).
/proc/<pid>/cgroup, unified line) and sends its login session's scope —session-<id>.scopedirectly under the account's ownuser-<uid>.slice— assession, or nothing: a service undersystem.slice(the tool runner), a unit of the account's user manager (user@<uid>.service/...), another account's session, anything below a scope. The controller (mesh-controller follow-upfeat/272-the-terminal-said-explicitly) makes no other line the terminal.sessionis carried on follows too; field-name test updated (the controller's side holds the same list).go/v0.1.9(cd01c370, #14's merge).Tests.
TestTheLoginSessionAskingIsReadFromTheKernel: seven cgroup shapes (session scopes, user@ unit, system service, another uid's session, a path below a scope, empty) and the session sent for the test process as the kernel says it; fails before (noSession).merge-check.shpasses locally (throwaway nats-server).Order. Either order with the controller follow-up: an older controller ignores
session(unknown JSON field), and an older engine sends none, so the newer controller makes nobody the terminal until this engine is live — fails closed.Delivery
novox/mesh-host@4a5dcb0209ff— delivered since 2026-10-09T11:59:44ZDelivery plan — builds mesh-host → 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
4a5dcb02mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791546239078055755(builds --log build-1791546239078055755).