mesh-host

Files

T

jschoubben ccc86d3594 Put the tool runner in the own group of each module whose tools it runs (hq ADR 0334 §2)

A joining module's own directories belong to its own group, and its tools run in the
tool runner, which could not read them. An identity may now name the tool runner's
account: the engine puts it in mesh-<module> as it puts it in a library's group,
says the change as identity:<module> for the runner's unit to restart once, takes
it back when no identity names it, and refuses an account that is missing or root's.
The engine states contract 7.

2026-10-13 00:06:29 +02:00

declared_keys_test.go

Give a service's held state its own field and key, so main compiles again

2026-10-09 03:03:58 +02:00

declared_test.go

A node that loses its mesh comes back on its own

2026-08-29 20:17:49 +02:00

declared.go

Refuse a declaration for the other mode, or older than the mesh's last, and say what an apply would change first

2026-09-23 23:15:28 +02:00

former_test.go

A take is a comparison: the host's facts, former targets, and strays (hq ADR 0163)