static/app.js now injects the "Vault connections" panel into Settings → System
via DOM mutation observer + populates from GET /api/vault/status (already
served by routes/vault_status.py). Mirrors the original behavior from
hermes-webui fork commit 3e2c74f3 without needing any upstream HTML/JS edit.
routes/transcribe.py documents the STT migration design choice (streaming_hook
public-API method vs forced-internal entries) — implementation lands as a
follow-on. Plugin still loads cleanly without STT (route disabled in
_phase2_routes() until Phase 2.1).
CONNECTION-MAP.md regenerated: still 0 forced internals.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
THE single repo holding every Svrnty modification to nesquena/hermes-webui per
the SVRNTY-HERMES Plugin Protocol PRD (hermes/docs/SVRNTY-PLUGIN-PROTOCOL.md).
This scaffold is the empty vessel; Phase 2 migrates the existing fork
modifications (STT, vault status, brand skin) into it.
Contents:
plugin.py register(api) entry; reads 6-method
contract; wires static + routes
svrnty_hermes_webui_plugin/ package wrapper for pip install
manifest.yaml plugin name · version · upstream pin
pyproject.toml pip-installable
routes/__init__.py placeholder until Phase 2 migration
static/ placeholder for brand skin migration
CONNECTION-MAP.md AST-generated; 4 public API calls, 0 forced
scripts/ast-connection-map.py AST walker; modes: regen · --check · --diff
tests/{unit,integration,evals}/ skeleton for Phase 3 eval suite
.github/workflows/
plugin-tests.yml push: unit + integration + map check
connection-map-check.yml PR: regen + diff vs committed
upstream-drift.yml daily cron: detect new upstream tags +
run matrix (activates when Gitea runner
registered on Svrnty infra)
Karpathy 4 rules in CLAUDE.md; every subagent inherits them via the workspace
contract.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>