Burgunthy e8b7ce8c19 fix(session): persist profile_name and route batch key by profile ... Two follow-ups observed after deploying profile routing: 1. sessions.profile_name was NULL even when the agent ran inside the routed profile scope. _insert_session_row never wrote it, get_or_create_session / reset_session never passed it through, and the agent-side _ensure_db_session fallback had no way to read it. - Declare profile_name TEXT in SCHEMA_SQL so _reconcile_columns auto-adds it on existing DBs. - _insert_session_row takes profile_name and writes it. - SessionStore passes source.profile (or old_entry.origin.profile on reset) into db_create_kwargs. - _ensure_db_session reads the active profile via get_active_profile_name() inside _profile_runtime_scope. 2. DiscordAdapter._text_batch_key called build_session_key without profile=, so the batch key always landed in agent:main even when the routed profile differed — diverging from the agent session key namespace (agent:crypto-trader, agent:ai-expert, ...). Pass event.source.profile through so both namespaces agree. Live verification (jth-server-2, 2026-06-28): a test message in a routed #coin thread produced agent:crypto-trader:discord🧵... in the batch log and profile_name=crypto-trader in the sessions row. Default-routed chat still produced agent:main / NULL. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-07-15 09:50:05 -07:00
..
__init__.py	refactor(gateway): migrate Discord adapter to bundled plugin (full Teams parity)	2026-05-22 14:21:41 -07:00
adapter.py	fix(session): persist profile_name and route batch key by profile	2026-07-15 09:50:05 -07:00
plugin.yaml	refactor(gateway): migrate Discord adapter to bundled plugin (full Teams parity)	2026-05-22 14:21:41 -07:00
voice_mixer.py	revert(windows): roll back terminal-popup PRs #53791 #53810 #53829 (#53853)	2026-06-27 15:59:00 -07:00