Reports: one tab, reports that declare their kind, every run kept, a timeline to scrub and play issue #127 open andymccall opened this 25 days ago · 1 comment

Design: docs/reports.md. A report is a directory (report.toml with kind, title, summary and headline metrics; for performance and custom kinds an index.html and data/), from a Flow job's report output or oh report upload. The hub keeps each run's bundle as a content-addressed tree in the repository's store (unchanged files cost nothing), indexes reports and metrics in the database, keeps bundles by policy and metrics forever, and roots them for gc. One Reports tab replaces Coverage and Tests (built-in kinds; today's coverage and junit artifacts are implicit declarations); pages render in a sandboxed frame on a separate origin; a timeline scrubs, plays and compares runs, with report.run()/report.history() for pages that animate; metrics with thresholds set checks. Andy asked for it 2026-10-10, with Metal Gear's performance report as the first user.