wa-satellite — WhatsApp backbone API (LIVE)

Send + receive + attachments over WhatsApp. Backbone: this Worker -> Cloudflare
tunnel -> OpenWA gateway (Azure) -> proxy -> WhatsApp.

HOOK POINT
  Base: https://wa-satellite.catalin-932.workers.dev
  Auth: Authorization: Bearer <client token>   (backbone owner mints it: POST /admin/clients)
  Same-account Worker -> call via SERVICE BINDING (public fetch = error 1042). Off-account -> HTTPS.

ENDPOINTS
  POST /v1/whatsapp/outbox   {messages:[{to,text}]}                 send (recipient = to; paced plan)
  POST /v1/threads/<id>/reply {text | file:{name,type,content}}     reply in a conversation
  GET  /v1/threads?lane=whatsapp                                    list conversations
  GET  /v1/threads/<id>                                             conversation + messages (+assistant read)
  GET  /v1/threads/<id>/files/<fid>                                 download an attachment
  POST /v1/whatsapp ; POST /v1/whatsapp/<n>/pair|qr|connect         add + link numbers
  /v1/campaigns ; /v1/people ; /v1/companies ; /v1/tasks            cross-channel campaigns

PENDING (backbone builds on request)
  - outbound webhooks (push inbound + receipts; today: poll GET /v1/threads)
  - media in outbox (attachments as a first message)
  - sender pinning (only when a client has >1 number)

NOT BACKBONE (your side): UI/CRM, campaign UX, consent/STOP handling.