What problem does it solve? After an orchestrator run or a significant package landing, the owner needs a single readable artifact that captures what shipped, what changed visually, and what the measured gate numbers were, without digging through PRs, ledgers, and test outputs manually. ## Core Features & Use Cases - Structured closeout report: Produces one self-contained HTML file with a fixed section order — headline, landed PRs, visual evidence, gate numbers, time and cost, and parked or failed items. - Visual evidence embedding: Embeds before/after render pairs as downscaled base64 data URIs with captions, sourced from test_results, verifier PNGs, and refbank renders. - Gate and cost tables: Records measured values versus thresholds verbatim in tables, plus wall time per phase, delegated model token cost, and CI minutes. - Use Case: At the end of an overnight Astroray orchestrator session, gather merged PRs via gh, pull gate numbers from spec Status lines, embed the changed renders, and deliver a styled HTML report the owner reviews alongside the standup. ## Quick Start Use the run-report skill to generate the closeout report for today's run, including landed PRs, before/after renders, gate numbers, and the time and cost breakdown.
