id: write the Phase 13 plan: client shells and client capability providers #564

What and why

Write a Phase 13 plan after Phase 12, with F12.7 (ABI conformance), F12.14 (portals) and F12.12 (many worlds) as stepping stones, to hold D1-050..D1-056. The client-side and transport ideas from the platform reports have no plan to live in; Phase 12 stops short of them.

Source

• RPT §15 'Placement'

RPT = doc/2026-10-18T18-40-00Z_report_platform_world_state/2026-10-18T18-40-00Z_report_platform_world_state.md, REF = doc/2026-10-18T00-00-00Z_reference_platform_state/2026-10-18T00-00-00Z_reference_platform_state.md. Both are uncommitted reports in the platform-world-apps-migration worktree.

Current status

Not started. ls .opencode/plans has phase-9, phase-11, phase-12 and the 2026-10-20 status only; git grep -i 'phase 13' origin/main finds nothing.

Acceptance criteria

• .opencode/plans/phase-13-*.md is committed
• It holds D1-050..D1-056 (SSH frame transport, SSH-over-iroh, native shells, client capabilities, multi-server topology) and names F12.7, F12.14 and F12.12 as stepping stones
• Each task has an exit criterion in the Phase 11/12 style

Size

S

Prerequisites

• id: Phase 12 designs to run through the research workflow #534 (tracking issue) — D1-025 F12.7 Versioned guest ABI spec, plaza_abi_version export, conformance suite