montjeffrey e716f7ea65 test(gateguard): use the repository's own test helper ...

The suite was the only file in tests/docker using node:test. The repository's
dominant convention, in 229 of 327 test files including the sibling
gateguard-effectiveness suite, is a local test() helper that counts passes and
sets process.exitCode, which is what tests/run-all.js reads.

Adopt that helper verbatim, along with the sibling's tempDir wrapper so the
scenario fixtures resolve symlinked temp paths. Assertions are unchanged.

2026-10-04 22:40:42 -04:00

..

gateguard-effectiveness.test.js

feat(gateguard): measure question effectiveness with trapped agent tasks

2026-10-04 22:40:41 -04:00

gateguard-intent.test.js

test(gateguard): use the repository's own test helper

2026-10-04 22:40:42 -04:00

plugin-setup-harness.test.js

feat(docker): add hardened CLI test harness (#2625)

2026-08-06 16:52:39 -04:00