v0.11.1

The export downloaded the wrong extension

The page builds its download from a blob, so it never reads the
Content-Disposition the server sends — and it had .md hardcoded. Every format arrived
named Markdown: JSONL saved as .md, HTML saved as .md. The extension follows the
selected format now, and the filename goes through the same sanitising the server applies,
so a title containing a slash no longer becomes a path.

The Export button also stopped fitting. Naming the format in the button was meant to make
the picker beside it self-explanatory, but two controls each naming the format is one too
many for a 290px pane — the label ran 34px past the card's edge. The picker says it; the
button says Export.

A Claude Code skill ships with the repository

.claude/skills/agent-sessions/SKILL.md carries
the part a tool schema cannot: which tool answers which question, how to land on a search
hit instead of paging towards it, when the answer is a file rather than context, and what to
warn about when handing a pack to another agent.

ln -s "$PWD/.claude/skills/agent-sessions" ~/.claude/skills/agent-sessions

Code scanning

CodeQL now runs over the Go sources on every push. (Thanks — it caught nothing yet, which is
the outcome a read-only service should produce.)

Documentation

docs/mcp.md had get_messages orphaned outside the tools table by an earlier edit — the
table listed four tools and the fifth appeared as a stray paragraph at the bottom of the
file. A check now compares the documented tool names against what tools/list actually
returns. The document also gained a section on how the tools fit together, since the table
says what each one is but not which to reach for.

Full changelog: v0.11.0...v0.11.1