MC-4684

Problem: Elmar received direct DMs from @lucienne_claude_bot that were generated by the old Claude/CCGram persistent session via ~/workspace/notify.py, not by the current Hermes/Luci control-room session. Evidence from /home/lucienne/.claude/projects/-home-lucienne-workspace/2952377d-...jsonl shows explicit calls to `python3 notify.py ...` with tool results `Sent to Elmar DM` at 2026-06-03 21:18/21:28/21:31 SAST. Why this matters: old controller sessions can still bypass the current single-voice orchestrator model and DM Elmar directly. That creates stale/conflicting status, especially after Hermes/control-room state has changed. It is not a Telegram 409/poller conflict; it is an outbound notification governance issue. Scope: - Audit all direct Elmar DM senders: notify.py, scheduled tasks, ccgram/persistent Claude sessions, workers. - Add a governance/fence so legacy Claude/CCGram sessions cannot send non-critical MC status directly to Elmar; route to orchestrator inbox / MC topic instead. - Preserve true emergency/auth-failure alerts where policy explicitly allows direct notification. - Update runbook/docs so current Luci/Hermes controller is the single voice for MC status. - Add a regression/check: search active tasks/scripts for notify.py DM usage and flag MC-related direct DMs not using the approved controller route. Acceptance: - Reproduced source of the three 2026-06-03 DMs and documented it. - Legacy path either disabled, gated, or rerouted for MC status. - Critical/auth direct-alert exceptions remain functional and explicit. - No duplicate Telegram pollers are introduced.