jochen 5d5dccdd55 A login the mesh set is given back, and undeclaring one no longer stops the apply (hq issue 225) ...

A user had no removal, so an undeclared one failed as an orphan and
aborted every apply after. Removal now keeps the account, gives back
the shell recorded when the mesh first changed it if it is still the
mesh's and still usable, and says why otherwise (hq ADR 0176 §2).
A shell is refused before it is set unless it is executable and listed
in /etc/shells, since usermod succeeds on a missing one.

2026-10-04 03:57:34 +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)

2026-10-01 21:24:37 +02:00

lock_test.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode

2026-09-23 23:35:49 +02:00

lock.go

Refuse every file once the mesh has spoken, plan the cutover as one, and let the kept declaration repair the mode

2026-09-23 23:35:49 +02:00

store_test.go

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

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

store.go

A login the mesh set is given back, and undeclaring one no longer stops the apply (hq issue 225)

2026-10-04 03:57:34 +02:00