jschoubben 054754482c The running provisioner account is kept only for a client held this pass, and rows hold the guard (issue 774, review) ...

The review removed the guard and the suite still passed. The guard is now provisionerHeld, a placed client held as
its stand-in, rather than any placed client, so one placed and not held that composes no account keeps none stale.
Rows in the held client's table: the client taken out of the node's placement while what runs names the account, read
from the running own composition and from the client's running process, names no account; a placed client whose
process names no user names none. With the guard removed the first three fail; with it reduced to "placed", the last.

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

2026-11-04 01:53:29 +01:00

..

accounts

Revert "Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' (#174) from revert/774-l3 into main"

2026-10-29 21:04:13 +01:00

agent

node-engine.composition shows the node's own fields and what the last pass held (issue 774)

2026-11-04 01:50:21 +01:00

apply

The witness judges the tool runner's process by its id, <its module>.runtime, which the composition gives only the module whose manifest says it is the tool runner, never by a name (ADR 0601 §4; review round 1, finding 4)

2026-11-03 14:02:01 +01:00

beside

Take the catalogue's composition rules into the node-engine

2026-11-02 19:15:55 +01:00

bootstrap

Genesis installs no catalog module: the catalogue step and the take of mesh-catalog go (ADR 0604 section 7, issue 774)

2026-11-03 16:17:27 +01:00

bundle

Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)

2026-10-20 11:17:14 +00:00

compose

The running provisioner account is kept only for a client held this pass, and rows hold the guard (issue 774, review)

2026-11-04 01:53:29 +01:00

composer

An input carries the modules it holds as their stubs across the bus, and the sandbox names why the node-engine holds one (issue 774, group check 278aa5f0ccbe)

2026-11-04 00:45:35 +01:00

filling

Remove the mesh-cli forward to the controller

2026-11-02 11:28:35 +01:00

firewall

Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)

2026-10-20 11:17:14 +00:00

identity

mesh-host enrol redeems through the seat mesh-enrolment and refuses an answer the token's key did not sign

2026-11-02 01:49:01 +01:00

image

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

inventory

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:44 +02:00

judge

The node-engine owns the composition it alone runs (H1, H2)

2026-11-02 18:24:05 +01:00

link

The node record states the reader capabilities of the mesh-sdk the engine is built with (ADR 0614 §4, issue 774)

2026-11-03 23:29:17 +01:00

liveness

Apply a module again when the engine holds no record of its resources or its health says one is missing, and move a module with nothing to back up without a backup (issue 1944, issue 1945)

2026-10-25 10:59:21 +01:00

network

Write each node's health report into its own key of mesh-host_health on a change, so the watchman raises the machine's alerts without the controller (issue 774, the operator's alert table)

2026-10-29 22:56:14 +01:00

nodegrant

The node whole publishes its compositions and answers a candidate (H6)

2026-11-02 18:39:12 +01:00

outward

Report the networks the outward links are on, for the local network (issue 154, ADR 0340)

2026-10-13 11:20:21 +02:00

overlay

Merge five moved overlay tests into two, offsetting the tests this release adds

2026-11-02 18:39:51 +01:00

profile

The node-engine reports reads-wants; a failed apply is said; the have's fingerprint and digest follow its health (R6-A A6)

2026-10-24 16:43:26 +02:00

reachable

Report what an adopted node holds, its firewall and what is reachable, and speak unasked when that changes (hq ADR 0100)

2026-09-22 17:22:31 +02:00

selfcompose

node-engine.composition shows the node's own fields and what the last pass held (issue 774)

2026-11-04 01:50:21 +01:00

store

The node-engine hears no declaration: the queue, orders, put-backs, unsaid, numbers and news go; a session says the facts in the node-engine's own order, and the first have proves a build (R6-A A7, A8)

2026-10-24 16:25:11 +02:00

system

Drop the never-ran reading: a start timestamp of 0 does not mean a one-shot never ran (issue 1126)

2026-10-28 14:29:16 +01:00

takein

The node-engine owns the composition it alone runs (H1, H2)

2026-11-02 18:24:05 +01:00

tunnel

A taken tunnel's found configuration is retired once the take is proven (hq ADR 0119)

2026-09-27 00:47:57 +02:00

units

Take the node-engine's parser from mesh-sdk: remaining imports (issue 1392)

2026-10-20 11:17:14 +00:00

upgrade

Merge remote-tracking branch 'origin/main' into feat/r6

2026-10-24 23:00:09 +02:00

userlist

Read the bus's user-list file's place from what the node runs, not from the controller's compositions

2026-11-02 11:34:15 +01:00

validate

The node-engine owns the composition it alone runs (H1, H2)

2026-11-02 18:24:05 +01:00

witness

The witness judges the tool runner's process by its id, <its module>.runtime, which the composition gives only the module whose manifest says it is the tool runner, never by a name (ADR 0601 §4; review round 1, finding 4)

2026-11-03 14:02:01 +01:00