3 Commits

Include renames

Author	SHA1	Message	Date
jochen	2d18fa3380	Triage issues 228-278: close the fixed, re-check the rest ... Each issue is resolved with its fix and a replay or the reason none exists, or re-checked against main and the live mesh on 2026-10-08.	2026-10-08 01:31:10 +02:00
jochen	3ee27b870d	Issue 244: located — the console drops a mesh seat's node, and a push ran on every machine ... The same empty schemas recurred for push, plan, assign, pin and settings; for push the dropped machine became a push of the whole mesh. Record the evidence, the cause in the console's address form, and the open fixes.	2026-10-06 00:38:37 +02:00
jschoubben	8ade75c550	ADR 0189 collects again; issue 244: a verb with an empty schema cannot be called ... The nightly collector is back on the store (mesh-catalog#57). It was out for a day because while-stopped named the module-local id and the host refuses a declaration naming a container it does not have, whole; the namespacing was fixed the same night and the composition was read before anything was sent this time — plan's distribution.collect shows while-stopped as distribution.store. novox applied it with no refusal and the registry was untouched. The store is 40G at 14:37, the filesystem 56% full; the collector first fires at 03:30. Deleting a manifest frees no bytes until then, so that is the number to read against. 244: mesh-controller.plan and .node publish an empty schema and then refuse with 'needs node', including when node is passed — the console drops what the schema does not declare. A tool that cannot be called is worse than one that is absent, because it is listed. Worked around through the login shell, which is the path the console exists to replace.	2026-10-05 14:38:17 +02:00