Skip to content

v1.6.3

Choose a tag to compare

@catfish-1234 catfish-1234 released this 10 Nov 00:46
3393e3b

Preserve unresolved finding history across three demonstrated reset modes: a failed redundant Git-directory lookup, an EBUSY record-read failure, and malformed existing JSON. Read the already resolved path under the writer lock and refuse an unverified overwrite rather than resetting the count, original finding and baseline while claiming success. The existing caller reports UNVERIFIED when it cannot persist safely.

Three deterministic regressions fail against the prior source and pass with this fix. Per-process concurrent Stop diagnostics and the original count assertion are retained. This does not establish the cause of the observed Windows15-of-16occurrence count, fix every record-loss path, or change best-effort budget state and documented Stop fail-open behavior. Diagnosis is retained in docs/UNRESOLVED-INTEGRITY.md. Result-contract PR94 remains held; diagnostic PR95 is unmerged. No semantic detection, live-harness coverage or prevention claim.

All PR and postmerge checks passed, including the five-leg Windows-inclusive CI matrix. Fresh isolated merged-main tarball installation passed. Published and verified as @kavishdua/proctor@1.6.3 (latest). Registry tarball SHA-1: 3acd3702e773a7496dd1d3a3e8f8654c792fd570. A fresh registry install verified version, clean check, setup, unresolved gate and offline doctor. The published CLI refused to replace malformed existing history, reported UNVERIFIED with exit1 at exhausted Stop, and the unresolved gate returned3 while preserving the original bytes. Manual publication has no GitHub Actions provenance attestation.