Skip to content

v0.8.1: shaped by the first real reader

Choose a tag to compare

View all tags
@rodlunt rodlunt released this 13 Aug 09:19
· 154 commits to main since this release
v0.8.1
54e35c4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The first release whose contents came from watching a real reader use the tool: an external tester read a v0.8.0 report of a 181-rule run on his phone and sent screenshots, and everything user-facing here follows from that.

Upgrading: re-run your install command with @v0.8.1. No schema change: run-states from 0.8.0 remain readable, and this build reads them.

Reading the report on a phone

  • The not-applicable and could-not-evaluate blocks collapse behind one-line summaries carrying their counts, instead of screens of rule ids between you and the rest of the report
  • The per-domain table stacks into labelled rows at phone widths, instead of crushing six columns into a horizontal scroll
  • Long values such as full commit hashes wrap inside the run-details card instead of escaping it

Verified against the tester's actual run re-rendered at 412px and 320px.

Provenance

  • Pack dirty detection is now scoped to the rules directory. The tester's run lost its pack staleness check to an untracked mcp.json at the clone root, created by this README's own headless example. A stray file outside the rules directory can no longer cost you the comparison; a change inside it still does, because that genuinely changes the pack
  • Editable and checkout installs of the tool now report their own git commit instead of unknown, a modified tool build carries a visible caveat, and a dirty build reports could-not-check rather than pretending to compare against releases
  • The pack version string reads v0.6.1+10 instead of v0.6.1+, so two runs' packs compare at a glance

Pack compatibility contract

The tool reads an optional pack.toml from the rules directory, in which a pack declares its rule-file format and the oldest tool it requires. A mismatch renders an honest notice naming both sides; absent metadata claims nothing. The maintained pack now ships this file. Third-party packs can adopt it with two lines.

Protocol

AUDIT.md now carries explicit criteria for declaring a whole domain could-not-run versus running it with per-rule not-applicable verdicts, with a bias to running when in doubt. Motivated by two audits of the same repository at the same commit reaching opposite calls on a whole domain, one of which found a high-severity problem the other never looked at.

Assets 3
Loading