ScopeProof v0.1.16
ScopeProof v0.1.16
ScopeProof v0.1.16 consolidates six protected improvements to the local public-PR review workflow:
- Evidence-level guidance now appears where reviewers confirm criteria and inspect observed evidence.
- Gate reason codes are rendered as readable product language without changing deterministic gate data.
- Criteria confirmation uses one durable success state.
- The evidence matrix is reduced to scan-oriented fields; confidence, candidate count, reason, and missing evidence remain in criterion detail.
- Saved-review reopening is a collapsed secondary path so first-use actions remain primary.
- Visible criterion edits are explicitly marked as pending confirmation. ScopeProof preserves and labels the last confirmed analysis, prevents another analysis run across the mismatch, and invalidates the old analysis when the updated criteria are confirmed.
Verified release identity
- Protected-main merge:
e6f2ad46c7cf56f7ce2886d20d6b2a8aa7f30c22 - Immutable Action source tree:
f567447b4d23ef7e81df789b48826c221cb8a81e - Offline source suite: 243 passed, 1 intentional live-network skip
- Deterministic benchmark: 12 cases, 13 criteria, 0 mismatches, 0 must-have False Ready, 0 false blockers
- Wheel:
scopeproof-0.1.16-py3-none-any.whl - SHA-256:
64f0145d6f89229e62cfbebe8cef18fc996e2ab8a81b1b6ab8a234e5c5851088 - Clean installed identity: distribution, module, CLI, web launcher, and new-review provenance all report
0.1.16 - Dependency check: no broken requirements
- Packaged workbench: exact loopback health response
okon port 8517, clean shutdown, no traceback - Protected PR checks, merged-main CI, and merged-main CodeQL succeeded before publication
The bundled demo, automated suite, benchmark, packaging checks, and local health smoke are controlled product verification. They are not runtime evidence for a pull request, external customer validation, or proof of correctness.
Boundaries
ScopeProof remains deterministic, local-first, public-repository-only, and informational. It uses no paid or LLM API, creates no billing dependency, does not execute pull-request code, and does not support fork testing, private repositories, organizations, or second accounts in this public alpha.