From c8935acecad650f6fdc2592ab4f288022533a04c Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 2 Oct 2026 11:31:29 +0200 Subject: [PATCH] Issue 194 resolved: the fixed host forgot its former archive on all four machines --- .../00-report.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/04-ISSUES/194-the-hosts-own-former-archive-stops-every-apply/00-report.md b/04-ISSUES/194-the-hosts-own-former-archive-stops-every-apply/00-report.md index 56b920a..bb1cc06 100644 --- a/04-ISSUES/194-the-hosts-own-former-archive-stops-every-apply/00-report.md +++ b/04-ISSUES/194-the-hosts-own-former-archive-stops-every-apply/00-report.md @@ -1,8 +1,8 @@ --- -status: located +status: resolved opened: 2026-10-02 located-in: [mesh-host internal/apply (removeOrphan: a former target of a kind with no removal was fatal), mesh-host internal/store (Record keeps a former target for every kind, the host's own archive included)] -fixed-by: +fixed-by: mesh-host 65 — a former target of a kind the host cannot remove is left in place, said and forgotten; a dropped archive still refuses amended-design: --- @@ -62,3 +62,10 @@ because the alternative was four machines that could apply nothing. - Is there a bed that replaces a host under the current rules before the live mesh does (the proof row of [ADR 0141](../../02-DECISIONS/0141-the-host-delivers-its-own-successor.md) was a single crossover, before former targets existed)? + +## Resolved, 2026-10-02 + +mesh-host 65, merged 07:35Z. Recovered as the record above says: the operator dropped the one +`@former:` entry from each machine's host record and pushed; the fixed host then ran on all four and +its first apply said `forgotten mesh-host.next@former:… a former target left in place` and applied the +rest. The open questions stand as questions for the host's own versions, not as faults.