Skip to content

v1.6.4 - Visible unverified Stop state

Choose a tag to compare

@catfish-1234 catfish-1234 released this 10 Nov 01:36
1effdfc

Visible unverified Stop state

Unknown Stop checks and budget/record persistence now produce bounded UNVERIFIED diagnostics without turning infrastructure errors into cheating findings or silently clearing prior blocked continuity. Atomic updates preserve prior bytes and original history/provenance on replacement failure, and clean only temporary artifacts they successfully created.

A missing optional execution sequence uses known persisted counts, not an assumed fresh turn. Unknown budgets fail open. Enforce mode attempts to record only the established finding, explicitly not verified exhaustion/count; advisory mode still records nothing. Failed persistence stays UNVERIFIED, not a durable gate. Intentional skips remain silent and preserve continuity; clean count clearing requires successful atomic persistence.

Uncertainty has empty stdout and bounded stderr: Claude/Antigravity preserve exit0; Codex/Gemini use documented nonblocking exit1. Exit status alone does not establish clean checking or recording.

Validation

  • Twenty deterministic fault/ownership regressions; local97-file suite2269 passed,1 skipped.
  • Build/typecheck/lint/self-check and fresh tarball install passed.
  • FixPR98, releasePR99 and postmerge1effdfc all passed five supported CI legs without reruns. Postmerge CI: https://github.com/catfish-1234/proctor/actions/runs/42735724131
  • Security: https://github.com/catfish-1234/proctor/actions/runs/42735724435 ; dogfood: https://github.com/catfish-1234/proctor/actions/runs/42735724685
  • Published and verified as @kavishdua/proctor@1.6.4 (latest). Downloaded registry tarball SHA-1: 9ab4328d87a3a3aa45ee62586222e525f1836b29. Fresh registry install verified version, clean check, setup and deterministic smoke checks: budget path is a directory, persistent record rename failure/owned-temp cleanup, check infrastructure failure retaining a known count across all four protocol formats, and missing optional attempt sequence retaining the known count. Expected unresolved-gate statuses also passed. Offline doctor ran and honestly reported missing setup/CI in an empty test directory and unverified remote protection, not an independent-enforcement claim.

Limits

This closes the deterministic paths described in docs/UNRESOLVED-INTEGRITY.md, not every possible state-loss path. The original Windows15/16cause remains unresolved; result-contract PR94 remains held and unshipped. No new live model/judge or semantic-coverage claims. Local hooks/records remain agent-writable feedback, not independent enforcement. No catch-rate or prevention claim.

Changes: #98 ; #99