Repository navigation
impl(dashboard): project page + complexity-weighted progress visualization (seed: lab-cluster) #1108
Description
Dashboard: project page + complexity-weighted progress visualization
What
A pluggable dashboard page per project Area (org Project #4), following the /dns precedent (#906), seeded with lab-cluster. It renders the project's standard home from its sources instead of a hand-maintained copy:
- Project description + latest status: from
planning/roadmaps/<project>.mdand the newestdoc/<UTC>_status_<project>/record in the owning repo. - High-level items: the Project Bump build/buck/preludes/buck2-prelude from
3a02ea3to9530656#4 rows for that Area (Kind=Epic). - Work structure: the epic → sub-issue tree from GitHub, with blocks/blocked-by edges.
Visualization (the point of this issue)
Progress must reflect complexity and depth, not issue counts alone:
- Weights from
effort/*labels: xs=1, s=4, m=12, l=40 (l flagged open-ended). Unsized issues shown as unsized weight, never silently zero. - Per section (epic): weighted progress bar (closed weight / total weight) with raw count as the secondary number; hands queue = open weight by
mode/*(physical + hybrid weight waiting on hands vs online weight); blocked weight and longest dependency chain (depth). - Link graph: epic → issue tree; node size = weight, color = status, border = mode (solid online, dashed hybrid, thick physical); edges = parent / blocks.
- Project header: weighted % first, counts second, deepest chain and physical weight remaining as headline numbers.
Seed data (filed 2026-10-26)
Epics #1080, #1081, #1083, #1084, #1085, #1086, #1087, #1088, #1090, #1091, #1092, #1093 (Area=lab-cluster, Kind=Epic in Project #4), with 13 detailed sub-issues under epics 1–3 (#1094–#1106). Spec: goal workspace files/project-structure-spec-2026-10-26.md (Muse goal goal_ba17a5777c21).
Acceptance
- /projects gains a per-Area project page; lab-cluster renders description, latest status, epic rollup, hands queue, and the link graph from live data.
- Weighted numbers on the page match a hand-checked sample (one epic computed by hand from its sub-issues' labels).
- A project with flat, trivial issues reads visibly different from a deep, heavy one.
Metadata
Metadata
Assignees
Labels
Infrastructure, deployment, and operationsLarge: multi-day or open-ended; expect staged check-insNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedFully doable remotely: design, config, code, cloudQueue or user escalation stateHas a queued task in the Supabase agent queueFiled by the new-issue-creator jobQueue or user escalation stateQueue packet kind: verify, reproduce, and route this itemQueue worker lifecycle state
Activity
developing-today commentedon Oct 27, 2026
CODE-247
dezren39 commentedon Oct 27, 2026
Seed note: the Grist 'Program roadmap' table behind the dashboard currently has 6 basement-cluster rows. Reconciling those rows 1:1 with the 12 seeded epics (#1080, #1081, #1083-#1088, #1090-#1093) is part of this page's data work - the Project #4 pool is the source of truth once reconciled; the Grist rows should either mirror it or be retired in its favour, not drift independently.
dezren39 commentedon Oct 29, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 29, 2026
🤖 Agent note · done (triage verdict: CONFIRMED, routed)
39e8410b(2026-10-28). What exists: the Project Bump build/buck/preludes/buck2-prelude from3a02ea3to9530656#4 pool on /projects (pm-stack/aggregator/src/projects.ts, items carry labels/state/area/kind) and a per-project page at /program/lab-cluster (renderProgramProject, registry insrc/project-config.ts, from impl(aggregator): /program hub + /program/<project> pages for all configured projects #1121) — but both render counts only. Verified absent from the aggregator: any effort/* weighting (no weight map xs=1/s=4/m=12/l=40), weighted progress bars, hands-queue weight bymode/*, blocked weight, chain depth, and the epic→sub-issue link graph (the pool query fetches no parent/blocks edges).39e8410b1a23b99c9cb1f93c2ce869830a916c0645 remaining items
dezren39 commentedon Oct 29, 2026
🤖 Agent note · parked — merge queue stall (#1599)
01682ae9, basic check PASS, Codex review completed with no findings — the only blocker is the merge-queue stall tracked in ci: Actions check runs stuck in queued across PRs — no runner pickup since ~05:00Z 2026-10-28 #1599. Parked 20 min.dezren39 commentedon Oct 29, 2026
Slice 1 is code-complete, merge blocked on the repo merge-queue stall (#1599) — 2026-10-29T20:20Z, queue task 3003 (openchamber scheduled lane)
effortWeightxs=1/s=4/m=12/l=40, unsized counted separately, weighted % on/projects,/programcards and per-project + per-Epic blocks, hands queue bymode/*) is implemented and reviewed in PR feat(pm-aggregator): complexity-weighted progress slice 1 (#1108) #2373: CLEAN, required checks green, Codex no findings, hand-checked sample in the PR body.f64d4a6fall green).mainhas not moved since 10:57:51Z. Repo-wide, tracked in ci: Actions check runs stuck in queued across PRs — no runner pickup since ~05:00Z 2026-10-28 #1599.Merge pull request #2373 from developing-today/queue/3003-1108-weight…
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 3003 (small_fix, blocked, priority 30) 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