v0.8.0: the report answers the reader's question first

This release is mostly about the report you actually read, plus six defects found by a code review of the whole range before cutting it.

Upgrading: re-run your install command with @v0.8.0. This is a minor rather than a patch because the run-state schema moved from 3 to 4: a v0.7.0 build refuses a run-state file written by this release.

The report was redesigned

It used to open with six screens about how the run went, and the first finding landed on printed page 7 of 26.

• A computed headline is now the first thing on the page, naming what needs attention first
• Findings are sorted worst first, instead of the order they happened to be recorded in
• Five separate per-domain lists are now one table, with inline bars encoding quantity as length
• The tool self-assessment is collapsed behind summaries that each carry their own numbers, so nothing is hidden and nothing occupies the top of the page
• Severity levels are defined in the report itself, and stated as assigned by the assistant rather than measured
• Each finding carries its domain confidence and rule-fetch status, and those travel into filed issues too
• Print drops the issue-filing section rather than clipping it, long paths wrap on narrow screens, and dark-mode severity badges now meet contrast

Honesty of the audit itself

• not-applicable requires a written reason and renders it. One earlier tester run had 172 of 260 verdicts as unjustified not-applicable, invisible in the output
• Rule fetches are recorded, so a verdict reached without ever fetching its rule text is provable
• Run duration is measured by the server and compared against what the assistant claims

Gemini setup

The documented install could never have worked: the extension manifest sat in a subdirectory, and Gemini CLI resolves an extension only from a repository root, so the MCP server was never registered. The packaged extension is dropped in favour of a manual server entry and a prompt you can paste. Gemini support remains documented but unexercised against a real Gemini CLI.

Fixed before this cut

A pre-release review of v0.7.0..main found six defects, all fixed here:

• Resuming a run saved by v0.7.0 rewrote its schema version and made it permanently unresumable
• A finished timestamp in a different timezone form from the started one raised a TypeError and destroyed a completed run at the final step
• A typo in a custom output path (~unknownuser/...) crashed the configuration page and lost the rest of the form
• The markdown stripper rewrote shell commands, so a finding saying rm -rf build/* could file an issue saying rm -rf build/
• A finished time earlier than the started time rendered as its magnitude, so the duration row declared two identical figures disagreed
• The issue list over-counted how many boxes were ticked, ignoring findings already filed

Feedback

The report now asks two optional questions about what you concluded from it, alongside the existing freeform box. Both are off by default and never prefilled, like every other shared section.