[skill-drift] update(sentry-tanstack-start-sdk): client init pattern + beta status

[github-actions]

Warning

Auto-generated from external SDK content. Review all links and code suggestions before acting on them.

cc @getsentry/support

Summary

The TanStack Start SDK skill needs updates based on recent changes in getsentry/sentry-javascript:

1. Client Initialization Pattern Change (High Priority)

PR #21161 changed the recommended client-side initialization pattern:

Old pattern (currently in skill):

• Sentry.init() called in src/router.tsx inside getRouter()
• Gated with if (!router.isServer)
• tanstackRouterBrowserTracingIntegration(router) passed directly in integrations array

New pattern (from PR #21161):

• Sentry.init() called in src/client.tsx at top level, before hydrateRoot()
• tanstackRouterBrowserTracingIntegration(router) added separately in src/router.tsx via Sentry.addIntegration()

Rationale: Moving init to the client entry point ensures Sentry captures errors and breadcrumbs that occur before hydration (e.g., third-party library initialization errors). The previous pattern silently lost pre-hydration events.

Affected sections in SKILL.md:

• Phase 1: Detect (file detection logic)
• Phase 3: Configure Client-Side Sentry section (currently shows src/router.tsx pattern)
• New section needed for src/client.tsx setup
• Router section needs update to show Sentry.addIntegration() pattern

2. SDK Status Update (Mechanical)

PR #21175 promoted the SDK from alpha to beta:

Current (line 22-23):

> **Note:** This SDK is currently alpha and documented as compatible with TanStack Start `1.0 RC`.

Should be:

> **Note:** This SDK is currently in beta. The minimum supported version of TanStack Start is `1.111.12`.

References

• PR #21161 - Move initialization to client entry point
• PR #21175 - Promote SDK to beta
• Test app client.tsx
• Test app router.tsx