chore: remove stale and internal files from the public mirror

CONTRIBUTING.md

@@ -47,8 +47,8 @@ pnpm dev
 ```
 nirium-core/
 ├── apps/web/                  → Next.js 15 Dashboard - 27 routes, i18n (EN/ES)
-├── packages/sdk/              → TypeScript SDK v0.16.1 (npm: nirium)
-├── packages/sdk-python/       → Python SDK v0.11.0 (PyPI: nirium)
+├── packages/sdk/              → TypeScript SDK v0.19.0 (npm: nirium)
+├── packages/sdk-python/       → Python SDK v0.11.1 (PyPI: nirium)
 ├── nirium-soroban-contracts/  → Soroban smart contracts (Rust): NiriumVault + NiriumProtocol, both deployed on testnet
 └── .github/workflows/         → CI, release, security-gate
 ```

MCP_INTEGRATION_GUIDE.md

@@ -1,5 +1,7 @@
 # Nirium MCP Server - Integration Guide v0.4.0
 
+> **Historical document (MCP v0.4.0, April 2026), kept for reference.** The maintained guide is the [`nirium-mcp` README](https://github.com/nirium-protocol/nirium/tree/main/packages/mcp) in nirium-protocol/nirium, with the current tool list. Current release, checked on npm on 11 Nov 2026: `nirium-mcp` 0.6.4.
+
 > Model Context Protocol server for Nirium Protocol.
 > Exposes 11 tools to any MCP-compatible AI: Claude, GPT, Cursor, VS Code Copilot.
 > Published on npm as [`nirium-mcp`](https://www.npmjs.com/package/nirium-mcp).

NIRIUM_TECHNICAL_PAPER.md

@@ -2,6 +2,8 @@
 > Institutional DeFi Infrastructure Powered by Autonomous Agents on Stellar/Soroban
 
 **Version:** 2.5 - July 2026 (Updated Jul 13, 2026 - dual-network execution nodes, self-service API keys, non-custodial Payouts)
+
+> **Update, 2026-11-11:** figures in this paper (versions, endpoint counts) are as of its July-October 2026 revisions. The testnet NiriumVault is now the source-verified build `CDMFURE6…` (see section 3.1). Current status and evidence: [README](README.md) and [EVIDENCE.md](https://github.com/nirium-protocol/nirium/blob/main/EVIDENCE.md).
 **Author:** Nirium Protocol Team
 **Network:** Stellar Testnet (NiriumVault treasury, audit-gated) + Mainnet (receive-only execution nodes, early access)
 **Contact:** niriumprotocol@gmail.com
@@ -54,8 +56,8 @@ The LLM layer advises. The contract decides. A compromised LLM cannot drain fund
 
 ### 3.1 NiriumVault - Primary Execution Contract
 
-**Contract ID:** `CBTWMZCG3P72EHFAQ4ZLSEBIOFYJC244H5J6DHZIJ56FHFWJ2CFAWSZU`
-**Active Vault:** ID 1 (testnet, agent delegated)
+**Contract ID:** `CDMFURE6MYROTA2A6DLD4TN2S4QTN64L2FZ2I2RY2AREONX6DUQOI2S2` (testnet, source-verified on Stellar Expert, 9 Nov 2026)
+**Update, 2026-11-11:** this section previously listed `CBTWMZCG3P72EHFAQ4ZLSEBIOFYJC244H5J6DHZIJ56FHFWJ2CFAWSZU` with "Active Vault: ID 1". That was the deployment nirium.xyz used until 9 Nov 2026; the site now uses the source-verified build above.
 
 Core functions:
 - `create_vault(owner, asset, name, xlm_address)` - deploys vault, charges 12.5 XLM

SDKs.md

@@ -1,5 +1,7 @@
 # Nirium Protocol - Official SDK Documentation
 
+> **Historical document (SDK 0.5.0, spring 2026), kept for reference.** The maintained SDK docs are the package READMEs in [nirium-protocol/nirium](https://github.com/nirium-protocol/nirium): TypeScript `nirium` ([packages/sdk](https://github.com/nirium-protocol/nirium/tree/main/packages/sdk)) and Python `nirium` ([packages/sdk-python](https://github.com/nirium-protocol/nirium/tree/main/packages/sdk-python)). Current releases, checked on npm and PyPI on 11 Nov 2026: `nirium` 0.19.0 (npm) and `nirium` 0.11.1 (PyPI).
+
 **Version:** 0.5.0  
 **Packages:** `nirium` on npm · `nirium` on PyPI  
 **API Base:** `https://nirium-agent.fly.dev`