systematic-debugginglisted

# Systematic Debugging Skill ## 1. Root Cause Hypothesis Framework Do NOT guess code fixes. Mandatory sequence for ALL bug, crash, or regression fixes: 1. **Gather Concrete Evidence**: - *Code / Test*: Failing deterministic unit/integration test, assertion failure, compiler error, lint violation. - *Runtime / Android*: Logcat excerpt, crash stacktrace, ANR trace, lifecycle reproduction, permission denial, DB migration error. - *Logic / State*: Invalid StateFlow/LiveData transition, race condition, wrong Coroutine dispatcher/scope. - *Comparative Analysis*: Compare working vs. broken execution paths or historical commits to isolate the exact point of divergence. 2. **Formulate Explicit Hypothesis**: Identify the most likely root cause at the producer level. 3. **Plan Targeted Mutation**: Make the minimal fix directly addressing the root cause. 4. **Verify**: Prove the original failure is resolved and no regressions are introduced. At a suspected component boundary, compare the input, output, state, and configuration of the working and broken paths. Test one falsifiable hypothesis at a time. If fixes repeatedly fail, revisit the first divergence and the hypothesis before adding another patch; preserve the observations that disproved earlier hypotheses. Keep this within the approved scope and existing review budget. ## 2. Prohibition of Symptom Swallowing - Never resolve bugs by swallowing exceptions, adding empty `try-catch`, or returning fallback `0`/`null`/dumm