The indexer and the checker know a Go module the trunk holds a record of (issue 1966, bootstrap recovery)

Conversation 1 Commits 2 Files Changed 5

+38 -7

2 Commits

Author SHA1 Message Date

Author	SHA1	Message	Date
jschoubben	2e9f23f348	Round 1: known by the module path alone, never a package inside it mesh/delivery merged: source.main moved to novox/mesh-delivery@68581bed7e36 Details mesh/check failed: mesh-build-go: the change's manifests cannot be judged: the seat list is not read (the seat list is … \| 2e9f23f34828 on 68581bed7e36 The review of `0f5c186b`: counting each record's packages made 94 sub-package paths, commands among them, known names, which design 32 forbids; the seven names refused live are each their record's module (issue 1966). Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5	2026-11-08 01:24:54 +01:00
jschoubben	0f5c186b9c	The judge knows the Go packages the trunk holds a record of (issue 1966, recovery) The indexer's judge refused manifests whose `packages` name a Go package that no manifest declares as a package artifact: such a package has no series key, and knownPackages took series keys only, though each module the trunk published has a per-module record in the packages state naming its Go module and packages. knownPackages (and the checker's PackageNames) now also count each record's module and packages[].package; an unreadable state still judges no name. Quick vs thorough: this is the quick fix, the smallest change that lets the trunk's own records name what the manifests name. The thorough fix is that a build module builds Go package artifacts, so every Go package gets a series (the registry milestone); then the records stop being a source of names. Done now because the 15 refused manifests hold the bootstrap of the registry delivery.	2026-11-08 01:14:52 +01:00

jschoubben

2e9f23f348

Round 1: known by the module path alone, never a package inside it

mesh/delivery merged: source.main moved to novox/mesh-delivery@68581bed7e36

Details

mesh/check failed: mesh-build-go: the change's manifests cannot be judged: the seat list is not read (the seat list is … | 2e9f23f34828 on 68581bed7e36

The review of 0f5c186b: counting each record's packages made 94 sub-package
paths, commands among them, known names, which design 32 forbids; the seven
names refused live are each their record's module (issue 1966).

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

2026-11-08 01:24:54 +01:00

jschoubben

0f5c186b9c

The judge knows the Go packages the trunk holds a record of (issue 1966, recovery)

The indexer's judge refused manifests whose `packages` name a Go package that no
manifest declares as a package artifact: such a package has no series key, and
knownPackages took series keys only, though each module the trunk published has
a per-module record in the packages state naming its Go module and packages.
knownPackages (and the checker's PackageNames) now also count each record's
module and packages[].package; an unreadable state still judges no name.

Quick vs thorough: this is the quick fix, the smallest change that lets the
trunk's own records name what the manifests name. The thorough fix is that a
build module builds Go package artifacts, so every Go package gets a series
(the registry milestone); then the records stop being a source of names. Done
now because the 15 refused manifests hold the bootstrap of the registry delivery.

2026-11-08 01:14:52 +01:00

The indexer and the checker know a Go module the trunk holds a record of (issue 1966, bootstrap recovery) #173