Telemetry Canary (Observability & Logging Audit)

Audit code for proper telemetry instrumentation — ensure the app is not a black box in production, and that what it logs does not leak.

Auditing Categories

1. Empty / Silent Catch — catch blocks that swallow exceptions without logging a stack trace or forwarding the error.
2. Unstructured Logs — plain-string logging in server code (prefer JSON / structured key-value for cloud queries).
3. No Correlation ID — operations crossing boundaries (HTTP/gRPC/threads) without propagating a trace/correlation ID.
4. Missing Metrics — critical transactions (checkout, auth, errors) lacking counter/histogram instrumentation.
5. No Stack Traces — errors logged without stack context (logger.error(e.message) instead of logger.error(e)).
6. Sensitive data in logs — a log call in code a runtime loads whose argument is a request body, an Authorization/Cookie/Set-Cookie header (or the whole headers object), or a prompt or output value; logs that leave the machine keep it.

Per-stack grep patterns and right/wrong shapes per category: read references/checks.md before scanning.

Fix mode (choice-gated)

In Agent Context, after the report, present via ask_question:

• Apply safe logs: insert error logging into empty catch blocks (standard logger template) + stack-trace mapping. Each fix: checkpoint (copy the touched file(s) aside, or use an isolated worktree — never git stash/git commit, which can hide or include unrelated staged/unstaged user work) → record a build+test BASELINE → apply → build + tests → auto-revert only if a NEW failure appeared versus the baseline.
• Let me pick: user selects which telemetry gaps to resolve.
• Report only: exit unchanged.

Grants & denials (CLASSIFY-BLOCK)

Output

| file:line | category | severity | finding | recommendation |

Severity: CRITICAL (swallowed error with state mutation; a confirmed secret value written to a log) · HIGH (missing stack trace in error logs; sensitive data logged where the Worker config ships logs off the machine) · MEDIUM (unstructured log in API boundary; sensitive data logged where logs are only seen live) · LOW (minor trace gaps)