feat(erc8004): publish registration-v1 metadata

[DamirAGI]

Summary

• publish AGIRAILS Markdown and ERC-8004 registration-v1 JSON as separate artifacts
• pass only the registration JSON CID to ERC-8004 identity registration
• version pending-publish state and skip ERC-8004 registration for legacy state instead of reusing a Markdown CID
• add validated registration projection, read-only identity inventory, and migration-plan CLI/API surfaces
• export the new consumer APIs from the package root and document the workflow

Safety properties

• payment routing remains bound to the verified on-chain ERC-8004 agentWallet
• the migration tooling has no signer, transaction executor, upload side effect, or automatic approval
• initial metadata does not predict a token ID; post-mint identity binding remains a separately reviewed setAgentURI step
• unsupported A2A, MCP, x402, and trust capabilities are not advertised
• x402Support stays false

Validation

• replayed onto main at 040c97b83b924036c078cc4e64c1998c1e5200fd; final head f793dca75a259812abf171aec00837836256443e
• git range-diff reports all four replayed commits as patch-identical to the independently validated source series
• full SDK suite: 137/137 suites passed, 3,287 passed, 1 skipped, 0 failures
• build: passed
• lint: 0 errors, 16 pre-existing warnings in unrelated files
• packed-artifact dry-run at the pre-CodeQL-remediation head includes the ERC-8004 CLI, registration, inventory, migration modules, root exports, and documentation; the final follow-up changes only gateway normalization and its regression test
• companion publish proxy: 26/26 tests and typecheck passed at 5494f8762ac9912d24d3f666759fcb81b9d98458
• git diff --check: passed

Companion proxy branch: agirails/publish-proxy:feat/erc8004-registration-v1. The proxy change must be deployed before clients use the new artifact type.

No live RPC/fork/testnet, pinning mutation, identity migration, deployment, or npm release was performed.