Design 47 H: H-A-204, an entry names every requirement, pinned or waiting; a publish re-pins every entry

This commit is contained in:
2026-11-20 22:54:39 +01:00
parent d3849e37ce
commit f977c0e232
@@ -1093,3 +1093,12 @@ Where two preparers disagreed, the chosen one is named.
refuses a requirement of another repository with no pin (H-A-192), refused twelve test steps of the contracts mover.
The runner puts the entry's `packages` pins into every step ask's fetch (the contract's field exists), the same pins
the builder gives the build, so a test runs against what the build was built against (P1: one truth; H-A-183). P1, P7.
- **H-A-204 (an entry names every requirement, pinned or waiting; a publish re-pins every entry, 22:54)** Met live: six
build asks were refused for a requirement with no pin although the registry held its version (0.1.27, 0.1.4, 0.1.47)
or none yet (busgrants); the entries of modules not changed since kept their old `packages`, and no publish re-pinned
them. An entry's `packages` names every other-repository requirement of its module graph (H-A-201), with an empty
version where none is published yet (never left out, so the builder waits by H-A-165/194 instead of the build module
refusing); a package's publish re-pins every kept entry, of any repository and whether or not its module changed,
that names the path with no version or an older one in its accepted series (H-A-165, H-A-167, fingerprint moves);
and the indexer answers one entry's `packages` and paths at a revision through a tool, so a pin can be read without
the whole revision. P1, P4, P7; tools-are-how-a-module-is-spoken-to.