mesh-build-node consumes the seat list's events, so its runtime's consumer exists

Its runtime follows the seat list (seatlist.Start subscribes to mesh-catalog.seat-definition-changed and -removed); with no consumes
there was no consumer shanks_mesh-build-node_tools, the seat list was never read and the asks of a named asker were given back.

Builds: design 47 G A-488a (hq 25df48ad)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-19 13:41:12 +01:00
parent be993cb2c5
commit daa5d3ea5f
2 changed files with 12 additions and 0 deletions
+4
View File
@@ -24,6 +24,10 @@
"serves": ["current", "drop", "pause", "resume", "steps", "kept-artifact", "output"]
}
],
"consumes": [
"mesh-catalog.seat-definition-changed",
"mesh-catalog.seat-definition-removed"
],
"config": {
"capacity": {
"type": "number",