`docs.json` navigation cleanup for shipped Wave 7 pages

[truthixify]

Tier: S (1-2 days) | Type: chore

Context. Wave 7 landed a large batch of new pages but docs.json (the Mintlify nav) was never updated for most of them. Pages that exist on disk but are absent from the nav include guides/stellar/stellar-quickstart, guides/stellar/wraith-names-lifecycle, guides/integrations/blend, guides/integrations/soroswap, guides/integrations/reflector, guides/integrations/react-native, reference/security-disclosure, reference/threat-model, reference/audits, reference/stellar-networks, architecture/view-tag-scanner, architecture/announcement-format, and the ES translations (*.es.mdx). Readers can only reach them via search or direct link, which is the wrong default.

Scope.

• Audit every .mdx under guides/, reference/, concepts/, architecture/, api-reference/, sdk/ against the docs.json tree; add any missing page under its natural section.
• Add locale groups for es where an .es.mdx variant exists (Mintlify supports per-locale navigation entries).
• Order new entries alphabetically within each group unless there is an existing curated order.
• Add a comment header in docs.json naming the audit script (below) so future waves can rerun it.
• Add scripts/check-nav-coverage.mjs: scans mdx files and fails if any is missing from docs.json; wire it into the Compile docs snippets CI job.

Acceptance.

• Every existing mdx page in the shipped taxonomy is reachable from docs.json
• scripts/check-nav-coverage.mjs exits 0 on the current tree
• CI fails a PR that adds an mdx page without registering it in docs.json
• Renders in mint dev

Files. docs.json, scripts/check-nav-coverage.mjs (new), .github/workflows/ci.yml.

[franklin251861-killer]

@franklin251861-killer has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hey maintainer I would like to work on this issue, assign it to me .

ℹ️ Repo Maintainers: To accept this application, review their application or assign @franklin251861-killer to this issue.

[drips-wave]

Congratulations, @franklin251861-killer! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @franklin251861-killer: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @franklin251861-killer as part of the Stellar Wave Program's 8th Wave 🥳

😎 @franklin251861-killer: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.