[Asaf-prog]

Adds an opt-in WhatsApp Cloud API channel for one organization-owned number, following the integration plan (WA-01 to WA-05).

Stacked on #148. The base is codex/fix-140-cancelled-token-budget, so this diff shows only the WhatsApp work. GitHub retargets it to main when #148 merges.

Commits

1. test(manager): close SQL engines owned by repository tests. Fixes intermittent aiosqlite worker-thread exceptions in the full gate (task 0018).
2. feat(manager): prepare conversation turns idempotently. An opt-in idempotency key claims a durable receipt with the user message, so a retried preparation recovers the same turn. Migration 0007, ADR 0006.
3. feat(manager): add durable channel storage. Provider-independent inbox, sender bindings, execution claims, webhook receipts, ordered outbox and delivery events, worker ownership, and the channel identity port. Migrations 0008–0010.
4. feat(manager): connect WhatsApp webhook, worker, and delivery. Authenticated webhook intake, a supervised turn worker with conservative recovery, provider delivery with text controls, and /health returning 503 when the worker has stopped. Adds the regex dependency (used by text rendering).
5. docs. ADRs 0007–0010, tasks, and review records.

Rollout

Everything is off by default. Three flags turn it on in order, and settings validation rejects a flag without its prerequisites:

• EXTRA_WHATSAPP_ENABLED: webhook intake.
• EXTRA_WHATSAPP_WORKER_ENABLED: turn worker. Requires intake, an organization id, and an identity resolver plugin.
• EXTRA_WHATSAPP_SENDER_ENABLED: outbound delivery. Requires the worker.

No real account or number has been activated yet. Customer Google/JWT account linking and pilot packaging remain planned.

Validation

• make check passes on the final commit: 1423 tests, plus ruff and mypy.
• Every intermediate commit was checked in a separate worktree for tests, ruff, and mypy: 1126, 1159, 1174, and 1423 tests pass.
• Migrations 0007–0010 need to run on deploy.

🤖 Generated with Claude Code