Fix: Handle direct_message events in dashboard presence handler

[khaliqgant]

Summary

• Fix message routing bug where messages sent to GitHub username (e.g., khaliqgant) were not received in dashboard UI
• Messages sent to _DashboardUI worked because they were fetched from storage, but real-time direct messages were silently discarded

Root Cause

handlePresenceEvent in App.tsx only handled channel_message events and ignored direct_message events:

```typescript
// Before: Only handled channel_message
const handlePresenceEvent = useCallback((event: any) => {
if (event?.type === 'channel_message') {
// ... process channel message
}
// direct_message events were silently ignored!
}, [...]);
```

When UserBridge forwarded DMs via WebSocket as { type: 'direct_message', from: 'Agent', body: '...' }, they were discarded.

Fix

Added handling for direct_message events that:

1. Creates a consistent DM channel ID (dm:user1:user2 with sorted participants)
2. Appends the message to the channel messages state
3. Handles unread state like channel messages

Changes

This PR contains only the direct_message event handling fix in App.tsx. No relay-pty or Rust changes included.

Based on main, which already has the _DashboardUI display fixes from PR #193.

Test plan

• Send message from agent to GitHub username - verify it appears in dashboard
• Verify existing _DashboardUI routing still works
• Verify channel messages still work correctly

🤖 Generated with Claude Code

[my-senior-dev-pr-review]

🤖 My Senior Dev — Analysis Complete

👤 For @khaliqgant

📁 Expert in src/dashboard/react-components/ (10 edits) • ⚡ 56th PR this month

View your contributor analytics →

---

📊 1 file reviewed • 8 need attention

⚠️ Needs Attention:

• src/dashboard/react-components/App.tsx — New event handling logic potentially introduces security issues and requires thorough validation.

---

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

• 💬 AI Chat — Ask questions on any file, get context-aware answers
• 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
• 📚 Code Archeology — Understand how files evolved over time (/archeology)
• 🎯 Learning Insights — See how this PR compares to similar changes

---

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

• Ask questions about the code or PR
• Request explanations of specific changes
• Get suggestions for improvements

Slash commands:

• /help — Show all available commands
• /archeology — See the history and evolution of changed files
• /profile — Performance analysis and suggestions
• /expertise — Find who knows this code best
• /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona	Focus
@chaos-monkey 🐵	Edge cases & failure scenarios
@skeptic 🤨	Challenge assumptions
@optimizer ⚡	Performance & efficiency
@security-auditor 🔒	Security vulnerabilities
@accessibility-advocate ♿	Inclusive design
@junior-dev 🌱	Simple explanations
@tech-debt-collector 💳	Code quality & shortcuts
@ux-champion 🎨	User experience
@devops-engineer 🚀	Deployment & scaling
@documentation-nazi 📚	Documentation gaps
@legacy-whisperer 🏛️	Working with existing code
@test-driven-purist ✅	Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.