[skill-drift] fix(skill-drift): update cocoa/react-native/ruby skills for recent SDK changes

[github-actions]

SDK Changes

The following merged PRs triggered these skill updates:

• getsentry/sentry-cocoa#7831 — ref: Remove session replay environment checker and related options (ref: Remove session replay environment checker and related options sentry-cocoa#7831)
• getsentry/sentry-react-native#6070 — feat(core): Support SENTRY_RELEASE and SENTRY_DIST env vars in build scripts (feat(core): Support SENTRY_RELEASE and SENTRY_DIST env vars in build scripts sentry-react-native#6070)
• getsentry/sentry-ruby#2925 — feat(yabeda): Add sentry-yabeda adapter gem (feat(yabeda): Add sentry-yabeda adapter gem sentry-ruby#2925)

Changes Made

skills/sentry-cocoa-sdk/references/session-replay.md

• Removed experimental.enableSessionReplayInUnreliableEnvironment from the config options table (option was removed from SDK)
• Removed the code example showing how to force-enable replay on iOS 26+ via the removed option
• Removed best-practice note that referenced the removed option
• Updated iOS 26 troubleshooting entry to remove reference to the removed override option

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

• Added Env: SENTRY_DIST annotation to the dist option in the Core Options table
• Added SENTRY_DIST row to the Environment Variables table

skills/sentry-ruby-sdk/SKILL.md

• Added sentry-yabeda gem to the Gemfile install block
• Added Yabeda to the Framework Integration table with auto-instrument description
• Added Yabeda detection to the Phase 1 Detect script
• Added routing note for Yabeda detection in Phase 1 routing logic

Verified Against

• sentry-cocoa@main (PR #7831, merged 2026-04-29)
• sentry-react-native@main (PR #6070, merged 2026-04-30)
• sentry-ruby@main (PR #2925, merged 2026-05-04)

Note

🔒 Integrity filter blocked 6 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".
• #7847 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1168 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #893 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #2411 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #2938 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

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 · ● 828.3K · ◷

• expires on May 18, 2026, 1:25 PM UTC

[sentry]

Bug: The documentation incorrectly describes SENTRY_DIST as a runtime environment variable, but it is only used at build-time, which may mislead users.
_{Severity: LOW}

Suggested Fix

Update the documentation in SKILL.md to clarify that SENTRY_DIST is a build-time environment variable. Consider moving it out of the section for runtime variables or adding a clear note explaining its build-time-only nature.

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-native-sdk/SKILL.md#L662

Potential issue: The documentation for the `SENTRY_DIST` environment variable in
`SKILL.md` is misleading. It is listed with runtime variables and described as 'Falls
back from `dist` option', implying it can be set at runtime. However, evidence from the
original feature implementation and official Sentry documentation indicates that
`SENTRY_DIST` is exclusively a build-time variable. Setting it at runtime will have no
effect, which could lead to confusion and incorrect configuration for users trying to
set the distribution at runtime.

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