agentrust-trace-tests 0.5.0

trace-tests report: conformance results as an artifact somebody can forward

verify answers a question for the person who ran it. The audience that decides whether a portable evidence format beats a vendor console — an auditor, a counterparty, an acquirer — was never in that terminal.

trace-tests report --record trust-record.json \
  --html report.html --json report.json --badge trace.svg

• Self-contained HTML. No scripts, no external CSS, no fonts, no badge service, nothing fetched when the page opens.
• JSON under schema: agentrust-io/trace-tests/report/1, for CI gates and dashboards.
• SVG level badge.
• Runs every level up to --max-level, not one, because the answer a reader needs is the highest level the record reaches, not whether it cleared the level whoever ran the tool happened to pick.
• --fail-under N gates CI on a level. Without it the command exits 0: producing an artifact and enforcing a threshold are different jobs.

The report says it is not evidence

A shareable conformance report looks authoritative, gets forwarded, and is unsigned HTML anyone can edit. That is the same shape of thing as a control plane writing the log that describes its own behaviour, which is the problem this project exists to fix. So every report carries the record's digest, the suite and authoring-library versions, and the exact reproduce command, and states plainly that a reader who does not trust the sender should check the record instead of the report.

The HTML and the JSON render from one assembled structure so they cannot disagree about the verdict, and unverified findings count as failures from Level 1 up exactly as they do in verify.

Full detail in CHANGELOG.md.