Design 47 H: H-A-174, a tier-late pipeline-wanted frees nothing

This commit is contained in:
2026-11-20 18:00:48 +01:00
parent 21297155a4
commit 84e2514df5
@@ -908,3 +908,8 @@ Where two preparers disagreed, the chosen one is named.
H-A-170 sharpened: the indexer writes `release.<branch>.<module>` only for a mover that released a version in that
pipeline, and on `pipeline-wanted` of a newer pipeline it frees the record of a module below that pipeline's
revision only where the newer revision itself holds `release.<branch>.<module>`. P2, P7.
- **H-A-174 (a tier-late pipeline-wanted frees nothing, 18:00)** Met in the review of H-A-173: a tier-late
pipeline's later-tier movers released a version, so the newer revision holds their release record, yet their wants
were not written; freeing their older release on the tier-late event would remove the revision their want names.
A `pipeline-wanted` with outcome tier-late frees nothing; the same pipeline's later `pipeline-wanted` with outcome
running frees as H-A-173 says. P2, P7.