A check that could not run is asked again on the node-engine seat's running of its part (milestone 47/G W6.9b, issue 1373)

The checker consumes node-engine.running (kept last per subject) through its durable
consumer and hands each running.<node>.<module> to PartRunning; a body naming no part
asks nothing and is said. Naming the not-heard part by its module (the seat git's holder,
a build seat's holder) waits on the catalog half's claims (W3.6): until then the part is
unnamed and the first running asks the check again.

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

Builds: design 47 G §253, §315
This commit is contained in:
2026-11-11 14:49:20 +01:00
parent 0b7cec27e8
commit fe025a3b73
5 changed files with 65 additions and 2 deletions
+2 -1
View File
@@ -27,7 +27,8 @@
"mesh-delivery-indexer.views.packages",
"mesh-delivery-indexer.views.predefined",
"mesh-delivery-indexer.views.seat-definitions",
"mesh-conditions.findings-asked"
"mesh-conditions.findings-asked",
"node-engine.running"
],
"streams": [
{ "name": "checks", "events": ["preview.**", "owed.**", "try.**"] },