docs: Add trailing slashes to internal links in develop-docs (#19813)

## DESCRIBE YOUR PR

The last bucket from the trailing-slash work in #19639 and #19675, which
covered only the user docs.

`develop-docs/` renders at **develop.sentry.dev** from the same Next
config, so the same rule applies — a link without a trailing slash is
served a 308 before the page loads:

```
https://develop.sentry.dev/backend/application-domains   -> 308
https://develop.sentry.dev/backend/application-domains/  -> 200
```

**240 links across 39 files**, produced by `pnpm
lint:trailing-slash:fix` from #19666. No hand edits.

### Verification

- Every changed file differs from master **only by added `/`
characters** — no slash removed, no external URL altered, no other
content touched
- A sample of 25 rewritten destinations all return **200** on
develop.sentry.dev
- `pnpm lint:trailing-slash` is now clean for `develop-docs/`

The 23 violations the linter still reports are drift in `docs/`, fixed
separately in #19811.

> Note: `AGENTS.md` describes `develop-docs/` as a submodule, but it
isn't one — `git submodule status` is empty and the directory has direct
commits in this repo. Worth correcting in that file at some point,
though I've left it out of this PR.

## IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the
due date. You can update this information later by editing the PR
description.

- [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD
- [ ] Other deadline: YYYY-MM-DD
- [x] No deadline: 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
supplied a deadline.

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](https://github.com/orgs/getsentry/teams/docs)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Author: 2 people

.lycheeignore

@@ -66,3 +66,4 @@ https?://empowerplant\.io.*
 
 # Private GitHub repos
 https?://github\.com/getsentry/sdk-skills.*
+https?://github\.com/getsentry/security-as-code.*

develop-docs/getting-started/index.mdx

@@ -4,7 +4,7 @@ description: This documentation serves as reference points for developing agains
 sidebar_order: 1
 ---
 
-We recommend going through the [engineering practices](/engineering-practices) and our [development philosophy](/getting-started/philosophy/) before contributing a change to Sentry.
+We recommend going through the [engineering practices](/engineering-practices/) and our [development philosophy](/getting-started/philosophy/) before contributing a change to Sentry.
 
 
 <DevDocsCardGrid />

develop-docs/sdk/foundations/client/index.mdx

@@ -51,7 +51,7 @@ Related specs:
 - [Scopes](/sdk/foundations/state-management/scopes/) — scope chain and client resolution
 - [Transport](/sdk/foundations/transport/) — envelope delivery
 - [Envelopes](/sdk/foundations/envelopes/) — wire format
-- [Attributes](/sdk/foundations/state-management/scopes/attributes) — attribute type system
+- [Attributes](/sdk/foundations/state-management/scopes/attributes/) — attribute type system
 
 ---
 

develop-docs/sdk/foundations/client/integrations/graphql.mdx

@@ -20,7 +20,7 @@ sidebar_order: 2
 
 ## Overview
 
-GraphQL client integrations should match the guidelines for [HTTP Client Integrations](/sdk/foundations/client/integrations/http-client) with differences described below.
+GraphQL client integrations should match the guidelines for [HTTP Client Integrations](/sdk/foundations/client/integrations/http-client/) with differences described below.
 
 ---
 

develop-docs/sdk/foundations/client/integrations/index.mdx

@@ -26,10 +26,10 @@ Users configure integrations via the `integrations` option in `Sentry.init()`.
 
 Related specs:
 - [Client](/sdk/foundations/client/) — client lifecycle and event pipeline
-- [HTTP Client Integration](/sdk/foundations/client/integrations/http-client) — HTTP client instrumentation guidelines
-- [GraphQL Integration](/sdk/foundations/client/integrations/graphql) — GraphQL client instrumentation guidelines
-- [Feature Flags Integration](/sdk/foundations/client/integrations/feature-flags) — feature flag tracking guidelines
-- [Modules Integration](/sdk/foundations/client/integrations/modules) — loaded library and version reporting
+- [HTTP Client Integration](/sdk/foundations/client/integrations/http-client/) — HTTP client instrumentation guidelines
+- [GraphQL Integration](/sdk/foundations/client/integrations/graphql/) — GraphQL client instrumentation guidelines
+- [Feature Flags Integration](/sdk/foundations/client/integrations/feature-flags/) — feature flag tracking guidelines
+- [Modules Integration](/sdk/foundations/client/integrations/modules/) — loaded library and version reporting
 
 ---
 

develop-docs/sdk/foundations/client/integrations/mcp/index.mdx

@@ -6,5 +6,5 @@ The MCP Server module instruments Anthropic's Model Context Protocol (MCP) SDKs.
 
 ## Features
 
-- [Tracing](./tracing)
-- [Errors](./errors)
+- [Tracing](./tracing/)
+- [Errors](./errors/)

develop-docs/sdk/foundations/processing/batch-processor.mdx

@@ -38,7 +38,7 @@ The BatchProcessor **MUST** forward all spans and logs in memory to the transpor
 2. When the user calls  `SentrySDK.close()`, the BatchProcessor **MUST** forward all data in memory to the transport. SDKs **SHOULD** keep their existing closing behavior.
 3. When the application shuts down gracefully, the BatchProcessor **SHOULD** forward all data in memory to the transport. The transport **SHOULD** keep its existing behavior, which usually stores the data to disk as an envelope. It is not required to call a transport `flush`. This is mostly relevant for mobile SDKs already subscribed to these hooks, such as [applicationWillTerminate](https://developer.apple.com/documentation/uikit/uiapplicationdelegate/applicationwillterminate(_:)) on iOS.
 4. When the application moves to the background, the BatchProcessor **SHOULD** forward all the data in memory to the transport and stop the timer. The transport **SHOULD** keep its existing behavior, which usually stores the data to disk as an envelope. It is not required to call the transport `flush`. This is mostly relevant for mobile SDKs.
-5. Mobile SDKs **MUST** minimize data loss when sudden process terminations occur. Refer to the [Mobile Telemetry Processor](/sdk/foundations/processing/telemetry-processor/mobile-telemetry-processor) section for more details.
+5. Mobile SDKs **MUST** minimize data loss when sudden process terminations occur. Refer to the [Mobile Telemetry Processor](/sdk/foundations/processing/telemetry-processor/mobile-telemetry-processor/) section for more details.
 
 The detailed specification is written in the [Gherkin syntax](https://cucumber.io/docs/gherkin/reference/). The specification uses spans as an example, but the same applies to logs or any other future telemetry data.
 

develop-docs/sdk/foundations/state-management/hub-and-scope/index.mdx

@@ -61,7 +61,7 @@ The decision to remove the Hub from all Sentry SDKs was confirmed on 2024-05-03
 
 - **Disabled SDK**: The SDK is considered disabled when the client has no transport. In this state, callbacks like `configure_scope` and event processors **SHOULD NOT** be invoked, and breadcrumbs **SHOULD NOT** be recorded.
 
-- **Automatic Context Data**: SDKs and their integrations automatically populate scopes with useful contextual data such as tags, contexts, and extras. This typically happens by hooking into a framework (e.g., a web framework middleware setting request-related context on the scope). See [Data Scrubbing](/sdk/foundations/data-scrubbing) for considerations around sensitive data.
+- **Automatic Context Data**: SDKs and their integrations automatically populate scopes with useful contextual data such as tags, contexts, and extras. This typically happens by hooking into a framework (e.g., a web framework middleware setting request-related context on the scope). See [Data Scrubbing](/sdk/foundations/data-scrubbing/) for considerations around sensitive data.
 
 ---
 

develop-docs/sdk/foundations/state-management/scopes/index.mdx

@@ -72,7 +72,7 @@ Scopes are the mechanism by which Sentry SDKs propagate contextual data (tags, b
 This model replaces the [Hub & Scope](/sdk/foundations/state-management/hub-and-scope/) model. The Hub is removed; its functionality is absorbed into the three scope types. The design aligns with [OpenTelemetry's Context](https://opentelemetry.io/docs/specs/otel/context/) propagation — an immutable, fork-on-write mechanism that carries execution-scoped values across API boundaries. See [RFC 0122](https://github.com/getsentry/rfcs/pull/122) for the original design.
 
 Related specs:
-- [Attributes](/sdk/foundations/state-management/scopes/attributes) — attribute type system for scope data
+- [Attributes](/sdk/foundations/state-management/scopes/attributes/) — attribute type system for scope data
 - [Breadcrumbs](/sdk/foundations/state-management/scopes/breadcrumbs/) — structured event trail on scopes
 - [Hub & Scope](/sdk/foundations/state-management/hub-and-scope/) — deprecated predecessor
 
@@ -96,7 +96,7 @@ This replaces the manual hub-cloning pattern from the old model. Users no longer
 
 ### Automatic Context Data
 
-SDKs and their integrations automatically populate scopes with useful contextual data such as tags, contexts, and attributes. This typically happens by hooking into a framework (e.g., a web framework middleware setting request-related context on the isolation scope). This automatic enrichment is a key benefit of scopes — users get useful data on events without manual instrumentation. See [Data Scrubbing](/sdk/foundations/data-scrubbing) for considerations around sensitive data.
+SDKs and their integrations automatically populate scopes with useful contextual data such as tags, contexts, and attributes. This typically happens by hooking into a framework (e.g., a web framework middleware setting request-related context on the isolation scope). This automatic enrichment is a key benefit of scopes — users get useful data on events without manual instrumentation. See [Data Scrubbing](/sdk/foundations/data-scrubbing/) for considerations around sensitive data.
 
 ### Scope Chain
 

develop-docs/sdk/getting-started/ai-tools/index.mdx

@@ -20,4 +20,4 @@ This section covers the AI tools available to SDK engineers, how they layer toge
 | **[Sentry CLI](https://docs.sentry.io/ai/sentry-cli/)** | Natural-language issue management | List, inspect, and triage issues from the terminal or an agent |
 | Rules files | Workflow-specific instructions | Fixed conventions that vary by task or directory |
 
-Requirement levels (MUST/SHOULD) are defined in [Repository and Documentation Standards](/sdk/getting-started/standards/repository-docs) and [Review and CI Standards](/sdk/getting-started/standards/review-ci).
+Requirement levels (MUST/SHOULD) are defined in [Repository and Documentation Standards](/sdk/getting-started/standards/repository-docs/) and [Review and CI Standards](/sdk/getting-started/standards/review-ci/).