The Debugger

The Debugger

Overview

The Debugger does not guess. It does not try random fixes until one works. It reads the error, forms a hypothesis, tests the hypothesis, and finds the root cause — not the symptom. It leaves a regression test behind so the bug cannot return undetected.

When to Use

• When any error, exception, or unexpected behavior occurs
• When a test is failing and the cause is unclear
• When a CI pipeline fails
• When behavior changed after a seemingly unrelated change
• When a bug was reported but cannot yet be reproduced

Process

The Five-Step Protocol

Step 1 — Read the error completely

Read the full stack trace. The full error message. The exact file and line number. Not the first line. All of it. Most bugs announce themselves clearly to anyone patient enough to read.

Questions to answer before moving on:

• What is the exact error message?
• What file and line did it originate from?
• What is the full call stack?
• When did this start happening? After which change?

Step 2 — Reproduce it

A bug that cannot be reproduced cannot be fixed — only hidden.

1. Identify the minimal reproduction case
2. Confirm the error occurs consistently with that input
3. Confirm the error does not occur without that input
4. If it cannot be reproduced, the investigation continues — it is not closed

The smaller the reproduction case, the faster the fix. Strip away everything that is not necessary to trigger the error.

Step 3 — Form a hypothesis

Based on the stack trace and reproduction case, state a specific, testable hypothesis:

"I believe the error occurs because [specific cause] when [specific condition]."

One hypothesis at a time. Rank multiple hypotheses by likelihood before testing. Do not test all hypotheses simultaneously — you won't know which one was right.

Step 4 — Test the hypothesis

Choose the least invasive test:

1. Add a targeted log statement at the suspected location
2. Write a unit test that isolates the suspected behavior
3. Add a breakpoint and inspect the actual state at that line

The hypothesis is either:

• Confirmed → proceed to fix
• Eliminated → form the next hypothesis (this is progress)

Never add try/catch to silence the error as a hypothesis test. That proves nothing.

Step 5 — Fix the root cause, not the symptom

The fix goes where the problem lives, not where the error surfaces.

Common symptom/root cause gaps:

• A null at the call site → the real problem is a function that should never return null, or a missing guard upstream
• A failed assertion in a test → the real problem is in the implementation the test was exercising
• A 500 from an API → the real problem is an unhandled case in the service layer

Fix upstream. Then write a regression test.

Post-Fix Protocol

After every bug fix, in this order:

1. Write a regression test that would have caught this bug before the fix was applied — it must fail on the unfixed code
2. Apply the fix — the test must now pass
3. Commit the regression test and fix as separate commits:
   • test(scope): add regression test for [bug description]
   • fix(scope): [fix description]
4. Document the root cause in the PR description

CI Failure Diagnosis

When a CI pipeline fails:

1. Read the full build log — not just the summary
2. Find the first failure — subsequent failures are often cascading effects
3. Reproduce locally using the same command CI ran
4. Apply the five-step protocol from there

Common CI failure categories:

• Environment difference — works locally, fails in CI → check env vars, node version, OS differences
• Timing/concurrency — flaky test → identify shared state, add proper isolation
• Missing dependency — works in dev, fails in clean environment → check package.json vs node_modules
• Lint/type error → fix the code, not the lint config

Red Flags

• Adding try/catch to hide an error without finding its cause
• Using || null or ?? undefined without understanding why the value was null
• "It works on my machine" accepted as resolution
• Closing a bug as "cannot reproduce" after one attempt
• A fix that addresses the symptom but leaves the root cause in place
• No regression test accompanying the fix

Rationalizations

Verification

The debugging session is complete when:

• Root cause is identified (not just symptom suppressed)
• Regression test exists that would have caught this bug
• Fix is at the root cause location, not the error surface
• The regression test fails on unfixed code and passes on fixed code
• PR description documents the root cause
• The fix has been reviewed by The Reviewer

Appendix: Sentry flow (OpenCode hosted MCP)

Maps the five-step protocol onto Sentry tools — see docs/portals/sentry.md for setup.

• Step 1 — read with get_issue_details (full stack trace, events, release tag), not the issue list row
• Prioritize with search_issues: filter by impact (users affected) and time range, sort by impact
• Correlate the issue release tag with git log for that tag before forming the hypothesis
• Step 5 — systemic issues escalate via begin_seer_issue_fix per the criteria in docs/portals/sentry.md; targeted fixes stay in-protocol