#17023: docs(feishu): add multi-agent troubleshooting guide

## Summary Add comprehensive troubleshooting sections for common multi-agent Feishu/Lark deployment issues. ## New Content ### 1. Gateway Device Token Mismatch - **Symptom**: - **Context**: A2A communication fails, tools return unauthorized errors - **Quick Fix**: - **Root Cause**: Gateway service cached stale device token ### 2. Agent Not Replying in Group Chats - **Symptom**: Agent replies in DMs and when @mentioned, but not when speaking directly in groups - **Context**: Multi-bot setups (e.g., main_bot + pulse_bot) - **Root Cause**: Missing `deliveryContext.to` field in sessions.json - **Fix**: Manually add `to: "chat:oc_xxx"` format fields - **Key Detail**: Group chats use `chat:` prefix, DMs use `user:` prefix ## Real-World Context This guide is based on actual deployment experience with a dual-bot Feishu setup where: - `main_bot` handles general queries - `pulse_bot` handles specialized tasks Both issues were encountered and resolved during production deployment. ## Checklist - [x] Added to existing troubleshooting section - [x] Includes diagnosis commands - [x] Includes copy-paste fixes - [x] Documents prevention tips - [x] Follows existing documentation style --- **Related**: This addresses gaps in multi-agent configuration docs that aren't covered by the existing [Multi-agent routing](#multi-agent-routing) section. <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds two troubleshooting sections to the Feishu docs for common multi-agent deployment issues: **gateway device token mismatch** (stale cached token causing A2A communication failures) and **missing `deliveryContext.to` field** (agent fails to reply in group chats). The content is practical and well-structured, based on real dual-bot deployment experience. - The new sections fit naturally into the existing Troubleshooting section and complement the Multi-agent routing configuration docs - Prior review threads have already identified the key issues that need resolution before merge: invalid JSON comments in copy-paste blocks and a Linux-specific `systemctl` command that should use the cross-platform `openclaw gateway restart` - No new issues found beyond what has already been discussed <h3>Confidence Score: 3/5</h3> - Documentation-only PR that is safe to merge once the previously flagged JSON comment and platform-specific command issues are addressed. - Score of 3 reflects that while the content is valuable and well-organized, the previously flagged issues (invalid JSON comments in copy-paste blocks that would cause runtime parse errors, and a Linux-specific systemctl command) need to be resolved before merge. These are the same issues identified in prior review threads. - `docs/channels/feishu.md` — the JSON code blocks at lines 456-461 and 464-473 contain `//` comments that are invalid for `JSON.parse` (the parser used for `sessions.json` since commit 5c32989f), and the quick fix at line 432 uses `systemctl --user restart` instead of the cross-platform `openclaw gateway restart`. _{Last reviewed commit: 44febb5} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->