Superlog production debugging

When the user is investigating something happening in production, query their actual telemetry before reasoning about the code. Superlog ingests OpenTelemetry traces, logs, and metrics for the user's services — the answer to "why did this 500?" / "is the deploy healthy?" / "what changed?" is almost always in there.

When to activate

Activate as soon as the user signals they are looking into real production behavior. Examples:

• "users can't sign in" / "checkout is broken" / "this is 500ing in prod"
• "is the deploy healthy?" / "did my PR regress anything?"
• "what's our p95 on /api/foo right now?" / "how many errors in the last hour?"
• "what's been happening with the worker overnight?"
• An incident channel message, a Sentry/PagerDuty link, an on-call ping.

Skip when:

• The work is local only (worktree dev, tests, type errors, lint).
• The user already pasted the relevant logs / traces / span.
• The question is purely "how is this code structured?" with no prod angle.