dsh-purge tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of dsh-purgeagent-toolsbackupdeepseekdeepseek-harnessdshdsh-plugin

Session recording

Loading recording...

Download the original recording · fingerprint 21443597a3ae5eb0...

What the test found

dsh-purge-community 1.6.60 dependencies install and build; docs, client-bundle, npm-pack smoke and UI contract checks pass; the repo's full test suite passes 357/390 with 18 failures that reproduce only on Node >=22 (container has Node 18.19.1, CI uses Node 22); the real installer completes against a mock DSH CLI with a backup_id and the installed CLI answers status/selfcheck/probe/preset/boost/audit/usage/backup/diagnose, while apply correctly fails with exit 1 in a hostless environment.

Dependencies installed, docs check passed, panel bundle check passed, npm pack smoke passed (7/7), UI contract test passed. npm test: 357 pass/18 fail/15 skip - all 18 failures are Node-22-only test features (node:sqlite, import.meta.dirname in another file, steering runtime) not reproducible on container's Node 18.19.1 (CI runs Node 22). Real install exercised end-to-end: scripts/install.sh --dry-run exit 0, real install exit 0 with backup_id, installed CLI status/selfcheck/probe/preset/boost/audit/usage/backup/diagnose all exit 0 (selfcheck state=unknown is correct without a real DSH host; apply and invalid rollback exit 1 by design). One source fix applied: test/no-region-gate.test.mjs Node-18 compatibility. No real DSH host or credentials exist in container; installer verified against a schema-correct mock DSH CLI standing up per instructions.

Argusic installed dsh-purge in 7 minutes and launched it; verification reached Verified with mock services. 4 of 4 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of dsh-purge

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion