The step-ended outcomes gain no dropped: the drop verb's description now
says both a waiting and a running ask end their step could not run, the
why naming the drop and who asked it, one way for an ask that never ran.
Builds: design 47 H2 H-A-401
A holder whose node lacks what a step's packages need (the artifact's
check-needs, now named on the integration step's ask) says the step's end
declined with needs and lacks, in place of could not run. The runner puts
it again under a new ask id naming in not-on the nodes that declined it;
a holder on a listed node hands it back at once. The nodes that can take it
are the holders of the step's seat and of the need's seat less those that
declined; when none is left the step ends could not run naming the need
and the nodes asked. The build-step part's form is 3, the runner seat's 5.
Builds: design 47 H2 H-A-375, H-A-445 (ADR 0552 §2, §4)
The build modules' shared steprun parts of §799: again-delays (15s,60s) read
into a Puller's Delay; a fetch's 401/5xx or connection fault and a publish's
no responders or exited bundle are transport faults whose why opens fetch: or
publish:; the assigner call that named a silent holder goes. The builder reads
an exited bundle as no responders and keeps the part in a key's fault words.
Builds: design 47 H2 §799 (H-A-390)
The bus counts an ask given back before it ran as a delivery, so four asks were ended 'poison' having never run. Puller.Prior
(PriorRuns) counts the runs the step key says started. A poisoned pipeline step now says its step-ended, so the runner stops
waiting. refuseUnread, refuseAsker and the poison path acknowledge the ask once its end is written, not terminate it.
Builds: design 47 G §24, §25; lead answer A-489 (G-22-lead-answers-2.md)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy