Generic Debugging Rules for Perplexity Labs

# Generic Debugging Rules for Perplexity Labs

## Triage flow
- Reproduce reliably before changing code.
- Narrow blast radius with logs/metrics/traces.
- Form one hypothesis at a time; verify/falsify quickly.

## Incident handling
- Prioritize user impact reduction first, root cause second.
- Add temporary guardrails if full fix needs longer.
- Capture timeline, contributing factors, and concrete follow-up actions.

## Prevention
- Add regression tests for every production bug.
- Improve visibility where detection was delayed.
- Remove ambiguity from error messages and status signals.