mesh-catalog

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

CAT-BG4/BN1: the seat generator moves into buildstep, one program for Go and TypeScript

2026-11-04 15:12:46 +01:00

conformance

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

seatgen

seatgen: no seat list and no root package, definitions in any folder, seat-list-grain files generate nothing, packages with a dependency-free lock (ADR 0635 §1, ADR 0634 §8, F7; issue 1966)

2026-11-05 13:21:04 +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

CAT-BG2: mesh-build-go builds a Go package as its module zip and publishes it under its module path

2026-11-04 14:37:47 +01:00

askrun.go

CAT-BG5: mesh-build-go regenerates a contracts module's Go files and names each out of step

2026-11-04 15:06:54 +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 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_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

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

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

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_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

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

generated_test.go

seatgen: no seat list and no root package, definitions in any folder, seat-list-grain files generate nothing, packages with a dependency-free lock (ADR 0635 §1, ADR 0634 §8, F7; issue 1966)

2026-11-05 13:21:04 +01:00

generated.go

mesh-build-go: the generated-files compare finds a contracts module in any folder; a folder module's Go packages each publish under their own module path (ADR 0634 §8; issue 1966)

2026-11-05 13:23:00 +01:00

go.mod

Mesh-catalog modules import operator-channel from its domain's contracts module and the registry seats from mesh-delivery's (K-4..K-20 first part; ADR 0634 §7, ADR 0636; issue 1966)

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

go.sum

Mesh-catalog modules import operator-channel from its domain's contracts module and the registry seats from mesh-delivery's (K-4..K-20 first part; ADR 0634 §7, ADR 0636; issue 1966)

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

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

guard_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

guard.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_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

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

latepublish.go

Mesh-catalog modules import operator-channel from its domain's contracts module and the registry seats from mesh-delivery's (K-4..K-20 first part; ADR 0634 §7, ADR 0636; issue 1966)

2026-11-05 14:07:30 +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

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_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-catalog modules import operator-channel from its domain's contracts module and the registry seats from mesh-delivery's (K-4..K-20 first part; ADR 0634 §7, ADR 0636; issue 1966)

2026-11-05 14:07:30 +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

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

narrow.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_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 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_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

Mesh-catalog modules import operator-channel from its domain's contracts module and the registry seats from mesh-delivery's (K-4..K-20 first part; ADR 0634 §7, ADR 0636; issue 1966)

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

pull_bus.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_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_fake.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_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

pull_seat_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_seat.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_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.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

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

seat_tools_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

seat_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

step_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

step.go

CAT-BG5: mesh-build-go regenerates a contracts module's Go files and names each out of step

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

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

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

trees_integration_test.go

mesh-build-go: a real-git test that a root module's source leaves out its nested module folders and a folder module is narrowed like a root one (D-I4, ADR 0634 §8; issue 1966)

2026-11-05 13:25:09 +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

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

Ask git ls-tree for nested named paths in rounds: given go and go/seats/x together it lists go's children, so mesh-contracts' preview failed (issue 1966)

2026-11-04 19:38:50 +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