Build cross-channel bridge — relay important Discord messages to WhatsApp
Strengthened the cross-channel bridge to prevent Discord message silos — ~15 management messages had been lost because Discord sessions are isolated from WhatsApp.
- Added CRITICAL RULE callout at top: "Every substantive message from Maxime on ANY channel MUST be relayed to WhatsApp"
- Added bridge relay convention block with the exact
sessions_send() call signature
- Added quick-reference Relay decision table (message type → relay? yes/no/skip)
- Added 4-step procedure: check user ID → check substantive → call sessions_send → respond normally
- Channel ID mappings already existed, kept intact
- Replaced weaker guidance with same CRITICAL RULE callout and decision table
- Added exact
sessions_send() call to copy-paste
- Added 5-step quick check procedure
- Added "Testing the bridge" section with end-to-end test procedure
- Added "Quick reference: Robbie's bridge checklist" for every Discord session
- Added relay protocol reference (was missing entirely — only Chris/Debbie/Kelly had it)
- Added "One agent, many channels" note
- Added bridge health check to rotate-through checklist
- Documented the bridge fix, its motivation, and all changed files
- Sent test
sessions_send to agent:main:whatsapp:direct:+6580860085 with [discord|test] tag
- WhatsApp session confirmed receipt — relay path works end-to-end
Test message sent via sessions_send → WhatsApp session replied with confirmation. The [discord|test] tag pattern was received and routed correctly.