fix(ruby-sdk): add strict_trace_continuation and org_id config options

[Copilot]

Two new distributed tracing config options from sentry-ruby v6.5.0 (PR #2872) were missing from the skill, plus a Rails queue time fix from v6.4.1 (PR #2877) wasn't reflected.

references/tracing.md

• Added org_id and strict_trace_continuation to the config table
• Added "Strict trace continuation (v6.5.0+)" subsection with a config example and a full decision matrix covering all combinations of incoming baggage org ID, SDK org ID, and strict mode
• Updated capture_queue_time note to reference the v6.4.1 Rails fix

SKILL.md

• Added org_id and strict_trace_continuation rows to the Phase 3 Sentry.init options table
• Updated version reference to v6.4.1 and capture_queue_time note to match

Sentry.init do |config|
  # Explicitly set org ID for self-hosted / Relay setups where DSN parsing fails
  config.org_id = "123456"

  # Reject incoming traces whose sentry-org_id baggage doesn't match this SDK's org
  config.strict_trace_continuation = true
end

strict_trace_continuation is relevant for microservice architectures where Ruby services may receive requests from third-party Sentry users — without it, foreign trace IDs can bleed into your dashboards.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[skill-drift] sentry-ruby-sdk may need updates</issue_title>
<issue_description>## SDK Changes Detected

The following PRs were merged to getsentry/sentry-ruby in the last 7 days that may affect the sentry-ruby-sdk skill:

• feat: Implement strict trace continuation sentry-ruby#2872 — feat: Implement strict trace continuation (feat: Implement strict trace continuation sentry-ruby#2872)
• chore(transport): Handle HTTP 413 response for oversized envelopes sentry-ruby#2885 — chore(transport): Handle HTTP 413 response for oversized envelopes (chore(transport): Handle HTTP 413 response for oversized envelopes sentry-ruby#2885)
• fix(rails): Track request queue time in Rails middleware sentry-ruby#2877 — fix(rails): Track request queue time in Rails middleware (fix(rails): Track request queue time in Rails middleware sentry-ruby#2877)

Potential Skill Gaps

1. New Config Options: PR #2872 adds two new configuration options not present in the skill's tracing reference table:

   • config.strict_trace_continuation (Boolean, default false) — controls whether the SDK starts a new trace when incoming sentry-org_id baggage doesn't match the SDK's org ID. Prevents inadvertent trace continuation from third-party services.
   • config.org_id (String) — explicitly set the organization ID (useful for self-hosted/Relay setups where DSN-based parsing may not work). Takes precedence over DSN-extracted org ID.

   The skill's tracing config table in references/tracing.md currently lists: traces_sample_rate, traces_sampler, trace_propagation_targets, propagate_traces. Neither new option appears.

2. Rails Queue Time Fix: PR #2877 fixes request queue time tracking in Rails middleware. The skill (references/tracing.md) mentions queue time capture being automatic in v6.4.0+ via Puma — this fix may change behavior or requirements worth documenting.

Skill Files to Review

• skills/sentry-ruby-sdk/SKILL.md — init options table in Phase 3
• skills/sentry-ruby-sdk/references/tracing.md — distributed tracing config table and propagation section

Priority

MEDIUM — new configuration options that affect distributed tracing behavior; relevant for microservice architectures using Ruby services.

Generated by SDK Skill Drift Detector · ◷

• expires on Mar 21, 2026, 9:08 PM UTC

Comments on the Issue (you are @copilot in this section)

Custom agent used: skill-updater
Expert Sentry SDK skill author that updates and creates SDK skill bundles. Specializes in researching SDK changes, verifying APIs against official docs and source code, and producing high-quality wizard flows with deep-dive reference files. Use when updating skills after SDK changes, creating new skills for new platforms, or fixing skill drift issues.

• Fixes [skill-drift] sentry-ruby-sdk may need updates #39

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.