2 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	133e10a738	Issue 102 resolved, verified on the machine with both forwarders gone; 097's orphan was on the host network ... The addresses follow: the control plane holds the ports the node gave, a recorded build holds no address at all, and the two forwarders that had been holding the control plane together are removed. 097's stranded container turned out to be listening on every interface and connected to the mesh's store — by its own old database, which is the only reason nothing was at risk.	2026-09-24 00:02:13 +02:00
jschoubben	235b9ea0e5	Issues 096 and 097, and 094 diagnosed: a setting stored where it cannot work, and a resource that changed target ... 094's cause is one blind spot read from two ends, written up in its diagnosis; the fix answers the first open question and not the other two, which become 096. 097 was found looking at what the forge's cutover left running.	2026-09-23 02:20:48 +02:00