Answer A-463: the indexer takes in a merge it never took in, and says so

This commit is contained in:
2026-11-17 01:40:16 +01:00
parent e34c74c2f8
commit b6c99f171d
@@ -1454,3 +1454,12 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-462b** (A-462a; principle 3) A want a rule holds keeps that rule's words, which say why it does not move; A-462a's
words ("waits for the entry of that fingerprint") are written only on a want no rule holds. (From the review of
A-462.)
- **A-463** (ADR 0573 §2; principles 3, 1 and 4) A merge the indexer never took in is noticed and taken in by the
indexer itself: at its start and on every source revision the gate's source names, it compares each repository's
`taken` merge with the head that source names, and a repository whose head is newer is taken in as its merged
message would have been (the catch-up of `indexer_take_in`, for that repository), said in its log, with a condition
raised while it stays behind (the repository, its taken merge and the head) and cleared once taken. A merge is never
left untaken in silence, so no package stays published at a commit older than its trunk. (Live, 2026-11-17 02:00:
mesh-contracts #14, merged 2026-11-16 14:14Z, was never taken in; `packages` kept every mesh-contracts package at
20b06dbc, and every build of the node-engine since 15:24Z and of the assigner since 22:51Z failed on symbols only #14
holds.)