4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	1bc5719b8b	Feature 57 (config and provisioning): release mesh-sdk, the reviewed release branch on top of main	2026-10-16 08:24:11 +00:00
jochen	d49d3a14d8	0.1.14: the provider loop says a consumer it keeps failing on the bus, and its recovery (hq ADR 0224, issue 272) ... No provider on runProvisioner passed announce, and the loop had no standing per consumer, so the object store, the SQL and document stores, the mail server and the others failed their consumers in their journals alone. The loop now keeps the Go copy's standing (failing after five minutes, again every fifteen, recovered on success, when unasked or retired, and on the first success since start) and says it through the SDK's emit unless given another announce.	2026-10-13 08:26:33 +02:00
jochen	0704908d0b	Retire only after ten minutes as well as five passes, and never through remove ... Five passes are 25 s, shorter than a real hiccup. And a provider's remove can destroy — a ledger file, a public DNS record — so an adapter without a retire of its own is mark-only: the consumer keeps its access, is marked and said, and remove is reached only by a person's delete (hq ADR 0230).	2026-10-06 14:30:39 +02:00
jochen	e0453316b8	0.1.12: retire a consumer the mesh stops asking for, after five stable passes, and wait for a person over the bound ... The hourly release let a mistaken bulk unassignment drain one consumer an hour with nobody deciding. Per novox/hq ADR 0230 a consumer is retired (disabled, marked, data kept) only after the same unasked set in five consecutive passes; more than 3, or more than half of those held, waits for approve or reject. Deletion is a separate act of a person, of a retired consumer only.	2026-10-06 13:47:51 +02:00