Design 47 H: H-A-198, a package artifact's tree holds its same-repository requirements

This commit is contained in:
2026-11-20 22:08:24 +01:00
parent 9925385b24
commit 382bfb7739
@@ -1055,3 +1055,10 @@ Where two preparers disagreed, the chosen one is named.
fault. Every module's pull loop, the tool runner's included, claims its durable through the SDK's one guard before it
pulls (P7: shared behaviour lives in the SDK), and a re-serve stops its old loop before it binds the new one so the
guard refuses only a true second loop. P1, P7.
- **H-A-198 (a package artifact's tree holds its same-repository requirements, 22:08)** Met live: the steps of a package
artifact (grantsstate) could not run because its go.mod requires a client of the same repository at the zero version
and the step's fetch, narrowed to the artifact's own path, held no module of that path, while nothing of a repository
is published before its merge. A package artifact's `paths` in the catalog entry name its own directory and every
same-repository module directory its go.mod requires, transitively, as the indexer derives them from the go.mod edges
(H-A-157); a same-repository requirement is built from the tree, never pinned; a requirement of another repository
is pinned by H-A-183. P7, P4 (the indexer owns the entry; the build modules only narrow by what it names).