8505559fa9
Every USER message starts a conversation (the same boundary the turn engine's delta scoping keys on). The latest conversation renders in full; older ones collapse to a one-line summary row — head text, reply count, last-activity time — that expands/collapses on click. db's 'threads per conversation' ask, delivered as timeline folding: no log-model change, no new persistence, cross-machine sync untouched. groupChatConversations() splits the log (leading member run from a trimmed log forms a headless block); rendering extracts renderEntry() unchanged. Tests: conversation splitting (headless block, heads, startIndex) + fold source contracts. 256/256 plugin tests pass.
Bundled plugins
Drop a <name>/plugin.{ts,tsx} here that default-exports a HermesPlugin and
it registers automatically at boot (vite glob in ../contrib/plugins.ts), with
the same inventory + live enable/disable contract as runtime plugins.
Keep this tree for real shipped plugins (and the small authoring fixtures that
dogfood the SDK). One-off demos that rebuild a core chrome piece 1:1 do not
belong here — they double the UI and confuse Settings ▸ Plugins. Publish those
in the companion
hermes-example-plugins
repo instead.
User- and agent-authored plugins load at runtime from
$HERMES_HOME/desktop-plugins/<name>/plugin.js (the disk door) — see the
hermes-desktop-plugins skill.