# Hermes WebUI fixture provenance

These minimal files contain the exact patch-context fragments extracted from the
Hermes WebUI image pinned by `dockerfiles/Dockerfile.hermes-webui`:

- Image: `ghcr.io/nesquena/hermes-webui@sha256:a83a3893111dcb250e7aa7aa657d3d6f4570b0e2fd00d9b7569246fc5e7339b2`
- Version: `0.52.181`
- OCI source revision: `7a94e34a6d639576576baa9131acf6765f6d2b98`
- Full upstream `static/index.html` SHA-256: `6e218d42f6e047168a774c59aa9fc98a55b608cdc070cf1049ad414a597a722c`
- Full upstream `api/routes.py` SHA-256: `a09c3a236a323b0d1ad22409f6576fa21a0f3ca413ad8eeec06abb87067dc2ab`
- Full upstream `static/panels.js` SHA-256: `276e5dfc2cac6eee4a1820e4fab9c4da52743efed4a1b1e9d58d6dd15f6fd5c9`

The fixture stays intentionally narrow, but tests execute the shipped patchers
against it; large inline artwork bodies are reduced while their exact unique
boundary tags are retained so fail-closed replacements are exercised without
copying generated SVG payloads into the fixture.