docs: clarify managed ClawBox messaging channels

[yalexx]

Summary

• Clarify Telegram and web chat as managed ClawBox messaging paths
• Reframe WhatsApp, Discord, Slack, Signal, Matrix, Teams, Google Chat, and iMessage as advanced OpenClaw extension paths
• Update quickstart, first boot, hardware, messaging channel, and FAQ docs

Validation

• mint validate
• mint broken-links
• git diff --check

Summary by CodeRabbit

• Documentation
  • Updated the messaging channels guide to center on managed Telegram and on-device web chat, with other channels presented as advanced/only-if-supported options.
  • Revised setup and quickstart pairing/linking steps to focus on Telegram flows, and shortened group chat guidance.
  • Added/updated troubleshooting guidance and clarified advanced channel support notes across the FAQ, requirements, homepage, and ClawBox Connect materials.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5ce04601-c437-4c5d-b352-62491bf074e9

📥 Commits

Reviewing files that changed from the base of the PR and between b76e76e and 25cb9f2.

📒 Files selected for processing (1)

• docs-site/setup/openclaw-setup.mdx

---

📝 Walkthrough

Walkthrough

Documentation across the docs site was updated to position Telegram and on-device web chat as the managed messaging paths. Guide, hardware, homepage, quickstart, setup, and FAQ content were revised to treat other OpenClaw channels as optional advanced extensions.

Changes

Messaging Channels Documentation Update

Layer / File(s)	Summary
Messaging channels guide rewrite docs-site/guides/messaging-channels.mdx	Supported channels were narrowed to Telegram and Web Chat, linking instructions were rewritten to a Telegram-specific pairing flow, and group chat guidance was condensed.
Hardware pages messaging capability descriptions docs-site/hardware/clawbox-connect.mdx, docs-site/hardware/requirements.mdx	Messaging capability bullets were updated to reference Telegram/web messaging and optional additional OpenClaw channels.
Homepage and quickstart messaging copy docs-site/index.mdx, docs-site/quickstart.mdx	Hero, feature bullets, and quickstart steps were updated to emphasize Telegram and web chat as the default channels, with advanced channels mentioned as optional.
Setup and FAQ guidance updates docs-site/setup/first-boot.mdx, docs-site/setup/openclaw-setup.mdx, docs-site/support/faq.mdx	Pairing steps, setup notes, and the FAQ answer were updated to describe Telegram as the guided setup path and other chat apps as conditional advanced options.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• ID-Robots/clawbox#229: Also edits docs-site/guides/messaging-channels.mdx, with overlapping documentation structure changes on the same page.

Suggested reviewers: KrasimirKralev, GeorgiK77

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers summary and validation, but it omits required template sections like type of change, testing details, checklist, and screenshots/logs.	Add the missing template sections: type of change, how it was tested, checklist items, and screenshots/logs if applicable.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main documentation change about managed ClawBox messaging channels.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/channel-support-audit-2026-07-09

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed: dependency version conflict. Check your lock file or package.json.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

CI Summary

✅ Tests

• Result: passed
• View run
• Coverage: statements 69.6%, branches 59.51%, functions 64.85%, lines 71.59%

✅ E2E

• Result: passed
• View run

✅ E2E Install

• Result: success
• View run

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs-site/setup/openclaw-setup.mdx`:
- Around line 37-41: The Telegram setup section should mirror the new guidance
used for Discord by pointing users to ClawBox’s guided Telegram flow instead of
only showing manual OpenClaw config steps. Update the Telegram note/content in
openclaw-setup.mdx alongside the existing Telegram setup instructions so it
references the managed path described in
docs-site/guides/messaging-channels.mdx, and keep the manual configuration
guidance only as a fallback for unsupported versions or plugins.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5e713e91-a015-4be5-993c-dd68c1074504

📥 Commits

Reviewing files that changed from the base of the PR and between 111446c and b76e76e.

📒 Files selected for processing (8)

• docs-site/guides/messaging-channels.mdx
• docs-site/hardware/clawbox-connect.mdx
• docs-site/hardware/requirements.mdx
• docs-site/index.mdx
• docs-site/quickstart.mdx
• docs-site/setup/first-boot.mdx
• docs-site/setup/openclaw-setup.mdx
• docs-site/support/faq.mdx