Fixed
- v0.6.1 regressed detection of agents run as container images from a
registry named without a dot: its registry-stripping expression required a
dot in the host, sodocker://registry:5000/all-hands-ai/openhands:0.9,
docker://localhost:5000/…, anddocker://localhost/…were no longer
recognized (v0.6.0 recognized them). Found by the 2026-09-09 follow-up
review's live comparison of the two published tarballs. The registry
component now follows Docker's rule — the first path segment is a registry
when it contains a dot or a colon or islocalhost— and owner identity
stays exact behind any registry form. Tests intests/precision.test.ts.
Frozen benchmark: 0 of 152 cases changed (no snapshot uses adocker://
agent image).
Changed
scripts/benchmark/report-behavior.mjsrecords the SHA-256 of the
dist/cli.jsthat scanned, in each report's metadata and in the
comparison header, so a report identifies the implementation even when the
working tree was dirty (the Day 8 report had recorded a commit plus 21
uncommitted changes).
Verified artifact
The attached agentci-guard-0.6.2.tgz is the tarball pnpm package:smoke verified at commit 7defcb51817ef5cd3471052e17a1c2a6e045d330 (10 checks from the extracted tarball without node_modules, including an npm install -g into a temporary prefix and a scan through the resulting bin shim). SHA-256:
ca28b0e2f6ac02324817564c860fa571cede8e70413cf56f860b22e3447cbcf2 agentci-guard-0.6.2.tgz
Install exactly this candidate: npm install -g https://github.com/David-Wu1119/agentci-guard/releases/download/v0.6.2/agentci-guard-0.6.2.tgz then agentci --version (prints 0.6.2). npm registry publication is pending (a separate, human-authorized step; the registry serves 0.1.0). Action route: uses: David-Wu1119/agentci-guard@v0.6.2. The floating v0 moves here only after the published-tag consumer smoke passes. Detector changed relative to v0.6.1 (registry parsing), so this is a new candidate identity; no frozen benchmark case moved.