fix(sentry): suppress user cancelled transaction errors in useSend

[sentry]

This PR addresses an issue where Sentry was reporting "Error: User cancelled transaction" events from hooks/useSend.ts as actual errors.

Problem:
When a user deliberately cancelled a transaction initiated via useSend.ts (e.g., by dismissing a biometric or passkey prompt), the USER_CANCELLED_TRANSACTION sentinel was converted into a generic Error('User cancelled transaction') and then unconditionally captured by Sentry. This led to false-positive error reports, creating noise in Sentry and obscuring genuine issues.

Root Cause:
Unlike hooks/useWithdraw.ts, which correctly uses the isUserCancelledError utility to prevent Sentry from capturing user-initiated cancellations, hooks/useSend.ts lacked this guard.

Solution:

1. Imported isUserCancelledError from @/lib/utils/withdrawErrors into hooks/useSend.ts.
2. Wrapped the Sentry.captureException call in hooks/useSend.ts with an if (!isUserCancelledError(error)) condition.

This change ensures that user-initiated cancellations are no longer reported to Sentry as errors, reducing noise and improving the signal-to-noise ratio for actual issues.

Fixes SOLID-K6

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated
solid-app	Ignored	Preview	Sep 24, 2026 10:36pm UTC
solid-app-staging	Ignored	Preview	Sep 24, 2026 10:36pm UTC