Design 47 H: H-A-367, the build-step part's forms

This commit is contained in:
2026-11-21 23:19:53 +01:00
parent 9dea4eefed
commit b0f8d434e6
@@ -2281,3 +2281,10 @@ Where two preparers disagreed, the chosen one is named.
- **H-A-366 (a bundle purges an object's leftovers, 23:15)** The registry's purge of a deleted object's chunks is an
objects act of the runtime: mesh-sdk's bundle objects gain Purge, served by the tool runner, the same shape as the
process side's; the registry's program does not open its own connection for it. P9, P12.
- **H-A-367 (the build-step part's forms, 23:19)** Yes to the four, part form 2: (1) output takes the ask and answers
the ask, the output's last 64 KB, its size, the failing tests with their words, and whether it is no longer kept;
call and chunks go. (2) current answers the node, whether it takes asks, why not (paused, capacity 0, unhealthy),
since when, its capacity and the asks it runs (id, kind, module, started), whoever asked them. (3) the step's end
gains not-run as a list of test and reason. (4) the Node build seat accepts the kind install (id, asker, pipeline,
module, commit, the lock's text at the commit); the step's end gains the archive object's name; a step ask names
the archive the Go build module unpacks. P3, P7, tools-are-how-a-module-is-spoken-to.