Take questions on the socket and stream replies back

Each client gets a reader thread; commands are ask, stop, new, list, open,
search and delete. A reply streams think, token and tool events through
say(), which checks the turn counter under the same lock that stop takes,
so a stopped reply cannot send a token after its done. A finished turn is
saved; a stopped one is not. hello carries the current conversation and
any reply in flight, so a reconnecting canvas redraws both. Errors from
llama-server become an error event and the daemon stays up; every exit
path of main() logs a line, which the voice version's silent death lacked.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions