The delivery repository's contracts and SDK live under modules/ as mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths renamed to match the folders (the TypeScript names already did), and every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools and mesh-sdk follows in the same group: a design as it should be, one path per module, checked by the group's check building every importer. Builds: design 47 G §427, §88 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
19 lines
903 B
Go
19 lines
903 B
Go
package main
|
|
|
|
// claude-code's reading of which modules exist and of each placed module's manifest (design 47 G §196, §594, §614): the
|
|
// catalog half, taken through meshcatalogclient's follower of the watched branches on the part's one views reader. A
|
|
// module's manifest is the one its catalog graph entry carries whole (§443), never the indexer's state `modules` or
|
|
// `manifests`.
|
|
|
|
import (
|
|
catalog "git.novox.be/novox/mesh-delivery/modules/mesh-delivery-contracts/go/seats/meshcatalog"
|
|
)
|
|
|
|
// CatalogHalf is what this module reads of the catalog half.
|
|
type CatalogHalf interface {
|
|
// Entry is a module's entry at the trunk; an error while a watched branch has no first view yet, never "no module".
|
|
Entry(module string) (catalog.CatalogEntry, bool, error)
|
|
// Ready is nil once every watched branch has its first view (none-yet counting as one), else says what it waits for.
|
|
Ready() error
|
|
}
|