Merge pull request 'Design 47 H: lead answer H-A-106 (the queue's over-cap start, the approved pipeline, the findings' form)' (#775) from design/47-H1-answers-37 into main

This commit was merged in pull request #775.
This commit is contained in:
2026-11-20 03:07:36 +00:00
@@ -452,3 +452,10 @@ Where two preparers disagreed, the chosen one is named.
test 36 and G-5's restore step are corrected to name `gate_head_take` when the design is next amended). P7. (b) The
run candidate's check of a module named twice with different manifests stays: it guards a run on request, which
stays (H-A-58); only the pull-request candidates go. P7.
- **H-A-106 (runner developer, 04:06; the queue)** (a) A start over the cap is written as an ordinary waiting pipeline
(its value `waiting`, its `waiting.<seq>` key) beyond the cap; `queue-full` is raised naming it and cleared when an end
brings the waiting count back to the cap or below; nothing is left unacknowledged (H-A-36 over §748's wording). P1,
P3. (b) A pipeline whose approval is answered and still runs has its `running.<pipeline>` key written at once, over the
bound, since it asks nothing new but its end; "waiting on its approval step" means every step not ended is an approval
asked of the operator. P3. (c) `pipelines-stalled` and `queue-full` have the kind as their id, severity warning, no
owner (the operator's), like `pipeline-failed`'s writer. P8.