Document chat provider integrations (codex)

[numnx]

🧩 Task: Document chat provider integrations

Automated task PR opened by Code UX for T07.

📋 Summary

Sprint: Sprint 162 · Integrate Chat Connections · Task: T07

Integrate configurable external chat providers under Settings -> Providers so WhatsApp, iMessage, Telegram, Slack, Microsoft Teams, and Discord can be securely connected to project-manager chat flows, managed through dashboard and MCP APIs, linked flexibly across projects/channels, and routed through the existing chat reply runtime with external-channel-safe replies that suppress dashboard-only rich widgets.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 08:01:22 UTC
Finished	2026-07-07 08:03:08 UTC
Duration	1m 46s

📊 Token Usage

Metric	Value
Input tokens	150,193
Cached input tokens	2,732,672
Output tokens	14,690
Total tokens	2,897,555
Invocations	2
Tool calls	64
Active time	6m 26s

Included usage estimate (subscription/local login): $2.56

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Document the external chat provider integration behavior, setup model, security requirements, routing rules, MCP management actions, outbound delivery behavior, and dashboard-widget suppression for external channels.

## Scope
- Create `docs/settings/chat-provider-integrations.md`
- Edit `docs/index.md`
- Edit `docs/SUMMARY.md`
- Edit `docs/settings/subcategories/provider-integration.md`
- Edit `docs/architecture/chat-thread-runtime.md`
- Edit `docs/mcp/tools-and-contracts.md`
- Mirror public docs in `docs-web/user/providers-and-models.md`, `docs-web/developer/mcp-tools.md`, and matching `docs-web/content/docs/*.mdx` pages as needed
- Consumes behavior delivered by T03, T05, and T06

## Implementation Requirements
1. Add a dedicated chat provider integrations page covering supported providers, OpenClaw/webhook/native bridge modes, credential handling, webhook signatures or bridge tokens, channel binding, project routing, same-channel multi-project ambiguity handling, outbound replies, retry/failure visibility, and rich-widget suppression.
2. Link the new page from `docs/index.md` and `docs/SUMMARY.md` under settings/integrations.
3. Update provider integration docs to explain that AI provider credentials and chat provider connections both live under Settings -> Providers but use separate runtime paths.
4. Update chat runtime architecture docs to describe external chat metadata, authenticated ingress, idempotency, existing conversation-thread reuse, outbound delivery records, and why dashboard-only widgets are suppressed outside the dashboard.
5. Update MCP tool docs with the new chat provider management actions, approval behavior, redaction rules, delivery-state inspection, and example payloads using generic project/channel labels.
6. Mirror the user/developer-facing changes into `docs-web/` content consistently with existing published docs structure.

## Constraints
- Do not claim direct official API integration for any provider beyond the implemented OpenClaw, webhook, or native bridge contracts.
- Do not mention real customer or live project names.
- Do not claim validation checks passed unless the worker ran them.
- Keep docs outcome-focused and aligned with final code behavior from dependency tasks.

## Verification
- Run `pnpm run check:docs-web`.
- Run `pnpm run lint`.
- Success means canonical docs and published docs describe the implemented setup, security, routing, management, and delivery behavior without overstating provider capabilities.

🌿 Branch Info

Base: feature/CODUX-162-integrate-chat-connections
Head: task/feature-codux-162-integrate-chat-connections-t07-codex-mractfsg

---

🤖 Generated by Code UX