#20700: docs: add real-world setups and use cases guide

## Summary Adds a new "Real-World Setups" page under `docs/examples/` showcasing practical production OpenClaw deployments: - **Personal AI Chief of Staff** — multi-channel + voice + Google Workspace - **Business Lead Capture Agent** — landing page + CRM pipeline + Discord alerts - **Multi-Channel Family Hub** — Raspberry Pi + WhatsApp + calendar coordination - **Developer Productivity Agent** — GitHub + browser relay + CI monitoring - **Trading Scanner** — exchange APIs + technical analysis + alerts Includes architecture diagrams, cron configuration examples, and operational tips. ## Why The existing docs cover features and configuration well, but there is no page showing what complete production setups look like. New users often ask "what can I actually build with this?" — this page answers that with real examples. ## AI Disclosure - [x] AI-assisted (drafted with Claude, validated against real production setups) - [x] Based on real-world deployments - [x] I understand what the content covers Happy to revise based on feedback! <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a valuable new documentation page showcasing five real-world production OpenClaw deployments with practical examples of architectures, configurations, and operational tips. **Changes:** - New `docs/examples/real-world-setups.md` with comprehensive use cases covering personal AI assistants, business automation, family coordination, developer productivity, and trading/market monitoring - Includes concrete `openclaw cron` command examples with proper syntax - Features architecture diagrams and best practices from production deployments - Follows existing documentation style and frontmatter patterns **Issue found:** - The new file is not registered in `docs.json` navigation structure, so it won't be accessible on the documentation website The content is well-written, technically accurate, and addresses a genuine documentation gap by showing users what complete production setups look like. All CLI commands use correct syntax matching existing documentation patterns. The examples reference valid OpenClaw features (cron, heartbeat, channels, models) that are properly documented elsewhere in the codebase. <h3>Confidence Score: 4/5</h3> - Safe to merge after addressing the navigation registration issue - The content is well-written, technically accurate, and fills a documentation gap. All CLI commands use correct syntax verified against existing docs. The only issue is that the page won't be accessible on the docs site without adding it to the navigation structure in docs.json. This is a straightforward fix that doesn't affect the quality of the content itself. - The navigation config `docs.json` needs updating to include the new page _{Last reviewed commit: d54c68d} <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->