fix(gateway): preserve kanban notifier chat type

[ljsdut]

Summary

• Persist chat_type on kanban_notify_subs, including legacy-table migration and rebuild specs.
• Carry HERMES_SESSION_CHAT_TYPE through gateway session context so kanban_create auto-subscriptions record the source lane.
• Rebuild notifier wakeup SessionSource with the subscription's persisted chat_type, falling back to group for old rows.

Root Cause

Kanban notifications delivered the text message to the subscribed chat, but the follow-up agent wakeup hardcoded chat_type="group". For DM-originated tasks, Hermes created or woke a synthetic group session instead of the PM's real DM session, so the PM often never saw the coder/QA completion in the active lane.

Tests

• PYTHONPATH=/tmp/hermes-pytest-deps:. /home/ubuntu/.hermes/hermes-agent/venv/bin/python -m pytest tests/gateway/test_kanban_notifier.py -q
• PYTHONPATH=/tmp/hermes-pytest-deps:. /home/ubuntu/.hermes/hermes-agent/venv/bin/python -m pytest tests/gateway/test_session_env.py tests/gateway/test_session_context_inheritance.py tests/gateway/test_async_delivery_capability.py -q
• /home/ubuntu/.hermes/hermes-agent/venv/bin/python -m py_compile hermes_cli/kanban_db.py gateway/session_context.py gateway/kanban_watchers.py tools/kanban_tools.py gateway/slash_commands.py gateway/run.py tests/gateway/test_kanban_notifier.py
• PYTHONPATH=/tmp/hermes-pytest-deps:. /home/ubuntu/.hermes/hermes-agent/venv/bin/python -m ruff check hermes_cli/kanban_db.py gateway/session_context.py gateway/kanban_watchers.py tools/kanban_tools.py gateway/slash_commands.py gateway/run.py tests/gateway/test_kanban_notifier.py

[alt-glitch]

This was generated by AI during triage.
Duplicate of #56632 — both fix the kanban notifier wake mis-routing by persisting chat_type on kanban_notify_subs and rebuilding the wakeup SessionSource with it (carried via HERMES_SESSION_CHAT_TYPE). Same mechanism, 6 of 7 files identical (#56632 is earlier/canonical, targets #56580). Flagging for a maintainer to pick one.

[teknium1]

Thanks for carrying the source lane through the notifier path. The premise is confirmed on current main: gateway/kanban_watchers.py:517-537 documents the missing provenance and hardcodes the wake source to chat_type="group".

Problems

• hermes_cli/kanban.py:2439-2444 is a sibling notification-subscription writer that still supplies no chat type. A manually created DM subscription would remain NULL and hit this PR's group fallback in gateway/kanban_watchers.py.
• The new gateway bridge in gateway/run.py is not directly covered: tests/gateway/test_kanban_notifier.py sets the ContextVar directly, while tests/gateway/test_session_env.py:33-72 does not assert HERMES_SESSION_CHAT_TYPE from _set_session_env().

Suggested changes

• Add and thread a --chat-type value through hermes kanban notify-subscribe, with a DM wake regression test.
• Add set-and-clear assertions for HERMES_SESSION_CHAT_TYPE through _set_session_env().

This is an automated hermes-sweeper review.

[teknium1]

Please add a direct regression assertion through _set_session_env(): the notifier test sets this ContextVar directly, so it would not catch this production bridge being omitted or cleared incorrectly.

[teknium1]

Merged via PR #72191 — your commit was cherry-picked onto current main with your authorship preserved in git log (05ab059). Your implementation won the arbitration among four competing PRs for this bug: earliest submission and the only one that fixed the auto-subscribe path end-to-end (ContextVar bridge + gateway stamp + schema with self-heal backfill), not just the slash-command site. Nice work.