Development record

A build lane can start a spec step whose wait on another spec's step is written only in prose, before that step has landed. A step's needs: line takes only the same spec's step numbers (internal/core/spec/steps.go), so a dependency across specs goes in prose. spc-2610301950037469 step 2 says it waits for spc-2610301917245442's steps 1 and 3; the readiness check cannot read that. On 2026-11-01 lane 2 of run-2610312053537139 started step 2 while the parent's step 1 was still on an unmerged pull request (#1315) and its step 3 had not been built. The implementer built the hook half, could not build the verb half, and the review returned FIX FIRST. Landing would have marked the whole step landed, and step 3, which reads the verb's limits field, would have started next. A full implement and preflight cycle was spent on a step that could not be finished.