mesh-catalog

mesh-config: read the pull request's commit from head_sha (issue 1826)

2026-10-22 11:09:48 +02:00

catalogfeed_test.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

catalogfeed.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

config_test.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

config.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

declared.go

Every module follows the assigner's new places: the contracts' go/ path, mesh-wants in the delivery contracts, the state and tool assignments (issue 1966)

2026-11-05 22:29:07 +01:00

delivery.go

mesh-config reads the placement, wants, haves, modules, manifests, predefined list and config candidates through the seats' types and clients, the builder's builds through its published package; the kept value is its own layout (B5f; ADR 0634 §1, §4; issue 1966)

2026-11-05 15:52:59 +01:00

findings.go

G findings: artifact-store-tools and mesh-config read what their held writer holds, so a restart neither drops nor rewrites their findings

2026-11-11 22:17:21 +01:00

list.go

mesh-config: read declarations from each placed module's own manifests as built, and placement alone, so a module from its own repository resolves (issue 1953)

2026-10-29 15:19:24 +01:00

main.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

manifest_test.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

ownerviews_test.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

ownerviews.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

proposals_test.go

K-A2: mesh-config asks every proposal; the router holds the oldest back

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

proposals.go

K-A2: mesh-config asks every proposal; the router holds the oldest back

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

pullforge_test.go

mesh-config: read the pull request's commit from head_sha (issue 1826)

2026-10-22 11:09:48 +02:00

pulls_test.go

mesh-config keeps held values in the seat's typed state kept, through the config client's key and codec (B5g, B2f; ADR 0565 §5, ADR 0634 §4; issue 1966)

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

pulls.go

mesh-config keeps held values in the seat's typed state kept, through the config client's key and codec (B5g, B2f; ADR 0565 §5, ADR 0634 §4; issue 1966)

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

readers.go

Every module follows the assigner's new places: the contracts' go/ path, mesh-wants in the delivery contracts, the state and tool assignments (issue 1966)

2026-11-05 22:29:07 +01:00

reads-outside

Design 47's last milestones: the keeper, self-check, healers, hand-acts, provisioner, vault, artifact sweep, disk readings, credential forms (issues 774, 1952, 1953, 1954, 1955)

2026-10-30 02:21:51 +01:00

renames_test.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

renames.go

G findings: the modules with findings of their own write them through mesh-sdk's writer

2026-11-11 21:58:08 +01:00

resolve.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

retiring.go

G findings: the modules with findings of their own write them through mesh-sdk's writer

2026-11-11 21:58:08 +01:00

sources.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

switch_tools.go

CAT-C1..C8, C10: mesh-config moves a renamed config value, answers both names in the rename window, retires an unread value on the operator's Approve; the keeper reads its findings

2026-11-04 11:46:16 +01:00

takeover_test.go

mesh-config reads the placement, wants, haves, modules, manifests, predefined list and config candidates through the seats' types and clients, the builder's builds through its published package; the kept value is its own layout (B5f; ADR 0634 §1, §4; issue 1966)

2026-11-05 15:52:59 +01:00

takeover.go

W16.2: mesh-config reads which modules exist, their manifests and a build's manifest from the catalog half through meshcatalogclient's branch follower (milestone 47/G)

2026-11-11 23:34:28 +01:00

whole_integration_test.go

W16.2: mesh-config's whole test says the catalog-revision event on the branch's part, as the bus says it

2026-11-11 23:34:51 +01:00