rnd-debug-pipelinelisted

# R&D Debug Pipeline ## Overview The debug pipeline is a focused workflow for fixing isolated bugs without a full `/start` decomposition. A dedicated debugger diagnoses the bug and hands off a structured report to the Builder — the Builder fixes without re-investigating. **Core principle:** Diagnosis and fix are separate roles. The Builder receives a complete diagnosis report; they do not re-investigate the root cause. ## When to Use - A specific bug has been reported and is reproducible - The bug is isolated (1-2 files, not a design flaw) - A full `/start` pipeline is unnecessary overhead ## Pipeline Phases ### Phase 1: Reproduce Confirm the bug is real and understand the exact conditions that trigger it. Document the minimal reproduction steps. If the bug cannot be reproduced after reasonable effort, return status `CANNOT_REPRODUCE`. ### Phase 2: Diagnose Apply `rnd-framework:rnd-debugging` methodology to find root cause. Produce the diagnosis report (format below) saved to `$RND_DIR/diagnosis/T<id>-diagnosis.md`. Return status `DIAGNOSED` or `ESCALATE`. ### Phase 3: Fix (Builder handoff) The Builder receives the diagnosis report and the pre-registration from the debugger. The Builder does NOT re-investigate — they implement the fix described in the report using `rnd-framework:rnd-building` discipline. ### Phase 4: Verify An independent Verifier checks the fix against the success criteria in the pre-registration. Same process as the standard pipeline — the Ver