DO NOT MERGE - docs(sdk): standards and playbooks

[stephanie-anderson]

DESCRIBE YOUR PR

Add enforceable SDK standards and step-by-step playbooks to the Getting Started section of the SDK develop-docs.

Standards (7 categories):

• Planning & Scoping, Code Submission, Code Quality, API & Architecture, Review & CI, Repository & Documentation, Coordination & Maintenance
• Each standard defines the rule, enforcement mechanism, suggested skills, and per-SDK override policy

Playbooks (12 workflows):

• Opening a PR, reviewing a PR, reviewing AI-generated code, cutting a release, handling a regression, deprecating an API, dropping platform support, adding a dependency, cross-SDK rollout, handling external contributor PRs, setting up a new SDK repo, quarterly retro

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
  Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

Co-Authored-By: Claude noreply@anthropic.com

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview, Comment	Feb 18, 2026 9:47am
sentry-docs	Ready	Preview, Comment	Feb 18, 2026 9:47am

[dingsdax]

Suggested change

Every PR must include a description with: what the PR does, why these changes are being made, links to relevant issues or tickets (required for non-trivial changes; typo and one-line doc fixes exempt), alternative approaches considered (if any), additional context reviewers need. No test plan sections, no checkbox lists, no boilerplate. The tests in the diff are the test plan. Blank descriptions, template-only descriptions, and AI-generated filler are not acceptable.

Every PR must include a description with: what the PR does, why these changes are being made, links to relevant issues or tickets (required for non-trivial changes; typo and one-line doc fixes exempt), alternative approaches considered (if any), additional context reviewers need. No test plan sections, no checkbox lists, no boilerplate. The tests in the diff are the test plan. Blank descriptions, template-only descriptions, and AI-generated filler are not acceptable. PR descriptions must not include any customer data or sensitive information.