Design 47 H: H-A-201, the entry pins every requirement of the module graph

This commit is contained in:
2026-11-20 22:13:13 +01:00
parent 0e9f8751bf
commit 8105e2602b
@@ -1073,3 +1073,9 @@ Where two preparers disagreed, the chosen one is named.
root, so the generator's check failed every unit step. A hand-written helper of a seat lives in the seat's
hand-written client package, never under a generated root (ADR 0608 §5); the two move to the catalog seat's client
and their callers follow in the same commit. P7.
- **H-A-201 (the entry pins every requirement of the module graph, 22:13)** Met live: every build on the build node asked
a package at a sibling's version ("unknown revision"), because the Go build module borrowed a version for a
requirement the entry did not pin (a transitive one, or one a sibling names), and a build module given no pin now
refuses (H-A-192). The indexer pins, in the entry's `packages`, every mesh package the module's build requires at
the zero version, transitively across the module graph it reads from the go.mod files (H-A-157), not only the direct
requirements; a same-repository requirement is built from the tree (H-A-198). P4 (the indexer owns the entry), P7.