4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	d7a880a608	Say once after a restart that nothing waits, so an old retirement condition clears (issue 937) ... The controller clears a provider's retire-waiting condition only on its settled word, and a provider says settled only for a set its own memory held. A provider restarted after the set stopped waiting (here: the delivery of the grant-file fix) never says it, so the condition kept asking the operator to approve retiring what nobody waits on. The first pass of a process that finds every consumer asked now says settled once, with no set; the controller clears both conditions on it.	2026-10-16 16:42:39 +00:00
jochen	685cb1cb1b	Declare every module's data; the backup holder measures it (hq ADR 0233) ... Backup lines are derived from each module's data section instead of written by hand; the holder measures declared items, reads the array under them, and deletes a retired item only after a last restore point; the Go providers say each held consumer's size so an empty replacement is seen.	2026-10-06 16:47:49 +02:00
jochen	2c15074a0b	Retire only once the same answer has held ten minutes as well as five passes ... Five passes are twenty-five seconds, shorter than a controller restart, a store reconnecting or a file half written; the operator asked for both (hq ADR 0230).	2026-10-06 14:28:21 +02:00
jochen	e68ef88333	Retire a consumer the mesh stops asking for, and delete only on a person's word (hq ADR 0230) ... The hourly release of ADR 0229's brake still ended in the mesh acting alone on a mistake. A consumer now stays active until the same unasked set holds for five passes, waits for a person past three or half of those held, is disabled and marked rather than withdrawn, comes back as it was when asked again, and is deleted only through the provider's delete tool. The backend keeps the mark, so a restart forgets nothing and finds what was withdrawn before.	2026-10-06 13:54:10 +02:00