From beac2c0170f2e32b27e3d850ca531bc326a5168f Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:06:32 +0100 Subject: [PATCH] Answer A-218: pipeline-waits clears when the new runner runs healthy Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 37b257eb..a1103d43 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -154,3 +154,5 @@ the principle that settles it, cited as "design 47 G A-n". in an earlier assignment graph revision than the one it now runs from, by the revisions' own numbers; the running manifest is the catalog entry of the fingerprint the node-engine seat's `running` names, read through the catalog seat's `entry`, and `FormChanges` compares it with the want's entry. +- **A-218** (A-206, §696; principle 3) `pipeline-waits` is cleared when the node-engine seat's `running` says the + awaited runner fingerprint healthy; A-206's `runner version` holds over §696's wording.