Repository navigation
dashboard: full id platform coverage — auto-updated phases, validation, CI and queue panels #1239
Description
dashboard: full id platform coverage — auto-updated, nothing hand-maintained
The PM dashboard now lists id (Grist roadmap rows + org Project), but the id picture is still assembled by hand and goes stale. Build the id section out into a coherent, full-featured, automatically updated view of the whole platform. Drew (2026-10-26): "We need to make a coherent, full-featured dashboard that covers everything and gets updated automatically with all aspects of the id platform built out on it."
Panels (all fed from live sources, no manual edits)
- Path to Phase 12: the ordered checklist from id: Path to Phase 12 — ordered prerequisite queue (CI trust → validation → journal → visibility → remaining F11) #1235 with live per-step state (issue state + queue state), so the "what's next" answer is always on screen.
- Phase tracker: Phases 0–13 progress derived from the phase plans + issue states (F-item mapping), including validation status per phase from id: validation — Phases 0–8 + platform completion acceptance audit #1075–id: validation — delivered Phase 11 items (claimed-done audit) #1078 and their follow-ups.
- Build health: PR CI lane + id E2E nightly trend (pass/fail history, current failure links) from the GitHub Actions API.
- Queue & fleet: repo-health queue depth/age for id work, claimed/parked items, sweep outcomes — the same numbers the fleet runs on.
- Phase 12 readiness: per-F-item state (design via id: Phase 12 designs to run through the research workflow #534, issue, PR) for F12.1–F12.18.
Rules
- Strategy rows stay human-owned in Grist; everything operational is generated. If a number on the dashboard required a person to type it, that's a bug in this issue's terms.
- Reuse the existing aggregator + collectors (Projects-token collector pattern); extend the Grist seed/roadmap generation from
planning/roadmaps/id.mdwhere a table is wanted. - Mobile-reviewable, per the slice-2 dashboard rules (impl(aggregator): slice 2 — mobile, needs-Drew/needs-orchestrator tiers, time-granular roadmap, session clarity #898). Loopback + tailnet only, same access model as today.
- Coordinate scope with the discussion in the "next horizons" issue before building panels beyond the list above.
Acceptance: the five panels live on the dashboard, each showing a source timestamp; killing any manual step in keeping them current; a stale-source warning appears instead of silently old data.
Acceptance criteria
- The dashboard's id section shows all five panels — Path to Phase 12 (id: Path to Phase 12 — ordered prerequisite queue (CI trust → validation → journal → visibility → remaining F11) #1235 steps with live issue + queue state), Phase tracker (Phases 0–13 incl. validation status from id: validation — Phases 0–8 + platform completion acceptance audit #1075–id: validation — delivered Phase 11 items (claimed-done audit) #1078), Build health (PR CI lane + E2E nightly trend from the GitHub Actions API), Queue & fleet (repo-health depth/age, claimed/parked, sweep outcomes), Phase 12 readiness (per-F-item design/issue/PR state for F12.1–F12.18).
- Every operational number on the dashboard is generated from a live source; if a number required a person to type it, that is a defect against this issue. Strategy rows remain human-owned in Grist.
- The dashboard is mobile-reviewable and keeps the existing access model (loopback + tailnet only), reusing the aggregator + collectors (Projects-token collector pattern).
Metadata
Metadata
Assignees
Labels
Package/app: id (pkgs/ or apps/ in this repo)pm-stack (Pad/Grist) in developing-today/codeLarge: multi-day or open-ended; expect staged check-insNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedFollow-up spun out of earlier workFully doable remotely: design, config, code, cloudOrg Project gate: queued next — orchestrator adds to the boardOrdinary priority (the default)Queue or user escalation stateFiled directly by a humanQueue or user escalation stateQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-368
dezren39 commentedon Oct 27, 2026
Intake review
Related: #1235 (Path to Phase 12 — source of the ordered-step panel), #898 (slice-2 dashboard rules), #1240 (next-horizons discussion — coordinate scope there before building panels for undecided phases).
Notes: The filer already normalized kind/source/status/effort/app labels; this pass added priority and acceptance criteria. The 'no hand-typed numbers' rule in the body is the sharpest requirement and is now an explicit acceptance test.
Risks: Panel scope can sprawl — five panels each with a live collector is a real build; the Phase 12 readiness panel depends on #534's design pass producing per-F-item state worth showing. Staleness must be visible (a dead collector should look dead, not quietly freeze at its last value).
Suggested approach: Build panel by panel behind the existing aggregator, starting with Path to Phase 12 (its data model — issue + queue state — is already the fleet's daily bread).
17 remaining items
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8045 (small_fix, queued, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
opencode; handing off to the laptop claimant.dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 4, 2026
🤖 Agent note · blocked: packet defect