Skip to content

0.2.32 — verification reporting and the Runtime Report, refined

Latest

Choose a tag to compare

@bkuan001 bkuan001 released this 18 Aug 20:52
· 5 commits to main since this release
v0.2.32
209c0e8

Verification

  • The verifier no longer resumes from a record's self-declared hash after a mismatch: the chain anchor is always the recomputed value, and records after the first break are reported once, as an unverifiable tail, instead of being graded individually. Reported and fixed by @lukiod through the SECURITY.md process — the project's first external security report, scoped precisely and turned around fast (#8).
  • LIMITS §9 updated to match the reporting semantics; windowed reports continue to verify a span on its own terms.

Runtime Report

  • Free-text search, tool/type/severity filters, date windowing, sortable columns, and a click-into-record drawer showing the full sealed record.
  • Viewer-local timestamps with a UTC toggle.
  • Plain-language summary column prefers the recorded outcome summary; the drawer's chain-position note defers to the page-level verification verdict.

Also

  • chain_breaks() helper for window-level integrity checks.
  • The post-break summary links the canonical LIMITS document.