mesh-catalog

announce_integration_test.go

mesh-build-node: announce the states it keeps from its code, so readers are granted from its word (issue 1790, ADR 0495 §2 §5)

2026-10-22 18:08:06 +02:00

announce.go

Announce the pauses state in the three build modules, and pin mesh-sdk 518dae5 (an unreadable pause pulls as not paused)

2026-10-25 18:57:08 +01:00

asks_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

asks.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

build_integration_test.go

A missing bubblewrap fails the sandbox proofs on a build node instead of skipping them

2026-10-27 21:36:28 +01:00

build_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

build.go

Merge main (#617 , #618 ) into the registry milestone (issue 1966)

2026-11-06 00:18:20 +01:00

check_test.go

Seat fixtures of the claude-code and node-build tests carry their domain (ADR 0636 §5; issue 1966)

2026-11-05 14:39:49 +01:00

check-needs

mesh-build-go: report the needs a package's check-needs marker names, test it only where the node has them, decline an ask needing what the node lacks (issue 890)

2026-10-26 13:37:52 +01:00

check.go

Merge main (#617 , #618 ) into the registry milestone (issue 1966)

2026-11-06 00:18:20 +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

emit_build_test.go

mesh-build-node: emit a package that builds before its tests, so tests importing its own output find it (issue 1869, part of issue 1309's run step)

2026-10-22 18:23:25 +02:00

emit_test.go

Review round 1 for the Node build module: build depth (1490), bin scripts for the test script (1491), toolchain.reported and its stream (1483, 1488); delta part 3 of 4

2026-10-20 21:10:18 +00:00

fetch_test.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

fetch.go

Merge main (#617 , #618 ) into the registry milestone (issue 1966)

2026-11-06 00:18:20 +01:00

forge_test.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

generated_package_test.go

The seat-list case waits for the reader's change instead of racing it; the node build's generated-package fixture carries its domain (issue 1966)

2026-11-05 14:40:30 +01:00

harness_test.go

mesh-build-node: push each done bundle to the artifact store from its own process and answer its reference (issue 1587, S5-S8, ADR 0498 §1 §2, lead decision L9)

2026-10-22 18:25:14 +02:00

installed_toolchain_test.go

Replace the downloaded release's tests with tests of the installed toolchain (issue 1572, ADR 0477)

2026-10-21 08:02:02 +00: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

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

isolation_integration_test.go

A missing bubblewrap fails the sandbox proofs on a build node instead of skipping them

2026-10-27 21:36:28 +01:00

keys.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

kit_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

main.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

manifest_test.go

mesh-build-go, -image and -node declare the builder's published package builds, which they now read their forms and keys through (B5i; ADR 0634 §1, §4; issue 1966)

2026-11-05 16:09:52 +01:00

module_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

module.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

needtools_test.go

A missing bubblewrap fails the sandbox proofs on a build node instead of skipping them

2026-10-27 21:36:28 +01:00

package_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

package_paths_test.go

mesh-build-node builds and tests each TypeScript package at its own path, with its own lock (ADR 0634 section 8, issue 1966)

2026-11-05 21:14:56 +01:00

package_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

package.go

Merge main (#617 , #618 ) into the registry milestone (issue 1966)

2026-11-06 00:18:20 +01:00

preview_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

preview_test.go

Make the build modules' fetch merge the head onto a trunk commit and place siblings beside the tree, so the checker judges the merge and tests read their siblings (issues 1675, 1676, 1677)

2026-10-21 21:04:59 +02:00

preview.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

probe.go

Build TypeScript with the installed node and name no Node version (issue 1572, ADR 0477)

2026-10-21 08:04:41 +00:00

publish_integration_test.go

CAT-BN3: mesh-build-node publishes through the registry seats and holds no registry credential

2026-11-04 15:30:06 +01:00

publish_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

publish.go

Commit the build modules' publish code a bare ignore pattern hid; drop committed go.work.sum

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

push_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

read_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

read.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

reads-outside

mesh-build-node tests decode their manifest instead of judging it (ADR 0578 §3)

2026-11-01 02:40:56 +01:00

recipe.go

mesh-build-node: name each bundle's launchers by mesh-sdk's one rule, and move the recipe for the SDK a member's lock names (R4e, lead decision L10)

2026-10-22 18:39:06 +02:00

registry.go

CAT-BN3: mesh-build-node publishes through the registry seats and holds no registry credential

2026-11-04 15:30:06 +01:00

room_test.go

mesh-build-node runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery; its state names are its seat's; the three build modules require the contracts they import (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:07:50 +01:00

room.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

store_integration_test.go

Builders, the artifact store's tools and distribution read and write the registry reference form through the registry clients' reference package, and name the sweep seat from its contract (ADR 0634 §4, S-8; issue 1966)

2026-11-05 17:26:32 +01:00

toolchain_open_test.go

mesh-build-node: write the install's registry credential in the account's home, never beneath the opened cache, and refuse to open a toolchain holding one (issue 1891 review, ADR 0533 §2)

2026-10-23 11:45:20 +02:00

toolchain_test.go

CAT-BN3: mesh-build-node publishes through the registry seats and holds no registry credential

2026-11-04 15:30:06 +01:00

toolchain.go

CAT-BN3: mesh-build-node publishes through the registry seats and holds no registry credential

2026-11-04 15:30:06 +01:00

tools.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

workspace.go

Build modules: a failed command's reason says its error, not its last progress line (issue 1703)

2026-10-26 15:21:01 +01:00