Align v19 CLI and MCP capability vocabulary

[flyingrobots]

Parent: #712
Blocked by: Runtime fork/settlement and generated SDK slices

Outcome

CLI and MCP expose the same v19 Runtime/Lane/Intent/Observer/Observation/Reading/Receipt/Settlement vocabulary and canonical machine envelopes.

Acceptance

• CLI supports the accepted command families: write, observe, fork, settlement preview/apply, receipt show, doctor, repair, and audit.
• MCP supports the accepted capability families without graph-first query tool names.
• Each operation opens/closes local Runtime resources internally.
• Human output shares the canonical Reading/Receipt renderer.
• JSON/JSONL and MCP envelopes use Reading.value and canonical Receipt fields.
• MCP batches/cursors remain transport details rather than public domain nouns.
• Help, tool descriptions, schemas, fixtures, and executable tests agree.
• Removed graph/session/OID/cache vocabulary is absent outside explicit migration/substrate diagnostics.

Non-goals

WARP DRIVE, offline bundles, and compatibility aliases.

[coderabbitai]

🔗 Related PRs

#726 - Move graph exports behind v19 public API boundary [merged]
#733 - Enforce the v19 public API contract [merged]
#745 - Seal Git substrate out of v19 receipts and evidence [merged]
#768 - Classify v19 writes with admission outcomes [merged]
#769 - feat(api): establish the v19 Runtime and Lane surface [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!