Answer A-276: a pipeline-waits finding names its awaited fingerprint in its evidence

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 11:19:18 +01:00
parent e98e675673
commit 3631a151a3
1 changed files with 3 additions and 0 deletions
@@ -362,3 +362,6 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-275** (§558, A-102; principles 3 and 7) The node-engine's self-composition reads a manifest's `invokes` with
  mesh-sdk's `catalogue.readInvokes`, which reads the short and the long form alike; no part keeps its own reader of a
  manifest field, and a form it cannot read is refused, never taken as no seats.
+- **A-276** (A-218, A-206; principles 3 and 7) A `pipeline-waits` finding names the awaited runner fingerprint in
+  one evidence entry `awaited <fp>`, written when the finding is raised; the runner clears exactly the findings whose
+  entry names the fingerprint its node-engine says `running` healthy. Its summary is never parsed.