feat: add iMessage channel, channels setup guide, 3-way distinction

- messaging/channels-setup.md: comprehensive guide covering all 3
  channels (Telegram, Discord, iMessage), bun install, plugin setup,
  session persistence workarounds, and enterprise admin settings
- messaging/imessage-setup.md: macOS-specific iMessage setup with
  Full Disk Access, /imessage access allow, and known quirks
- messaging/README.md: rewritten with 3-way distinction table
  (Channels=event-based, Dispatch=message-based, RC=direct control)
- examples/12: expanded from 2 options to 3 with clear trigger model
- feature-map.md: row 9 updated to include iMessage
- README.md: session persistence warning added as top-level section

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

messaging/README.md

@@ -2,44 +2,69 @@
 
 How Claude Code sends and receives messages, compared to OpenClaw.
 
-## OpenClaw: Native channel integrations
+## Three ways to reach Claude Code from your phone
 
-OpenClaw ships with 15+ channel connectors out of the box:
-Slack, Discord, Telegram, Email, SMS, WhatsApp, and others.
-Each is configured in a single YAML block. No additional setup.
+| Method | How it works | Best for |
+|--------|-------------|----------|
+| **Channels** | Chat apps push events into a running session | iMessage, Telegram, Discord |
+| **Dispatch** | Send a task from the Claude mobile app | Quick delegation |
+| **Remote Control** | Steer an active session from phone/browser | Guiding in-progress work |
 
-## Claude Code: MCP servers + native Telegram
+See `channels-setup.md` for the definitive guide to all three.
 
-Claude Code uses MCP servers for most messaging channels.
-Telegram is the exception: it has native support since v2.1.80.
+## Supported channels (native, event-based)
 
-### Native Telegram (no MCP needed)
+| Channel | Plugin | Platform | Since |
+|---------|--------|----------|-------|
+| Telegram | `@anthropic-ai/claude-code-telegram` | Any OS | v2.1.80 |
+| Discord | `@anthropic-ai/claude-code-discord` | Any OS | v2.1.80 |
+| iMessage | `@anthropic-ai/claude-code-imessage` | macOS only | v2.1.87 |
 
-Since v2.1.80, Claude Code has a Channels feature with Telegram support.
-Since v2.1.81, permission relay allows approving tool calls from your phone.
+All three follow the same pattern: install plugin, launch with
+`claude --channels`, receive and respond to messages.
 
-Install the Telegram plugin in Claude Code settings, connect your account,
-and Claude can send messages and wait for your approval before executing
-sensitive actions - from your phone, without opening a laptop.
+**Permission approval from phone:** When Claude needs to run a
+sensitive action, it sends a permission request through the
+channel. Reply "yes" or "no" from your phone.
 
-This is the closest to OpenClaw's native channel experience.
-See `telegram-channels-setup.md`.
+## MCP servers for other channels
 
-### MCP servers for other channels
+For channels not yet supported natively, use MCP servers:
 
-| Channel  | MCP Server                     | Notes                    |
-|----------|-------------------------------|--------------------------|
-| Slack    | `@modelcontextprotocol/slack` | Official MCP server      |
-| Discord  | Community MCP servers         | Search MCP registry      |
-| Email    | SMTP/IMAP MCP servers         | Several available        |
+| Channel | MCP Server | Notes |
+|---------|-----------|-------|
+| Slack | `@modelcontextprotocol/slack` | Official, well-maintained |
+| Email | SMTP/IMAP MCP servers | Several community options |
 
-The `.mcp.json` in this repo includes commented examples.
-See `slack-setup.md` for a complete walkthrough.
+See `slack-setup.md` for a complete Slack walkthrough.
 
-## Honest assessment
+## Setup guides in this directory
 
-OpenClaw is easier for multi-channel messaging: install once, configure in YAML,
-done. Claude Code requires setting up separate MCP servers per channel.
+| File | What it covers |
+|------|---------------|
+| `channels-setup.md` | General channels guide + Dispatch/RC comparison |
+| `imessage-setup.md` | iMessage-specific setup (macOS) |
+| `telegram-channels-setup.md` | Telegram-specific setup |
+| `slack-setup.md` | Slack via MCP server |
 
-For single-channel use (Telegram), Claude Code's native support is now comparable.
-For complex multi-channel workflows, OpenClaw has the advantage.
+## The critical limitation
+
+**If the Claude Code session closes, channels stop working.**
+This is the biggest practical difference from OpenClaw's
+always-on daemon. See `channels-setup.md` for workarounds
+(tmux, Mac Mini, VPS).
+
+## OpenClaw comparison
+
+OpenClaw ships with 15+ channel connectors: WhatsApp, Telegram,
+Discord, Slack, Signal, iMessage, IRC, Matrix, Teams, and more.
+Each is plug-and-play with YAML configuration.
+
+Claude Code has 3 native channels (Telegram, Discord, iMessage)
+plus MCP servers for Slack and others. The gap is narrowing but
+OpenClaw still has broader multi-channel coverage.
+
+Where Claude Code wins: security. OpenClaw's community skills
+(12% malicious per Cisco research) and CVE-2026-25253 highlight
+real risks. Claude Code's permission model and marketplace review
+process provide stronger guarantees for most users.