mesh-controller

Files

T

jochen 51c8c7ec52

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…

Details

mesh/repo-check pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

Say the terminal explicitly, only from a login session, and name the unannounced pull request (hq ADR 0272)

- commandEnvironment takes the terminal as a bool instead of reading an
  empty verb as one; every non-terminal line names its verb and is stripped
  of MESH_CLI_TERMINAL, and a test with the mark set in the serving
  environment fails when that strip is taken out.
- On the control-node the operator's account is the terminal only from a
  login session, as the node-engine reads it from the kernel's cgroup; the
  tool runner and the account's user units run as the operator too, and are
  ordinary calls. The request carries `session` (field-name tests on both
  sides).
- A pull request the forge never announced is named with its number in
  the condition's headline (hq issue 347), from the stalled line's
  `number`, which mesh-delivery sends.

2026-10-09 13:41:32 +02:00

artifacts

Leave an eligible index for a confirmed collect instead of letting it go alone

2026-10-08 15:47:42 +02:00

broker

mesh-cli lines are calls, followed to their answer; the terminal does not follow assign (review of hq ADR 0272)

2026-10-09 12:48:12 +02:00

builder

Let platform manifests go only on a confirmed collect, and copy again what a sweep took

2026-10-08 15:47:42 +02:00

catalogue

Fill machine facts in a user's home, so an agent account named with a home is made there