[skill-drift] fix(multi-sdk): update 4 skills for recent SDK changes

[github-actions]

SDK Changes

The following PRs were merged in the last 7 days that affect skill files:

• feat: Implement strict trace continuation sentry-cocoa#7705 — feat: Implement strict trace continuation (feat: Implement strict trace continuation sentry-cocoa#7705)
• feat(metrics): add metric_flush_threshold flag sentry-php#2059 — feat(metrics): add metric_flush_threshold flag (feat(metrics): add metric_flush_threshold flag sentry-php#2059)
• feat(ios): Add attachAllThreads option sentry-react-native#5960 — feat(ios): Add attachAllThreads option (feat(ios): Add attachAllThreads option sentry-react-native#5960)
• feat(core): Add Sentry.appLoaded() API to signal app start end sentry-react-native#5940 — feat(core): Add Sentry.appLoaded() API to signal app start end (feat(core): Add Sentry.appLoaded() API to signal app start end sentry-react-native#5940)
• feat(react-router): Export sentryOnError sentry-javascript#20120 — feat(react-router): Export sentryOnError (feat(react-router): Export sentryOnError sentry-javascript#20120)

Changes Made

skills/sentry-cocoa-sdk/references/tracing.md

• Added strictTraceContinuation and orgId to the Configuration table
• Added a "Strict Trace Continuation" subsection under Distributed Tracing with a Swift code example

skills/sentry-php-sdk/references/metrics.md

• Added a new "Threshold-Based Auto-Flushing" section documenting metric_flush_threshold for PHP/Laravel
• Added metric_flush_threshold to the Symfony YAML configuration example

skills/sentry-react-native-sdk/SKILL.md

• Added attachAllThreads (iOS only) to the Native/Mobile Options table
• Added a new "App Start Accuracy — Sentry.appLoaded()" section explaining when and how to call it

skills/sentry-react-sdk/references/tracing.md

• Added Sentry.sentryOnError as a simpler alternative to SentryRouteErrorBoundary in the React Router v7 error handling section

Verified Against

• getsentry/sentry-cocoa@main (PR #7705)
• getsentry/sentry-php@master (PR #2059)
• getsentry/sentry-react-native@main (PRs #5960, #5940)
• getsentry/sentry-javascript@develop (PR #20120)

Note

🔒 Integrity filter blocked 21 items

The following items were blocked because they don't meet the GitHub integrity level.

• #282 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #20123 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5067 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5951 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5914 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5913 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5902 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5900 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5901 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5897 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5893 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5892 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5891 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5863 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5864 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5865 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 5 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by SDK Skill Drift Detector · ● 1.1M · ◷

• expires on Apr 23, 2026, 8:22 AM UTC

[sentry]

Bug: The documentation example for React Router v7 incorrectly uses the onError property on a route object. The correct property is errorElement, causing silent failure of error reporting.
_{Severity: HIGH}

Suggested Fix

Replace the incorrect onError: Sentry.sentryOnError example with the correct pattern using the errorElement property, such as errorElement: <SentryRouteErrorBoundary />. This will align the new example with the established, correct pattern already present in the documentation and ensure routing errors are captured by Sentry.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: skills/sentry-react-sdk/references/tracing.md#L459-L466

Potential issue: The documentation example for React Router v7 error handling suggests
using `onError: Sentry.sentryOnError` on individual route objects. However, `onError` is
not a valid property for route objects in React Router v7; it is only valid on the
`<RouterProvider>` component. The correct property is `errorElement`. This is
contradicted by another example in the same file which correctly uses `errorElement`.
Code following the new, incorrect example will silently fail to capture routing errors,
leading to a complete loss of error visibility for those routes.

_{Did we get this right? 👍 / 👎 to inform future reviews.}