Hermes Agent 96609bdade framework: prove the wrapper guard both ways, and resolve its wrappers relatively ...

Two defects found by running the guard rather than reading it.

1. The guard resolved its sibling wrappers through a hardcoded
   $HOME/.config/mosaic/tools/git. On a host with no installed mosaic home — a
   CI container, a bare checkout — every wrapper lookup missed, `[ -x ]` failed,
   and the guard fell through allowing the raw API write it exists to block. It
   failed OPEN, silently, in exactly the environment least likely to notice.
   It now resolves relative to its own path, so it names the wrappers from the
   install it was launched from, with $HOME as the fallback.

2. There was no test. Adding one surfaced the guard's other sharp edge
   immediately: it matches the literal text of the Bash command, so a harness
   that embeds a blocked pattern inline trips the guard on itself rather than on
   the fixture. That is the correct fail-closed posture and it is now recorded in
   the test's own comments, because the next person will hit it too.

test-wrapper-guard.sh asserts twelve fixtures and asserts the ALLOWED cases as
hard as the blocked ones. A guard that over-blocks gets routed around and a guard
that under-blocks is decoration; only pinning both edges keeps it useful. It is
hermetic — no network, no credentials, no repository — so it joins the CI
sanitization step directly rather than the exclusions file.

2026-08-12 16:54:18 -05:00

..

ci-image.yml

CI: add pre-baked ci-base image (producer) [Phase 1a] (#637)

2026-06-22 22:20:48 +00:00

ci.yml

framework: prove the wrapper guard both ways, and resolve its wrappers relatively

2026-08-12 16:54:18 -05:00

publish.yml

chore(ci): bump ci-base image node 22 → 24-alpine (#639)

2026-06-23 00:59:39 +00:00