BM4: each build module keeps a run's test output in its outputs objects

The Go build module's level answers its text in output (test2json's Output
lines), the Node build module's what its commands wrote; the delivery SDK's step
run keeps it as <node>.<ask> in the module's outputs objects, which each module
asks for in requires (1 GiB, kept 7 days) and reads through the verb output at
form 2. Each module's kit test runs the SDK's SeatVerbs.

Builds: design 47 H2 §791, §820; H-A-412 (1), H-A-412 second addendum (a), H-A-421, H-A-434
This commit is contained in:
2026-11-22 01:32:40 +01:00
parent 46990669de
commit 1697b7041c
15 changed files with 154 additions and 27 deletions
+1
View File
@@ -70,6 +70,7 @@
"requires": [
{"name": "steps", "storage": "key-value", "template": "state", "options": {"ttl-seconds": 172800, "objects-max-mib": 256}},
{"name": "detected-steps", "storage": "key-value", "template": "state", "options": {"history": 1}},
{"name": "outputs", "storage": "object-store", "template": "objects", "options": {"max-mib": 1024, "max-age-days": 7}},
"artifact-store",
"forge-account",
"npm-package-registry",