Sentry triage

Walks an agent through every unresolved Sentry issue in the current project, one at a time. Each issue is investigated to root cause, the same pattern is hunted across the whole codebase, the fix is proposed and approved, and committed. Resolving the Sentry issue is a separate, explicit decision — never assume a fix should auto-close the issue; always ask first.

This is a workflow skill, not a coding-convention skill — it expects to be invoked (via natural phrasing or /sentry-triage), not auto-applied to every file edit.

1. Preflight — refuse to start if requirements are missing

Before doing anything else: