Protocol: check command arguments, keep readers alive, one daemon

From review of the protocol commit. An exception inside a command, such as
an id SQLite cannot bind, killed that client's reader and left a deaf
connection still receiving events; commands now run under a try that
answers error. Ids must be integers: delete with no id compared None to an
unsaved conversation's None and wiped it, and a string id deleted the row
through SQLite's affinity while the Python comparison missed, leaving the
current conversation pointing at nothing so every later answer failed to
save. ask, search and their arguments are type-checked instead of coerced.

serve() refuses to start over a socket that answers, since unlinking it
orphaned the live daemon's clients, and main() removes the socket only if
it served it. The accept loop logs and continues on errors instead of
dying silently, and a client line over a megabyte is dropped. The two
known ceilings, a stalled client delaying everyone once for 2 s and a
stopped reply holding the llama-server slot until its next chunk, are
marked. New checks cover each of these and a client connecting mid-reply.

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

0 files changed, 0 insertions, 0 deletions