1.9 KiB
Phase 6 Placeholder Audit
Updated: 2026-06-06T04:15:19Z
Commands
rg -n "chatwootParityStub" internal/handler internal/service internal/router internal/channel
rg -n "chatwootParityStub" internal/router/router.go | wc -l
scripts/parity_frontend_smoke.sh --check
Result
chatwootParityStub appears only in internal/router/router.go: 20 call sites plus the helper definition.
All call sites are nil-handler guards for public webhook registration paths:
- Telegram webhook callback.
- WhatsApp verify and event callbacks.
- TikTok verify and event callbacks.
- LINE event callback.
- Twilio SMS, delivery status, and root callback aliases.
- Twitter CRC and event callbacks, including legacy aliases.
- Instagram verify and event callbacks.
- Shopify webhook callback.
No chatwootParityStub call site is registered on the reused dashboard account/contact/conversation/message/inbox API path, widget API path, public help-center path, public inbox/contact/conversation/message API path, or enterprise settings API path.
Classification
The remaining stubs are defensive nil-handler fallbacks. In normal app bootstrap the matching provider handlers are wired and these branches do not define the route behavior. Provider-specific webhook behavior remains owned by the existing webhook/channel parity slices and future B12 or provider fixture failures.
Phase 6 is therefore in Review for the inspected placeholder surface. Reopen it only if a fresh rg audit or reused frontend smoke identifies a frontend-reachable chatwootParityStub, not implemented, or placeholder success response in account/contact/conversation/message/inbox/widget/public critical paths.
B12 Readiness
scripts/parity_frontend_smoke.sh --check passed and refreshed docs/parity/frontend_smoke_report.md. Live API/browser/enterprise smoke remains pending because it requires the full PostgreSQL, Redis, Meilisearch, GoChat, Vite, and Chrome stack.