[Eras256]

The README in the public mirror and the one in the private source had drifted apart. Each had edits the other didn't (the mirror had the status table, Why now and the Blend notes; the private copy had the source-verified vault). This PR puts the same file in both repos.

What changed, all checked live on 10 Nov 2026:

• Title is now "Nirium Core", with the brand line and a short note that npm/PyPI packages are released from nirium-protocol/nirium. Added the reviewer pointer to FOR-REVIEWERS.md and EVIDENCE.md.
• Removed the nine static shields.io badges (x402 "In Production", "Status Active", etc.). They can't go stale-proof. The CI and Security Gate badges stay.
• Status table now matches the nirium README: x402 last settled payment 29 Sep 2026 (from Horizon, recipient GCLBBPON), Audit Trail last anchor 6 Nov, Payouts with no mainnet runs yet.
• NiriumVault is now the source-verified CDMFURE6 everywhere, with the earlier deployments named.
• The three IPFS receipts marked 404 in October resolve again (200 on Pinata and nirium.myfilebase.com), noted with a dated update.
• Package versions from the registries: nirium 0.19.0, PyPI 0.11.1, nirium-mcp 0.6.4, nirium-cli 3.2.1, adapter 0.6.0.
• Six signed letters of intent instead of two, linked to EVIDENCE.md section 12, with a dated note.
• SCF Build Award row: submitted for SCF chore(deps): Bump @supabase/supabase-js from 2.103.0 to 2.118.0 #46 on 9 Nov.
• Removed the Fintech World Cup line (an award for a project on another chain).
• "27 routes" dropped (the app has 43 pages now). The 102 endpoints stays: 101 HTTP routes + 1 WebSocket, counted in the agent source.
• Quick start no longer says pnpm dev runs the agent here, since packages/agent is a types-only stub in this repo. Removed the Deploy commands for the same reason.
• MPP launch date softened to "March 2026" (couldn't confirm the exact day). The April 2 x402 Foundation date is confirmed.

Not in this PR: CI and the Security Gate are red on the public main since 5 Nov (SDK tests on @x402 2.28 and a follow-redirects override at >=1.16.1 instead of >=1.16.2). That's a dependency change and goes in its own PR.

🤖 Generated with Claude Code

[M0nsxx]

Reviewed. Same README in mirror and source, statuses dated against Horizon and the live API, verified vault CDMFURE6, current versions, six LOIs. Approving.