debugging

Form at least three hypotheses across orthogonal axes such as user-code logic, SDK behavior, and async timing, then gather runtime evidence for each. Confirm the root cause only when toggling the suspected cause toggles the bug, then lock it with a failing-first test.

Run the three-run signature protocol: an unchanged rerun, the failing test in isolation, and the smallest affected scope in a unique temp root. Classify the cause as a product race, fixture leakage, environment contention, or resource pressure before attempting any fix.

Yes. Bundled-JS binaries embed recoverable source: identify the bundler via string fingerprints, extract the bundle with the appropriate tool such as asar or pyinstxtractor, then analyze the plaintext source with grep instead of using Ghidra on the runtime.

The tsx plus node inspect CLI combination has a silent source-map failure where breakpoints by line number do not bind. The Node.js runtime reference documents the correct attach flags and source-map handling needed before starting a session.

Use Ghidra's decompiler when analyzing binaries without trustworthy source, such as closed libraries or firmware. Use pwndbg for live debugging sessions since it provides registers, stack, disassembly, and heap views as a strict superset of plain gdb.

The workflow requires the ability to gather runtime evidence, so bugs needing paid APIs, blocked networks, or missing hardware fall back to partial-evidence patterns. It also forbids git commits during the session and defers those to a separate step after user confirmation.