diagnose-why-work-stopped

From README

Diagnose Why Work Stopped Use Fix Failed Paperclip Run. It owns the current workflow: find the first causal failure, reproduce it red, repair the shared contract, test second-order effects, verify the real workflow, and deliver a PR with passing checks. A normal request to fix stopped work continues through that workflow without a separate plan-approval gate. If the user or calling workflow explicitly asks for diagnosis only or requires approval before implementation, perform the investigation and safety analysis within that scope. For example, a Terminal-Bench diagnosis child does not override the loop's board approval boundary. Keep the next action and its owner explicit. For issue-tree diagnosis, read the current doc/execution-semantics.md, inspect the relevant subtree and recent repairs, and classify non-progressing nodes: Genuine wait: a named human or external dependency must act. Agent-actionable but unrouted: authorized useful work lacks a live path.