3 Commits

Include renames

Author	SHA1	Message	Date
jochen	dfb14151bd	Say in the plan that a unit is restored only if it is still as the mesh held it ... Confirmation pass of #66: the plan is a preview, and the removal reads the unit when it runs; a masked unit or one changed since is left as it is.	2026-10-09 02:03:51 +02:00
jochen	a018ebd1ca	Pass -- before every unit, and give a unit back only when it is exactly as the mesh held it ... Third review of mesh-catalog #147. A unit's name can now come from a setting (a template's instance), so every systemctl call that names a unit passes `--` before it, and a name can never be read as an option. On removal, a unit is started or enabled again only when it is exactly the stopped and disabled the mesh held it to. A masked unit, or one somebody started or enabled since, is left as it is, and the report says why. A restore that fails (the start refused, or the unit not running after it) puts back what this attempt changed and is reported as waiting, so no apply is made fatal by it and the next one tries again. The tests' fake service managers read systemctl's arguments in the shape they were written for (oldShape); internal/system's own test holds the `--`.	2026-10-09 01:54:26 +02:00
jochen	9d48b8baf9	Start again on removal what the mesh's own declaration stopped (hq ADR 0269) ... A unit found running and enabled that a declaration held stopped and disabled stayed stopped and disabled when the declaration went: ADR 0118 never starts a unit on the way out. Unassigning the zfs module would so have left the home server's pool with no scrub schedule at all, said nowhere. The host now records what it declared for a service (Declared, beside Found). On removal, a unit found running and declared stopped is started again, and one found enabled and declared disabled is enabled again, each read back; the report says restored, and the plan says it first. A record from before the field starts nothing.	2026-10-09 01:35:27 +02:00