Deferred: WhatsApp template with Channels, Meta, and Auth0

[jerelvelarde]

WhatsApp is deferred until after the three active templates — Slack, web, and React Native — are stable. Keep this PR in draft and preserve jerel/whatsapp-channels-meta so implementation can resume later. Do not merge it as part of the active starter cleanup.

PR #13 removes the WhatsApp example from the active starter. This draft retains its app, setup guides, screenshots, and prior verification work. It currently retains its historical base on #7; reconcile it with main when WhatsApp work resumes.

The live demo server and public tunnel have been stopped, and the demo app has been unsubscribed from the WhatsApp account. External Meta/Auth0 accounts are retained. Historical validation below records the earlier setup state; it does not mean those services are still running. Remaining work includes verified identity linking, phone approval, and saving an approved request end to end before reintroduction.

---

Run the WhatsApp template through CopilotKit Channels and Meta's direct Cloud API, with OpenAI Agents SDK planning and Auth0 Guardian approval before saving the exact named request. All three template guides now offer OpenAI directly or OpenRouter, with copy-paste model settings and the correct environment-file location.

WhatsApp uses an explicit Responses model for OpenAI or Chat Completions for OpenRouter. The router path requires strict structured-output support, validates proposals locally, and keeps credentials and inherited OpenAI headers isolated. A missing selected key or invalid provider response fails without switching providers. The Auth0 approval and persistent-record boundaries stay in place.

The homepage, coding-agent instructions, sponsor setup, and WhatsApp walkthrough describe the same stack. Five Auth0 screenshots with a 20-second GIF, three Meta onboarding screenshots with a 12-second GIF, and a messages-subscription screenshot document configuration. The original GIFs show earlier setup stages. The recipient is now verified, the runtime and public tunnel report healthy, and Meta has verified the callback. Meta confirmed delivery of one Hello World message to the test phone. Live setup also exposed a missing account-level subscription: the messages field was enabled, but the WhatsApp account only subscribed Meta’s test viewer. The app is now subscribed to the WhatsApp account, verified by a subsequent read, and both setup guides explain that separate step. A real inbound Hi has now been processed by the Channels app; its sign-in reply is marked sent and the user confirmed receiving it. Sender linking, Guardian enrollment/approval, and a saved receipt remain unverified. Meta warns that unpublished apps cannot receive production webhook data; the verified test recipient has nevertheless completed this one inbound greeting and reply while the app remains unpublished. No authenticated OpenRouter journey has been recorded.

Stacked on #7 (jerel/template-readiness). Keep this PR draft until live phone verification is complete.

Validation:

• Clean installs, all five root workspace typechecks, 99 root/Slack/web tests, and the real local MCP stdio roundtrip passed.
• WhatsApp typecheck and all 48 tests passed, using the actual Channels/Meta runtime and Agents SDK with local Intelligence, Graph, Auth0, Responses, and Chat Completions services. Coverage includes provider/key/header isolation, strict schema, malformed output, API errors, identity/approval checks, persistence, and exact rendered consent text.
• Web production build passed with the existing transitive Google Vertex dynamic-dependency warning. No app formatter/lint/build target is configured; WhatsApp tests execute the real tsx runtime.
• Independent spec and final code review passed. Relative links and anchors, added official OpenRouter links, manifest/lockfile consistency, and diff hygiene were checked. No resolved dependency version changed for the OpenRouter addition.
• Latest update changes only the WhatsApp app README, walkthrough, and a messages-subscription screenshot. App typecheck, local links/anchors, and diff/privacy review pass. The new screenshot contains the Meta header/avatar and subscription rows, with no credentials, verification codes, or recipient number. Existing GIF frames were previously inspected and remain unchanged. No application source changed.

Operational limits: the direct SDK acknowledges before app persistence; its internal listener must stay private; the JSON store supports one process. Old Twilio state and changed business numbers are refused without overwriting data and require a fresh data file plus relinking. Changing only the model provider does not require relinking. App-scoped legacy-peer-deps handles unused legacy connector conflicts; eight transitive audit findings remain (seven moderate, one high).

Step-by-step WhatsApp screenshot guide · Model-provider setup for all templates

[jerelvelarde]

Preserved unchanged as a draft in Jerel’s personal repository: jerelvelarde/agents-everywhere-starter-kit#1. Both the implementation head (e248bde) and historical base (b677af2) are retained there. Closing this upstream draft to keep the active hackathon starter focused on Slack, web, and React Native. WhatsApp remains deferred with its outstanding live verification documented in the new draft.