Debug

Build a tight, red-capable feedback loop before changing code. Then minimize, test falsifiable hypotheses, fix the root cause, and drive the same loop green.

1. Establish the symptom safely

Capture the user's exact observable symptom: error, wrong output, UI state, failed request, or measured latency. Record the triggering input, environment, and expected versus actual behavior.

Redact secrets before displaying or saving evidence:

• Replace credentials, tokens, cookies, authorization headers, and personal data with <REDACTED>.
• Record environment-variable names and presence by default, not values.
• Keep credentials in the environment when building reproduction scripts.