whazaa 0.6.42 → 0.6.44

package/dist/index.d.ts

@@ -1,28 +1,50 @@
 #!/usr/bin/env node
 /**
- * index.ts — Whazaa MCP server entry point
+ * Whazaa MCP server — entry point and tool registrations.
  *
- * Exposes tools over the Model Context Protocol (stdio transport):
+ * This file is the executable that Claude Code (or any MCP host) launches to
+ * use Whazaa. It serves three distinct roles depending on the command-line
+ * argument supplied:
  *
- *   whatsapp_status   — Report connection state and phone number
- *   whatsapp_send     — Send a message to your own WhatsApp number (with optional TTS voice)
- *   whatsapp_tts      — Convert text to speech and send as a WhatsApp voice note
- *   whatsapp_receive  — Drain queued incoming messages from your phone
- *   whatsapp_wait     — Long-poll for the next incoming message
- *   whatsapp_login    — Trigger a new QR pairing flow
- *   whatsapp_rename   — Rename this Claude session (tab title + registry)
+ *   - **MCP server mode** (default, no argument): Registers all WhatsApp tools
+ *     over the stdio JSON-RPC transport and begins forwarding calls to the
+ *     watcher daemon via IPC.
+ *   - **Setup mode** (`setup`): Runs the interactive setup wizard from
+ *     `setup.ts` (writes MCP config, installs the /name skill, pairs WhatsApp).
+ *   - **Uninstall mode** (`uninstall`): Removes Whazaa config and credentials.
+ *   - **Watcher mode** (`watch [sessionId]`): Starts the long-running watcher
+ *     daemon that owns the Baileys WebSocket connection.
  *
- * Architecture: The MCP server is a thin IPC proxy. All WhatsApp operations
- * are forwarded to the watcher daemon (watch.ts) over a Unix Domain Socket
- * at /tmp/whazaa-watcher.sock. The watcher is the sole owner of the Baileys
- * connection. If the watcher is not running, tools return a clear error.
+ * ### Architecture: thin IPC proxy
+ * The MCP server itself holds no WhatsApp state. Every tool call is forwarded
+ * via a Unix Domain Socket (`/tmp/whazaa-watcher.sock`) to the watcher
+ * daemon (`watch.ts`). The watcher is the sole owner of the Baileys connection
+ * and fan-out message queues. This design means multiple Claude Code tabs can
+ * share a single WhatsApp session without conflict.
  *
- * CRITICAL: stdout is the MCP JSON-RPC transport.
- *   - NEVER write non-JSON to stdout.
- *   - All debug output, QR codes, and logs go to stderr.
+ * ### Tools registered
+ * | Tool name              | Purpose                                                  |
+ * |------------------------|----------------------------------------------------------|
+ * | `whatsapp_status`      | Report connection state and logged-in phone number       |
+ * | `whatsapp_send`        | Send a text or TTS voice note to self or any contact     |
+ * | `whatsapp_tts`         | Convert text to a Kokoro voice note and send it          |
+ * | `whatsapp_send_file`   | Send a file (PDF, image, video, etc.) via WhatsApp       |
+ * | `whatsapp_receive`     | Drain the queued incoming messages for this session      |
+ * | `whatsapp_contacts`    | List recently seen contacts, with optional search        |
+ * | `whatsapp_chats`       | List chat conversations (Desktop DB or Baileys fallback) |
+ * | `whatsapp_wait`        | Long-poll for the next incoming message                  |
+ * | `whatsapp_login`       | Trigger a new QR pairing flow                            |
+ * | `whatsapp_history`     | Fetch message history for a chat                         |
+ * | `whatsapp_voice_config`| Get or set TTS voice mode configuration                  |
+ * | `whatsapp_speak`       | Speak text aloud through the Mac's local speakers        |
+ * | `whatsapp_rename`      | Rename this Claude session (tab title + registry)        |
+ * | `whatsapp_restart`     | Restart the launchd-managed watcher service              |
+ * | `whatsapp_discover`    | Re-scan iTerm2 sessions and refresh the session registry |
  *
- * SETUP MODE: When invoked with "setup" argument, runs an interactive setup
- * wizard. In setup mode stdout is the terminal — console.log is safe.
+ * ### stdout constraint
+ * In MCP server mode, **stdout is the JSON-RPC transport**. Never write
+ * anything other than well-formed MCP JSON to stdout. All debug output,
+ * QR codes, and log lines must go to stderr.
  */
 export {};
 //# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8CG"}