feat(channels): WhatsApp concierge channel (shared number + phone routing)

[vibegui]

Summary

Adds WhatsApp as a third channel, stacked on the Teams/Discord channels PR (#3749 — this PR's base is vibegui/org-chat-integration, so the diff is WhatsApp-only). Merge #3749 first.

Unlike the per-org Teams/Discord bots, WhatsApp uses one shared decoCMS concierge number. A user verifies their phone once in their profile; inbound messages route by phone → user → org and the org's agent answers as that real user.

How it works

• Verification (inbound-only): Studio issues a code shown in the user's profile; the user texts it to the concierge number; that inbound proves ownership and links the number. No phone typing, no Studio→worker send for verification.
• Routing: global POST /api/whatsapp/ingest (shared-secret auth, async) — verify code → resolve phone→user → pick the target org (saved default + in-chat numbered pick-list / switch) → run the agent as the real user → reply via the worker's /send.
• Identity: one verified phone → one Studio user, across all their orgs.
• Enable-only channel: no per-org credentials/bot — CHANNELS_LIST advertises WhatsApp (setupKind: "shared"), CHANNEL_CREATE activates immediately with a chosen agent. Only available when WHATSAPP_WORKER_URL/TOKEN, WHATSAPP_INGEST_SECRET, WHATSAPP_CONCIERGE_NUMBER are set.
• The deployed Cloudflare worker (mangabeira) stays the WABA owner and becomes a thin relay — integration prompt in .context/whatsapp-worker-integration-prompt.md.

Key pieces

• migration 110-user-phones; 109-channels.bot_user_id made nullable
• UserPhoneStorage + phone canonicalization; whatsapp-worker client; whatsapp-ingest route
• runChannelTurn generalized (botUserId→userId) so the real user can answer
• profile tools PHONE_LINK_START / PHONE_GET / PHONE_DELETE (basic-usage)
• profile "Link WhatsApp" UI + "Add WhatsApp" enable dialog

Testing

• bun run check / lint / fmt:check / knip clean; build:server ok.
• Unit tests: org-selection resolver + phone canonicalization (+ existing channel adapter tests).
• Manual: curl the ingest endpoint with a mock worker /send, or wire the real worker per the prompt. Run bun run --cwd=apps/mesh migrate first.

🤖 Generated with Claude Code

---

Summary by cubic

Adds WhatsApp as a shared-number concierge channel. Members link their phone once; inbound messages route phone → user → org, and the agent runs as the real user.

• New Features

  • Global ingest endpoint with secret auth; verifies one-time codes, resolves phone → user → org (remembered org, number pick-list, or switch).
  • Runs agent turns as the real user (runChannelTurn now uses userId) and replies via the WhatsApp worker /send.
  • Enable-only channel: listed when configured, created without a bot or credentials, activates immediately with a chosen agent.
  • Profile tools and UI for phone linking: PHONE_LINK_START, PHONE_GET, PHONE_DELETE; “Link WhatsApp” in profile with live polling.
  • Settings UI: “Enable WhatsApp” dialog to pick the answering agent.
  • Storage and utils: UserPhoneStorage, phone canonicalization/masking, and unit tests for org selection and phone utils.

• Migration

  • DB: new user_phones table; channels.bot_user_id is nullable for WhatsApp.
  • Config: set WHATSAPP_WORKER_URL, WHATSAPP_WORKER_TOKEN, WHATSAPP_INGEST_SECRET, WHATSAPP_CONCIERGE_NUMBER.
  • Deploy/enable the WhatsApp worker, then run migrations and enable WhatsApp per org by selecting an agent. Members link their phone from their profile.

^{Written for commit 6dfad87. Summary will update on new commits.}

[vibegui]

Superseded by #3850 — WhatsApp is now based off main (standalone), not stacked on the Teams/Discord channels PR.