Session-store updated_at values are naive local datetimes; passing them
through without an offset broke Instant.parse() on the client, dropping
last_active and leaving the chat list unsorted after restart.
Two live-deployment bugs found during end-to-end verification:
1. server.py: ContextVars set in adapter.connect() do not propagate into
aiohttp handler tasks, so hermes_bridge._current_server()/_current_adapter()
resolved to None inside message handlers (conversation.list returned empty
snapshots, broadcast fan-out and notification paths silently no-oped).
Bind both contextvars at the top of _handle_ws — the per-connection task
owns the context for all its handler dispatch and agent-thread bridges.
2. hermes_bridge.py: create_conversation passed two extra positional args to
SessionStore.get_or_create_session() (source, False, False) — the actual
signature is (source, force_new=False). TypeError was swallowed by the
guard, so pre-creating an empty Hermes session at conversation.create
always failed; sessions were only created on first message.
Verified live against the running gateway: full 11-point E2E (auth 401,
hello/ready, conversation list/create/delete with persistence, chat.send
round-trip through the agent, run lifecycle events, models.current,
reasoning.current). 46/46 unit tests pass.
Pheby
Codex