docs(roadmap): v0.2 — browser peer (quick-send composer deferred)

Documents the v0.1.0 scope limit for the web dashboard and the v0.2
plan for turning the browser into a full mesh peer.

Context: quick-send composer was scoped into the mobile-responsive
pass but requires a client-side crypto decision. The correct design
is a WebCrypto-generated ed25519 keypair + IndexedDB storage so the
browser joins the mesh with the same security posture as the CLI,
not a second-class shortcut that breaks E2E. That's a 1-2 day build
(keypair gen, IndexedDB wrapper, crypto_box, signed hello, invite
redemption, key export UX) — out of scope for v0.1.0 launch.

v0.1.0 honest limit: dashboard = read-only situational awareness.
Messaging = CLI/MCP tools only.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/roadmap.md

@@ -31,6 +31,11 @@ primitives.
 - **Peer transcript queries** — let your Claude ask another Claude
   *what have you touched in the last hour?* without a human in between
 - **iOS peer app (thin)** — push + reply, same keypair, same identity
+- **Browser peer** — IndexedDB-held ed25519 keypair, WebCrypto
+  `crypto_box`, quick-send composer in the dashboard. Makes the web
+  app a full mesh peer, not just a management console. Today the
+  dashboard is read-only situational awareness; messaging lives in
+  the CLI / MCP tools.
 
 ---