jochen
2d1d4bf988
A held delivery asked a person a question with no right answer: four hq merges that build nothing, merges adding a module the controller sends nowhere, controller merges whose change a later walk of the same trunk already delivered, and a group member held because its composed check had not yet answered. Only stop could end them, which marks a delivered change as an error on its pull request. - A merge whose plan moves no module (nothing, or only a new module sent nowhere) is delivered at once. - A new final state, covered: every module a merge moves was sent by a finished walk of a later merge into the same trunk, which contains it. Shown as success on the pull request; a group counts it as delivered. - A group member waits published while its composed check is asked and unanswered, and a member held for it is lifted back to published once it passes for the heads that merged. Read again each tick, so the deliveries already held end by themselves after the rollout.