Merge branch 'develop' into feat/stellar-sponsored-batch-send

Author: Mathew2k-hash

.github/workflows/snippets.yml

@@ -32,6 +32,9 @@ jobs:
       - name: Check snippets
         run: pnpm run check:snippets
 
+      - name: Check nav coverage
+        run: pnpm run check:nav-coverage
+
   stellar-testnet-snippets:
     name: Stellar snippet testnet validation
     runs-on: ubuntu-latest

SECURITY.md

@@ -41,3 +41,5 @@ We operate a discretionary USDC bug bounty:
 Complete details — scope, severity definitions, coordinated disclosure terms, safe-harbor language, reward criteria, and what to include in a report — are in our security disclosure policy:
 
 **https://docs.usewraith.xyz/reference/security-disclosure**
+
+Researchers who want to file a finding should also read the **[Auditor Guide](https://docs.usewraith.xyz/reference/auditor-guide)** — it includes the severity matrix with Wraith-specific examples, the reward ranges, a proof-of-concept template, and our response SLA.

docs.json

@@ -82,6 +82,7 @@
             "group": "Architecture",
             "pages": [
               "architecture/overview",
+              "architecture/announcement-format",
               "architecture/chain-connectors",
               "architecture/tee",
               "architecture/stellar-cryptography",
@@ -90,11 +91,18 @@
           },
           {
             "group": "Contracts",
-            "pages": ["contracts/evm", "contracts/stellar", "contracts/solana", "contracts/ckb", "reference/stellar-event-schemas"]
+            "pages": ["contracts/evm", "contracts/stellar", "contracts/solana", "contracts/ckb"]
           },
           {
             "group": "Reference",
-            "pages": ["reference/security-disclosure", "reference/threat-model", "reference/audits"]
+            "pages": [
+              "reference/audits",
+              "reference/auditor-guide",
+              "reference/security-disclosure",
+              "reference/sep-compatibility",
+              "reference/stellar-networks",
+              "reference/threat-model"
+            ]
           }
         ]
       },
@@ -119,24 +127,33 @@
             "pages": [
               "guides/quickstarts/python"
             ]
+            "pages": ["guides/quickstarts/rust"]
           },
           {
             "group": "Guides",
             "pages": [
               "guides/stealth-payments",
+              "guides/stellar-quickstart",
+              "guides/stellar-quickstart.es",
               "guides/single-chain-agent",
               "guides/multichain-agent",
               "guides/bring-your-own-model",
               "guides/privacy-best-practices",
               "guides/stellar-fees",
               "guides/stellar-troubleshooting",
-              "guides/spectre-stellar-cookbook"
+              "guides/spectre-stellar-cookbook",
+              "guides/stellar-wallet-integration"
             ]
           },
           {
             "group": "Integrations",
             "pages": [
-              "guides/integrations/aquarius"
+              "guides/integrations/aquarius",
+              "guides/integrations/blend",
+              "guides/integrations/nuxt",
+              "guides/integrations/react-native",
+              "guides/integrations/reflector",
+              "guides/integrations/soroswap"
             ]
           },
           {
@@ -145,6 +162,7 @@
               "guides/stellar-mainnet-deployment",
               "guides/stellar-payment-links",
               "guides/stellar-multisig-withdrawal",
+              "guides/stellar/multisig-authority-rotation",
               "guides/stellar-offline-signing",
               "guides/stellar-tx-simulation",
               "guides/stellar-explorer-recipes",
@@ -153,13 +171,12 @@
               "guides/stellar/stellar-liquidity-pool-swap",
               "guides/stellar/stellar-path-payment",
               "guides/stellar/sponsored-batch-send",
+              "guides/stellar/passkey-signing",
+              "guides/stellar/stellar-quickstart",
+              "guides/stellar/wraith-names-lifecycle",
               "guides/wraith-names-stellar",
               "guides/ops/self-hosted-deployment"
             ]
-          },
-          {
-            "group": "Integrations",
-            "pages": ["guides/integrations/nuxt"]
           }
         ]
       },
@@ -171,6 +188,7 @@
             "pages": [
               "api-reference/endpoints",
               "api-reference/fetch-announcements-stream",
+              "api-reference/stealth-keys",
               "api-reference/types"
             ]
           }

docs/CONTRIBUTING.md

@@ -27,8 +27,30 @@ Use `no-check` only for intentionally illustrative pseudocode:
 
 Prefer making snippets compile over opting them out.
 
+## Navigation coverage
+
+Every `.mdx` page in the shipped taxonomy (root pages plus `architecture/`,
+`api-reference/`, `contracts/`, `guides/`, `reference/`, and `sdk/`) must be
+registered in the `docs.json` navigation tree, and every navigation entry must
+resolve to a real file. This is enforced by:
+
+```bash
+npm run check:nav-coverage
+```
+
+The checker (`scripts/check-nav-coverage.mjs`) scans for `.mdx` files that are
+missing from `docs.json` and for nav entries that point at files that no longer
+exist. Run it after adding, renaming, or removing a page:
+
+```bash
+node scripts/check-nav-coverage.mjs
+```
+
+Note: `docs.json` is strict JSON — do not add `//` comments to it, the Mintlify
+CLI rejects them. Keep this file comment-free.
+
 ## CI
 
-Every pull request runs the snippet checker through GitHub Actions. A separate
-non-blocking Stellar testnet job is reserved for end-to-end snippet validation
-that depends on network availability.
+Every pull request runs the snippet checker and the nav coverage check through
+GitHub Actions. A separate non-blocking Stellar testnet job is reserved for
+end-to-end snippet validation that depends on network availability.