docs: update pairing docs with SQLite persistence and TUI execution details

README.md

@@ -30,7 +30,7 @@ Self-hosted personal AI assistant with Telegram and Terminal interfaces.
 - **Skills System**: Extensible capability packages (bundled, managed, workspace tiers)
 - **Gateway Lock**: Single-client mode — reject additional WebSocket connections when one is active
 - **Tailscale Serve**: Auto-expose gateway via Tailscale Serve on daemon start with lifecycle management
-- **DM Pairing Codes**: Allow unknown senders to pair with the bot via time-limited codes across all channels
+- **DM Pairing Codes**: Allow unknown senders to pair with the bot via time-limited codes across all channels, with SQLite-backed persistence across restarts
 - **Lane Queue**: Per-session FIFO queue serializes concurrent gateway requests
 
 ## Quick Start
@@ -505,7 +505,7 @@ pairing:
 1. Generate a code via the TUI (`/pair generate`), gateway API (`pairing.generate`), or web dashboard
 2. Share the code with the user
 3. The user sends the code as their first DM to the bot
-4. If valid, the user's sender ID is permanently approved for that channel
+4. If valid, the user's sender ID is permanently approved for that channel (persisted in SQLite, survives daemon restarts)
 5. Approved users can be listed (`/pair list`) and revoked (`/pair revoke <channel> <id>`)
 
 ### TUI Commands