meridiandebuglisted

# /meridian:debug — Systematic Debugging 4-phase systematic debugging with decision logging. Uses the protocol from `references/discipline-protocols.md`. ## Arguments - `<description>` — Bug description or error message - `--plan <id>` — Associate with a specific plan - `--phase <id>` — Associate with a specific phase ## Procedure ### Phase 1: Investigation 1. Read the full error message and stack trace 2. Identify the exact file, line, and function 3. Check recent changes: `git log --oneline -10` and `git diff` 4. Reproduce the error by running the failing test/command 5. Record findings ### Phase 2: Pattern Recognition 1. Categorize the error type: - Import/module error - Type error / null reference - Logic error / wrong behavior - Race condition / timing - Configuration / environment - Data integrity 2. Search codebase for similar patterns 3. Check if this is a known issue pattern ### Phase 3: Hypothesis 1. Form a specific hypothesis: "The error occurs because X" 2. Identify evidence that would confirm/refute 3. Test with minimal change 4. Record hypothesis and result as a decision: ```bash PYTHONPATH=$MERIDIAN_HOME uv run --project $MERIDIAN_HOME -- python -c " from scripts.db import connect, get_db_path from scripts.state import create_decision conn = connect(get_db_path('.')) create_decision(conn, '<hypothesis and result>', category='approach', rationale='<evidence>', phase_id=<phase_id_or_None>) conn.close() " ``` ### Phase 4: Implementati