feat: Run Report infographics + Studio 3D stage panels (#60) — v1.8.0#61
Merged
Conversation
#60) - state/stage-reports.js: parse the 15 canonical stage artifacts + key deliverables (release-readiness, summary), size-capped, malformed-tolerant - GET /api/run-report?run=<id>: one sandboxed call returns all parsed reports (reuses the run-dir resolver; traversal → 404) - runs carry a stageReports index; shipped in client state - 3 tests: parsing, index, malformed-JSON tolerance Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rds (#60) - New Observe page: run selector, KPI flashcard row, infographic grid - Shared card renderers: threat-severity donut, compliance/consistency gauge, test pass/fail bars, cost flashcard, requirements/planning/architecture stat-chips, release-gate badges, mini-lists - Polished motion: count-up numbers, donut/gauge fill from zero, bar fill, card fade-in + hover lift, blocked-gate pulse — all CSS/SVG, zero deps Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…raphic (#60) Clicking an agent now fetches /api/run-report and renders that stage's compact infographic in the side panel — threat severities + gate, compliance score, test pass/fail, cost/mo, requirement counts — so 'what they shipped' shows the real structured data. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…graphics Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
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
2 participants
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.
Closes #60.
Surfaces the run data that was captured but never shown — the 15 structured stage reports — as eye-catching infographics, in both agreed places.
Server
state/stage-reports.js— parses the 15 canonical stage artifacts + key deliverables, size-capped, malformed-tolerantGET /api/run-report?run=<id>— one sandboxed call (reuses the run-dir resolver; traversal → 404)stageReportsindex in client stateRun Report page (Observe)
Run selector → KPI flashcard row → infographic grid of all 15 stages:
Polished motion: numbers count up, donut/gauge fill from zero, bars fill, cards fade-in + hover-lift, blocked gates pulse — all CSS/SVG, zero new deps.
Studio 3D
Clicking an agent now fetches the run report and renders that stage's compact infographic in the side panel — 'what they shipped' shows the real structured data.
Verification
node --checkcleanRelease
v1.8.0 + CHANGELOG.
🤖 Generated with Claude Code