[v1] Scope freeze: reposition repo as toolkit, not node

[SMC17]

Problem
The v1 release needs this work to make the toolkit claim defensible.

Scope

• Reposition the repo and release language around toolkit scope only.
• Add an explicit supported/unsupported surface table.
• Remove or demote any wording that implies v1 validator/node readiness.

Files

• README.md
• PROJECT_STATUS.md
• ARCHITECTURE.md
• docs/ROADMAP.md
• docs/ROADMAP_TO_PARITY.md

Gates

• Supports Gates A/B/C/D/E

Acceptance Criteria

• Top-level docs define v1 as codec/signing/conformance toolkit scope.
• Supported and unsupported surfaces are explicit.
• PROJECT_STATUS.md contains the exact v1 release claim.

Related

• Epic: [Epic] v1 XRPL Toolkit release #45
• Milestone: v1 XRPL Toolkit

[SMC17]

Started in working tree:

• rewrote canonical release docs around the toolkit-first v1 target
• updated secondary docs (docs/AGENT_RUNBOOK.md, docs/SOURCE_OF_TRUTH.md, docs/status/AGENT_NATIVE_BACKLOG.md) to make research tracks explicitly non-v1
• changed local runtime/example wording away from daemon/node framing in src/main.zig and examples/ledger_consensus.zig

Remaining work is broader example/doc cleanup and any public API renames needed to finish the scope freeze.

[SMC17]

Progress update:

• swept more user-facing examples/docs away from node-era framing:
  • examples/simple_payment.zig now demonstrates canonical serialization explicitly
  • examples/http_server_demo.zig and examples/network_demo.zig are marked experimental and outside the v1 release promise
  • docs/AGENT_CAPABILITY_MATRIX.md now refers to the local runtime instead of starting a node
• current remaining rg hits for daemon/node on the user-facing path are limited to issue-title references like demo-node in execution tracking, not product docs/examples themselves

Verification:

• wording sweep rechecked with rg -n "Run node|Start node|daemon|demo-node" docs examples README.md GETTING_STARTED.md src/main.zig