jschoubben 8e32583089 A node names its provisioner client's account whenever a client runs there, filled files or not (issue 774) ...

The declaration named the account only beside its filled files (node.go), so a node whose every filled-file module
was held this pass named none: on ace from 2026-11-04 01:29 its build modules and ssh-client were held for their
forge binding, and the node-engine refused every write of the files they keep, and of every other module's. The
account is the node's, named whenever the rendering has one. A row holds restic, the provisioned mesh's one
filled-file module, with the client placed: the node's own still names the account; it named none before.

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

2026-11-04 02:17:01 +01:00

..

testdata

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

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

frombustest_test.go

A node names its provisioner client's account whenever a client runs there, filled files or not (issue 774)

2026-11-04 02:17:01 +01:00

frombustest.go

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

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