Answer A-249: the tool runner takes a chunked answer whole for a bundle

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 20e3e1a3cd
commit 7e9bb2dab4
1 changed files with 4 additions and 0 deletions
@@ -266,3 +266,7 @@ the principle that settles it, cited as "design 47 G A-n".
  through the build seat's `steps`; the ask is put through the delivery SDK's `buildrun.Asker`.
 - **A-248** (A-163, A-232; principle 8) `buildrun.Asker` gains the asker its subject names (the caller's seat name,
  A-163), empty meaning the builder until the asker rename at the join; the ask's own `Asker` field is left as it is.
+- **A-249** (A-237; principles 7 and 8) A bundle takes a chunked seat answer through its ordinary seat call: the tool
+  runner receives the chunks with `buscalls.SeatChunks` and hands the bundle the whole answer, so no bundle receives
+  chunks itself. mesh-build-go's `inputOf` calls the mesh-catalog seat's `input` that way and decodes that verb's
+  own answer form.