Development record

When a role routed to a runner fails, the loop records the fallback with only the runner's exit status ('2.1.316 exited with status 1', internal/core/runner/proc.go) and leaves out what the runner reported (the stored transcript keeps it, the fallback's detail does not), so the cause is invisible where a person looks: on 2026-11-01 the routed implementer of run-2611012037155265 failed because claude --bare found no API key, and claude reported 'Not logged in' as the result line of its stream-json output on stdout, with stderr empty, which only a hand run of the same command showed. The fallback then parked the lane, since a fallback is final.