Build a live squad dashboard

I want one page about my squad that I can open every morning and share with the team, built from our real numbers. ## Context - Squad: [squad] - Period: [last 30 days], compared with the 30 days before it - Where it will be seen: [a screen in the office | a link in Slack | my own browser tab] - If I left anything in [brackets], keep what reads as a default (a period, a number of days, the first of several options) and ask me for the rest in one go, before pulling any data. - Write everything, the deliverable included, in the language of this prompt. ## Pull this data from DevStats 1. Throughput, PR Cycle Time with stage breakdown, Deploy and DORA Metrics — both periods 2. Daily WIP for the current period 3. Open PRs, Aging Issues and Aging Branches — the current snapshot 4. Sprint Progress — only if the squad runs sprints 5. Benchmarks ## How to build it - A dashboard has to answer three questions in five seconds: are we shipping, is anything stuck, are we stable. Lay the page out in that order, top to bottom. - Open with one sentence that reads the data for me, for example: "Review is the slowest stage this month and three PRs have been waiting 5+ days." - Top row: four tiles — PRs merged, PR cycle time, deploys, change failure rate. Each with the change vs the previous period and the benchmark tier as a small label. Color means better or worse, not up or down: cycle time going down is green. - Middle: cycle time by stage as one stacked horizontal bar (where the time goes), and WIP as a small trend line. - "Stuck right now" is the section people act on, so make it the largest: the five oldest open PRs and the five oldest in-progress issues, with age and link. - A sprint progress bar, only if there is an active sprint. - Seven elements at most. No pie charts, no gauges. Large numbers, small labels. If it goes on an office screen, it must be readable from three meters. - It is a shared page: show PR and issue titles and repositories, not people's names. - Show the period and the date the data was pulled. If a tool returned nothing, show an empty state that says so instead of a zero. - A change failure rate of 0% usually means incidents are not recorded: write "not recorded" on the tile instead of a green zero. A stage that is blank in the previous period was not tracked: show no change for that stage, and none for the total. - When two reports count the same thing differently (open branches in Daily WIP and in Aging Branches), show one of them and name the report. ## Deliver 1. A single self-contained HTML file I can download (publish it as an artifact as well if you can): inline CSS, charts in inline SVG or one charting library from a CDN, responsive, with light and dark themes. 2. Keep all the numbers in one JSON object at the top of a script, and render the page from that object. Running this prompt again then only replaces the object. 3. Three lines, in your reply and not on the page, telling me how to refresh it and what to look at first each morning.