Repository navigation
v1.6.2
Baseline-controlled dynamic cross-runs restore a bounded set of Jest/Vitest and Python test controls, including deleted or newly added controls. Config-only changes trigger a separate run. Config-change failures remain diagnostic evidence, not cheating findings; probes/mutations do not attribute findings across changed controls.
Resolved Git hashes identify local inputs, not independently trusted revisions or runner/dependency identity. Custom setup imports and other runner controls remain outside this bounded coverage. Dynamic remains opt-in/advisory. No new live-verified harness coverage or authenticated execution claim.
All PR and postmerge CI passed, including the full Windows-inclusive matrix. Fresh isolated tarball installation passed. Published and verified as @kavishdua/proctor@1.6.2 (latest). Registry tarball SHA-1: 748d0e65399f71a323f263e1c87a172997490114. A fresh registry install verified version, clean check, setup, unresolved gate and offline doctor. An end-to-end config-only differential ran three suites, observed failure under restored baseline controls and returned diagnostic evidence with zero cheating findings. Offline doctor correctly reports missing CI/CODEOWNERS in the scratch repository and unverified branch protection. Manual publication has no GitHub Actions provenance attestation.