v0.6.5
Bug Fix
Chat resume not wired: Claude session ID passed but ignored (#8)
The chat manager correctly stores Claude session IDs from result events and passes them as resume_session when spawning follow-up sessions. But lookupResumeSessionID looked up the value in the agentruntime session registry (UUID mismatch — it's a Claude ID), then fell back to filesystem scanning (empty on Docker). Resume was silently dropped, causing every turn to start a fresh Claude conversation.
Fix
lookupResumeSessionID now passes the raw session ID through when no registry or filesystem match exists. The chat manager already resolved it to the correct Claude session ID.
Result
Multi-turn Docker chats now maintain conversation context across turns via --resume --session-id.