jschoubben 22bbb9c2c0 Keep a check's answer within the steps state: leave out the taken versions ...

A catalog check's answer of 264712 bytes was refused by the steps state
(256 KiB per value) and its end written failed without it, so the checker
lost the biggest member's answer and could not preview it. When a passed
or failed end is refused as too large, finish writes it once more without
the fetch's taken versions (fetch.packages, which no reader judges), the
step's reason saying how many were left out, why, and that the module's
journal names each; still too large, it ends failed as before.

Quick fix for issue 1921 (note 91); the thorough fix is design 47 G A-290
(an answer over the bound kept as the object output.<ask>).

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

2026-11-12 16:32:48 +01:00

..

buildcpu

The Go build module says at a build's end which mesh packages its programs import, so a fingerprint can take their content (ADR 0593 §2)

2026-11-02 18:27:33 +01:00

cmd

seatgen: a client may import its contracts module's domain SDK (-domain-sdk; ADR 0634 §2; issue 1966)

2026-11-05 14:41:28 +01:00

conformance

C4: the conformance kit gains Passing with the words of each runner when the network did not answer; each build module's tests call it and checks/failurekit refuses one that does not (ADR 0664, issue 1748)

2026-11-09 23:15:35 +01:00

seatgen

The generated TypeScript parser of a key form names its own parameter and locals apart from the form's parts

2026-11-05 21:24:07 +01:00

testdata

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

askrun_test.go

A check step that errors after its fetch merged still answers its fetch

2026-11-12 15:23:48 +01:00

askrun.go

A check step that errors after its fetch merged still answers its fetch

2026-11-12 15:23:48 +01:00

buildhours.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

capacity_cpu.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

capacity_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

capacity.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

cpu.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

digestshape_test.go

Keep a check's answer within the steps state: leave out the taken versions

2026-11-12 16:32:48 +01:00

fetch_integration_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

fetch_test.go

C2: mesh-build-go says a failure of the network as a transport fault: one download, no retry of its own (ADR 0664 §1, issue 1748)

2026-11-09 23:10:16 +01:00

fetch.go

C2: mesh-build-go says a failure of the network as a transport fault: one download, no retry of its own (ADR 0664 §1, issue 1748)

2026-11-09 23:10:16 +01:00

generated_test.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

generated.go

mesh-build-go runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery: the Puller takes buildstep.StepAsk (the read bridge is the form's own AskAs), the toolchains value is the build runner's own, the stale-step part is buildrun's, keys and values come from the seats and clients (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:05:34 +01:00

go.mod

C2b: a seat verb's no responders is a transport fault when the assigner names a holder of the seat; a seat nothing holds fails at once (ADR 0664 §1, issue 1748)

2026-11-09 23:12:35 +01:00

go.sum

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966)

2026-11-05 16:56:39 +00:00

gotest.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

guard_test.go

mesh-build-go reads a check's toolchain from the job, answers with the Delivery SDK's CheckAnswer and typed FetchAnswer, and takes the toolchains value from the Delivery SDK; askrun_gaps.go and toolchain.go are gone (B5j; ADR 0584 clause 2, ADR 0634 section 6; issue 1966)

2026-11-05 16:24:13 +01:00

guard.go

mesh-build-go reads a check's toolchain from the job, answers with the Delivery SDK's CheckAnswer and typed FetchAnswer, and takes the toolchains value from the Delivery SDK; askrun_gaps.go and toolchain.go are gone (B5j; ADR 0584 clause 2, ADR 0634 section 6; issue 1966)

2026-11-05 16:24:13 +01:00

isolate_caches_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

isolate_integration_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

isolate_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

isolate.go

Bind a run's heads read-only over its workspace, read its input from the state the ask names, and prove the kept programs' sweep (issue 1921, review round 1)

2026-11-06 23:24:48 +01:00

latepublish.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

merge_integration_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

merge_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

merge.go

C2: mesh-build-go says a failure of the network as a transport fault: one download, no retry of its own (ADR 0664 §1, issue 1748)

2026-11-09 23:10:16 +01:00

mirror_integration_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

mirror_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

narrate_test.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

narrate.go

CAT-NR1: every build narrates its asks of a seat in one place

2026-11-04 16:05:27 +01:00

narrow_test.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

narrow.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

pack_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

pack_unix_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

pack.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

phase.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

programs_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

programs.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

publish.go

C2b: a seat verb's no responders is a transport fault when the assigner names a holder of the seat; a seat nothing holds fails at once (ADR 0664 §1, issue 1748)

2026-11-09 23:12:35 +01:00

pull_bus.go

C1: a build step that ends on a transport fault below its last run is written again and handed back to the bus with a delay (ADR 0664 §1, issue 1748)

2026-11-09 23:04:44 +01:00

pull_capacity_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

pull_drop.go

F3: mesh-build-go and mesh-build-node follow the drops other holders write, and a module with no watch says so (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:42:13 +01:00

pull_fake.go

C1: a build step that ends on a transport fault below its last run is written again and handed back to the bus with a delay (ADR 0664 §1, issue 1748)

2026-11-09 23:04:44 +01:00

pull_integration_test.go

C5: the integration row reads the dropped step as dropped (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:44:08 +01:00

pull_seat_test.go

F3: mesh-build-go and mesh-build-node follow the drops other holders write, and a module with no watch says so (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:42:13 +01:00

pull_seat.go

C1: a build step that ends on a transport fault below its last run is written again and handed back to the bus with a delay (ADR 0664 §1, issue 1748)

2026-11-09 23:04:44 +01:00

pull_test.go

C1: a build step that ends on a transport fault below its last run is written again and handed back to the bus with a delay (ADR 0664 §1, issue 1748)

2026-11-09 23:04:44 +01:00

pull.go

F8, dropped: the build module's drop uses the generated contracts' Drop and ends the step dropped, with the named cause (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:41:10 +01:00

refusal.go

F8, dropped: the build module's drop uses the generated contracts' Drop and ends the step dropped, with the named cause (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:41:10 +01:00

seat_tools_test.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

seat_tools.go

C1b, C1c: the seat's verb drop refuses a dropped ask at pull, ends one that runs, and the start sweeps old drops (ADR 0664 §5, issue 1748)

2026-11-09 23:07:49 +01:00

step_test.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

step.go

Keep a check's answer within the steps state: leave out the taken versions

2026-11-12 16:32:48 +01:00

steptool.go

mesh-build-go runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery: the Puller takes buildstep.StepAsk (the read bridge is the form's own AskAs), the toolchains value is the build runner's own, the stale-step part is buildrun's, keys and values come from the seats and clients (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:05:34 +01:00

tap.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

transport.go

C2: mesh-build-go says a failure of the network as a transport fault: one download, no retry of its own (ADR 0664 §1, issue 1748)

2026-11-09 23:10:16 +01:00

trees_integration_test.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

trees_named_test.go

A merge preview reports raw paths and objects, so only the indexer computes a named tree or reads packages (ADR 0593 §2)

2026-11-02 18:28:22 +01:00

trees_test.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

trees.go

The key keeper is ssh-client's published package sshkeys, taken by series by the three build modules; Said, KindBuilder, ExecRunnerClean from the Delivery sdk (B5d; ADR 0634 §1; issue 1966)

2026-11-05 14:55:59 +01:00

watch_settings_linux.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

watch_settings_other.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

workspaces_test.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

workspaces.go

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00