Answer A-192: the watchman hears waits and running, reads no other state

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 88e0ca6f2d
commit 39b4149687
1 changed files with 4 additions and 0 deletions
@@ -47,3 +47,7 @@ the principle that settles it, cited as "design 47 G A-n".
 - **A-191** (§33, §540; principle 3) A `pipeline-failed` finding whose commit no pull request merged, or whose `pull`
  read fails, is written with no `owner` (so it reaches the operator at once) and says why in its explanation; a
  failed read is said and the owner is written at the next step end of that commit.
+- **A-192** (ADR 0596, ADR 0603 §8, §499, §541, §520; principles 1 and 7) The builder says `wait-held` and `wait-ended`
+  for a key queued behind a package, in the one wait form with its `part`, and the watchman times it from those; its
+  reads of the builder's `builds`, the node-engine's `have` and `mesh-host.health` go, replaced by the node-engine's
+  `running` (with `healthy`) and its wait events.