Design 47 H: H-A-212, the re-pin revision carries entries; the runner keeps starting a publish's pipelines

This commit is contained in:
2026-11-20 23:17:07 +01:00
parent 4463e40ac1
commit d07dc5aad6
@@ -1151,3 +1151,13 @@ Where two preparers disagreed, the chosen one is named.
revision" by the revision number, never by the source (a no-op where they were equal); the take-in again of
H-A-210 is kept the same way (its call "take-in again of <repository>"). H-A-210's "no revision" is amended so.
P1 (one truth: every fingerprint has its entry in a kept revision), P4.
- **H-A-212 (the re-pin revision carries entries; the runner keeps starting a publish's pipelines; H-A-211 amended,
23:17)** Met in the build of H-A-211: the runner already starts a publish's pipelines itself on package-published
(start.go Published, movers read from its catalog half, keyed by branch, source, artifact and version), and keys a
take-in's pipeline by source. So the indexer says no take-in.taken for a re-pin: it keeps the re-pinned entries as
revision N+1 of the same source S on every watched branch, with the revision's call naming the publish
("publish of <path> <version>"), and says catalog-revision; the runner's Published reads its movers from the half at
a revision whose call names that publish (it waits for it as it waits for a take-in's revision), so the pipeline
carries the re-pinned fingerprints; pipeline keys stay as they are. The take-in again (H-A-210) keeps its revision
the same way with the call "take-in again of <repository>" and the runner treats it as a publish's revision for
every mover whose fingerprint moved. P1, P4, P7.