837acdc91d
Review finding on #112260: the hosted-room member relabel regex was a third hand-copied opener list that missed the frames context_compressor and title_generator already treat as harness input, so a member reply starting with "[System: ..." or "[IMPORTANT: 2 background processes ..." reached peers in its exact trusted shape. agent.prompt_builder.CONTROL_FRAME_OPENERS is now the single source; the gateway regex is built from it and the desktop TS literal mirrors it byte-for-byte.
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 Capabilities ▸ 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.