fix: route dev case notifications to main group

[aviadr1]

Summary

• Dev case creation (case_create with caseType=dev) now sends notifications to the main group instead of the source work group
• Dev case suggestions (case_suggest_dev) also route to the main group
• Work case notifications continue going to the source group as before

Test plan

• Added test: dev case from non-main group notifies main group (tg:111)
• Added test: work case from non-main group notifies source group (tg:222)
• All 16 IPC GitHub issues tests pass
• All 86 IPC tests pass
• Build clean

🤖 Generated with Claude Code

[aviadr1]

Self-Review (Round 1)

Checklist

• case_create with dev type: notification routed to main group JID via isMain lookup, falls back to resolvedChatJid if no main group
• case_suggest_dev: notification routed to main group, falls back to source group
• Work cases unchanged — still notify source group
• Both paths have fallback if main group not found (graceful degradation)
• Tests cover the key routing invariants: dev→main, work→source

Path trace

Work agent (telegram_work) → case_suggest_dev IPC
  → targetJid = find(isMain) → tg:111 (main group)
  → sendMessage(tg:111, "💡 Dev case suggested...")

Work agent (telegram_work) → case_create with caseType=dev
  → notifyJid = find(isMain) → tg:111
  → sendMessage(tg:111, "📋 New dev case created...")

Work agent (telegram_work) → case_create with caseType=work  
  → notifyJid = resolvedChatJid → tg:222 (source group)
  → sendMessage(tg:222, "📋 New work case created...")

LGTM — ready to merge.