Add catch-must-log-to-sentry lint rule

[danielchen0]

Summary

• Adds catch-must-log-to-sentry rule that flags catch blocks containing logger.error() or console.error() without a corresponding Sentry.captureException() call
• Does not flag catch blocks without error logging (no false positives for handled errors)

Test plan

• All existing tests pass
• 7 new tests pass
• TypeScript compiles
• Prettier passes

[arnavsurve]

Clean, well-structured rule addition. The implementation is correct and consistent with existing rules in the codebase.

What I reviewed:

• Rule logic in catch-must-log-to-sentry.ts: The recursive containsCall helper is a solid approach for AST searching without a nested traverse. The rule correctly only flags catch blocks that have logger.error()/console.error() without Sentry.captureException(), avoiding false positives on handled errors.
• Test coverage: 7 tests covering the core cases (flagging logger.error, console.error, allowing both together, Sentry-only, no logging, empty catch, multiple independent blocks). Good coverage.
• README documentation: Properly adds a new "Error Handling Rules" section, updates the rule count, and includes clear code examples.
• Integration: Rule export, index registration, and config-modes test count bump are all correct.

Minor observations (non-blocking):

• The recursive containsCall traverses into nested function/arrow function bodies within the catch block. If someone defines a callback inside a catch that calls logger.error, it would trigger the rule even though the logging is in a different execution scope. This is an extremely rare pattern and arguably still worth flagging, so not a concern in practice.
• Only Sentry.captureException is recognized (not Sentry.captureMessage etc.), which seems intentional and correct for catch blocks.

All CI checks pass. LGTM.

🤖 Generated with Claude Code