Bugfix workflow

When a bug, failing test, error, regression is reported — follow this exact sequence.

1. Reproduce

• Establish the smallest reliable repro path (test, command, sequence of clicks, payload).
• If you cannot reproduce — STOP and ask owner for repro steps. Do not "fix" what you cannot reproduce.

2. Read code BEFORE hypothesis (R1)

• Read the file(s) implicated in the failure. Do not skim — actually Read with the tool.
• If the issue touches an external SDK/API → trigger official-docs-first skill (R2).
• Cite specific file:line in your reasoning.

3. Identify root cause

• Walk the failing path from symptom backwards.
• Check git log of the failing file: git log -p --follow <file> — recent changes?
• Use Grep/Serena find_references for related call sites.
• Hypothesis is OK only AFTER reading. Mark explicitly: "Hypothesis (unverified): X. Verifying via Y."