// Patterns that generate noise — handle in code, not Sentry:
// — User submits an invalid form → return 422, no Sentry
// — User requests a missing job ID → return 404, no Sentry
// — Rate limiter fires → return 429, no Sentry
// — Unauthenticated request to protected route → return 401, no Sentry

// Patterns that genuinely need Sentry:
// — Firestore write fails unexpectedly
// — Email sending fails after a successful job creation
// — Unhandled exception in any server component
// — Client-side React render crash affecting the user’s session
