SentrySDK logs fatal errors when crash reporting is disabled

[pacificleo]

Please do not open a pull request yet. A maintainer reviews the report and adds the ready label once it is confirmed.

What happened?

When running the app with crash reporting disabled in settings (or when testing a release build locally), the console is flooded with fatal Sentry SDK errors whenever a Redux action is dispatched:
[Sentry] [fatal] ... The SDK is disabled, so addBreadcrumb doesn't work. Please ensure to start the SDK before adding breadcrumbs.

This happens because LogActionsReducer and GitClient directly call SentrySDK.addBreadcrumb and SentrySDK.captureMessage without first checking if Sentry is enabled.

Steps to reproduce

1. Run a Release build of Supacode.
2. Turn off Crash Reporting in the settings (or don't provide a Sentry DSN).
3. Perform any action in the app that triggers a Redux action or a failing git command.
4. See the console flooded with Sentry fatal errors.

Supacode version and build

0.10.9

macOS version

macOS 26.4

System locale

en_US

Are you planning to fix this yourself?

• I intend to open a pull request once this is confirmed and marked ready.

Before submitting

• I searched existing issues and this is not a duplicate.
• I am on the latest available version of Supacode.
• I understand pull requests are closed until the issue is marked ready.
• I agree to follow this project's Code of Conduct.

[github-actions]

Thank you for filing this. A maintainer will review it and follow up here.

Please do not start any work or open a pull request until this issue is labeled ready. That label is a maintainer's go-ahead: a pull request opened against an issue that is not yet ready is labeled invalid until then. You will get a comment here the moment it is marked ready.

See CONTRIBUTING.md for the full flow.