- `claude_inbox.py`: posting to Claude's inbox is fire-and-forget, because the socket replies with nothing. Claude can send a `peer_message_status` receipt (delivered/held/refused) to a sender's `uds:` reply address, but the format was found only in the bundle and isn't documented. If it becomes documented, bind a temporary reply socket so `spawn message` can report "held for approval" or "refused" instead of just "posted".
- `projections/project_opencode_subprocess.py`: an OpenCode 2 black-box fallback that
  resumes a session committed to another agent gets no Meridian prompt, because the v2
  bare TUI rejects `--agent`. Fresh fallback sessions take `default_agent`. To close it,
  run a private `opencode serve`, call `POST /api/session/{id}/agent`, then attach the
  TUI with `--server`; or use a `--agent` flag if a later v2 adds one.
- OpenCode 2 has no effort channel that reaches the request: config parses
  `provider/model#variant` and agent `model.variant`, but probes saw no reasoning field
  in provider requests. TUI and streaming launches now report the field unsupported;
  revisit when upstream wires variants through.
- Per-launch MCP server injection needs a launch-bundle field containing server
  definitions. `tools.mcp` cannot supply it: that compatibility field contains
  harness-native permission names derived from `tools.rules`, while Mars installs
  package `mcp/<name>/mcp.toml` definitions during sync. OpenCode config can carry local
  definitions under `mcp.servers`, but Meridian must not reconstruct commands from tool
  permission names.

- `control_action.py`: every journal row in `control_actions.jsonl` repeats the full message text, so a large message (up to the 16 MiB socket limit) costs three durable writes, each fsynced. Keeping the text on the `requested` row alone, with later rows referring to it by action id, would cut that to one.
