From 4f9c6410e9016f9ca6c6d8913b9ada08fa47926d Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 13:55:01 +0100 Subject: [PATCH] Design 47 H2: H-A-472, orphaned durables are removable and ignored by the behind check --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index beed3432..747ca7d5 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -891,3 +891,12 @@ The lead's one-line answers to the questions H2's develop and review raise (impl out a merged member carrying that note, at the call and at the start's re-say alike, by the kept field, not by reading the watched branches again. Unwatched is a repository with no entry or an empty set in the watched registrations; a watched repository whose base branch is unwatched stays refused as today. P3. +- **H-A-472 (an orphaned durable is removable, and the behind check ignores it, 14:00)** The operator, 13:37: remove + the orphaned durables. (1) The bus module's `nats_consumer_remove` removes a durable named for a module of an accepted + manifest when that module's live twin on the same stream exists and is current (a durable with pulls waiting and a + delivery within the day), the act recorded in the hand-act log with the twin named; it keeps refusing a module's only + durable (H-A-127/128 hold for that case). (2) The grants part's consumer-behind check leaves out a durable with no + pulls waiting whose twin on the stream is current, and names such orphans once in a finding of their own + (`durable-orphaned`, cleared when removed), so the alarm says a real backlog only. (3) A part that renames its + durable removes the old name at its first start under the new (the tool runner for the modules it carries), so the + orphans do not come back. P-failure-loud, P3.