HTML report: trace view (step timeline + findings), not a bare table - #55
Merged
Conversation
…re table `tracelint check --html` now shows what happened, visually: each linted run renders as the agent's step timeline — every step a finding touches is marked inline with its rule and tier — beside finding cards (tier, rule, summary, evidence) and a verification-coverage bar. The CLI now passes the traces through; render_html gained a `traces=` param (without it, the compact findings table still renders, so existing callers/tests are unchanged). Still a single self-contained file: inline CSS, no scripts, no external resources (the report stays script-free by design). Reuses the canonical Trace + LintReport data already produced — no new plumbing. This is the "UI" done honestly: a static report artifact, not a hosted app. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
"Option A" from the UI discussion: make the report tracelint already emits (
--html) show what the agent did, not just a findings table — the honest, cheap "UI" (a static artifact, not a hosted app).What changed
tracelint check spans.json --html report.htmlnow renders each linted run as:finding_type, summary, and an evidence snippet;render_htmlgained atraces=parameter (pass alongsidereports=). Without it, the previous compact findings table still renders — so existing callers and tests are unchanged._cmd_checknow threads the traces through.Honest by construction
Still a single self-contained file — inline CSS, no
<script>, no external resources (a test enforces this). It reuses the canonicalTrace+LintReportdata already produced; no new plumbing, no backend. This is the "UI" as a report artifact, deliberately not a hosted dashboard (that would reintroduce "another place to go," against the strategy).Tests
Added
test_html_trace_view_shows_steps_and_findings(steps + finding + evidence render, still script-free). Full suite green; ruff clean.Bonus: the generated report is now a real screenshot source for the site hero.
🤖 Generated with Claude Code