From e428f479131e725da20c864a8d3c72b7a91a26f6 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 04:06:46 +0100 Subject: [PATCH] Design 47 H: H-A-106, the queue's over-cap start, the approved pipeline and the findings' form Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 1947273e..534df897 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -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.` 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.` 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.