debt-runnerlisted

# Debt Runner Interactive orchestrator for the Technical Debt Management System. Sequences existing TDMS scripts, applies convergence-loop verification at every stage, and owns the remediation plan artifact. ## Critical Rules (MUST follow) 1. **Never write MASTER_DEBT.jsonl directly** — all mutations go to staging files in `docs/technical-debt/staging/`. CL verifies staging, then existing scripts (intake-audit.js, resolve-bulk.js, etc.) apply to canonical files. 2. **Convergence-loop on every mode** — no mode completes without CL verification. Presets vary by mode (see each mode section). 3. **Post-mutation sync check** — after any pipeline that modifies MASTER_DEBT, run CL quick preset verifying MASTER_DEBT.jsonl and `raw/deduped.jsonl` item counts match + spot-check recent mutations in both files. 4. **Confirmation gate at >100 mutations** — present count + 10-item preview. User approves before applying. 5. **Return to menu after each mode** — present updated stats + mode menu. User picks next mode or exits. ## When to Use - Verifying accuracy of current technical debt items - Syncing new debt from SonarCloud or other sources - Planning and prioritizing debt resolution - Running deduplication, validation, or cleanup pipelines - User invokes `/debt-runner` or any mode variant ## When NOT to Use - Adding a single debt item manually — use `/add-debt` - Full SonarCloud interactive experience — use `/sonarcloud --interactive` - Auditing the TDMS ecosy