fix(wasm): document support and adoption of build_id section

[supervacuus]

DESCRIBE YOUR PR

This is a follow-up to #14591.

The current state of the docs (across platforms) does not reflect:

• that thebuild_id section is officially part of the WASM tooling conventions
• that this section is adopted by tooling other than Sentry (in particular, LLVM and thus emscripten supports it since version 17)
• how wasm-split still fits in this landscape

This PR tries to rectify this.

Open topics:

• It is obvious that file-formats and identifiers are duplicates across all platforms with WASM support. Of course, these could be extracted into includes, but I am no longer sure what the current approach in docs is regarding deduplication of sections.
• I am not sure if the statement regarding WASM source maps (the text above my changes in the file-formats section) still holds, but we can fix those in another PR.

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

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project	Deployment	Preview	Comments	Updated (UTC)
sentry-docs	🛑 Canceled			Aug 12, 2025 10:01am

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
develop-docs	⬜️ Ignored	Preview		Aug 12, 2025 10:01am

[codecov]

Bundle Report

Changes will increase total bundle size by 1.35kB (0.01%) ⬆️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
sentry-docs-client-array-push	9.85MB	-6 bytes (-0.0%) ⬇️
sentry-docs-server-cjs	12.38MB	1.36kB (0.01%) ⬆️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
static/chunks/pages/_app-*.js	-3 bytes	882.71kB	-0.0%
static/chunks/8321-*.js	-3 bytes	425.87kB	-0.0%
server/middleware-*.js	-5.55kB	1.0kB	-84.74%
server/middleware-*.js	5.55kB	6.55kB	555.3% ⚠️
static/HR6gFxCHn57q64Baon0Wx/_buildManifest.js (New)	684 bytes	684 bytes	100.0% 🚀
static/HR6gFxCHn57q64Baon0Wx/_ssgManifest.js (New)	77 bytes	77 bytes	100.0% 🚀
static/Y_Ge8RttZxzBllCkofes7/_buildManifest.js (Deleted)	-684 bytes	0 bytes	-100.0% 🗑️
static/Y_Ge8RttZxzBllCkofes7/_ssgManifest.js (Deleted)	-77 bytes	0 bytes	-100.0% 🗑️

view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
1729.js	-3 bytes	1.77MB	-0.0%
../instrumentation.js	-3 bytes	1.1MB	-0.0%
9523.js	-3 bytes	1.08MB	-0.0%
../app/[[...path]]/page.js.nft.json	455 bytes	744.91kB	0.06%
../app/platform-redirect/page.js.nft.json	455 bytes	744.83kB	0.06%
../app/sitemap.xml/route.js.nft.json	455 bytes	742.3kB	0.06%

[JoshuaMoelans]

LGTM, just a recurring typo that slipped through. Not sure if the suggestion is exactly how you wanted to write it, so feel free to adjust :)