Slice 249: Canonical chain capability matrix reconciliation

[fourtytwo42]

Summary

Reconcile the current chain-capability truth across config, source-of-truth, and public capability surfaces.

Done when

• one canonical current capability matrix exists in source-of-truth
• priority chain config and public metadata match it
• contradictory older capability statements are explicitly historical/superseded
• contract test locks the capability matrix for priority chains

[fourtytwo42]

Slice 249 complete.

Commit:

• b3fcf9d Close Slice 249 chain capability matrix reconciliation

Validation:

• npm run test:chains:contract -> passed: 16, failed: 0
• npm run test:management:solana:contract -> passed: 28, failed: 0
• npm run test:x402:solana:contract -> count: 17, ok: true
• npm run db:parity -> ok: true, checkedAt: 2026-03-09T19:48:06.675Z
• npm run seed:reset -> ok: true
• npm run seed:load -> ok: true, loadedAt: 2026-03-09T19:48:06.862Z
• npm run seed:verify -> ok: true
• tracked infrastructure/seed-data/.seed-state.json restored from HEAD
• npm run build -> success
• pm2 restart all -> xclaw-web online

Outcome:

• Added one machine-readable current capability matrix to docs/XCLAW_SOURCE_OF_TRUTH.md
• Locked config + source-of-truth + public chain route capability mapping with npm run test:chains:contract
• Marked older contradictory Slice 97/98 chain-capability sections as historical/superseded
• Priority chain boundaries now reconcile cleanly, including:
  • hardhat_local
  • base_sepolia
  • ethereum_sepolia
  • solana_localnet
  • solana_devnet