Repository navigation
feat(pm-stack): render flow analytics charts on Projects/Roadmap — time-in-status + throughput with stated windows #4830
Description
Part of #1281 (WIP limits + flow analytics, epic #1184 wave 2) — step 3 of the split recorded by triage task 6839 on 2026-11-03. Depends on #4829 (step 2: flow-analytics computation + JSON twins). Step 1 (WIP caps + violation flags) stays on #1281 itself.
Goal
Render the flow analytics computed by #4829 as charts on the Projects and Roadmap pages, so a project or epic's flow is visible where the work is already reviewed.
Scope
- Time-in-status and weekly throughput charts per project and per epic on the Projects/Roadmap pages, rendering exactly the numbers the feat(pm-stack): flow analytics computation — time-in-status + weekly throughput per project/epic, JSON-first with stated windows #4829 JSON twins expose (no second computation path).
- Every chart states the computation window it was computed over.
- Gappy or incomplete snapshot coverage degrades visibly on the chart (the coverage signal from feat(pm-stack): flow analytics computation — time-in-status + weekly throughput per project/epic, JSON-first with stated windows #4829), never as a silent zero or a smooth line over missing data.
Out of scope
- The analytics computation itself (feat(pm-stack): flow analytics computation — time-in-status + weekly throughput per project/epic, JSON-first with stated windows #4829).
- WIP caps and violation flags (step 1, on feat(pm-stack): WIP limits + flow analytics — per-lane WIP caps with violation flags; time-in-status and throughput charts per project/epic #1281).
Acceptance criteria
- Charts render per project and per epic from the feat(pm-stack): flow analytics computation — time-in-status + weekly throughput per project/epic, JSON-first with stated windows #4829 endpoints, with the computation window stated on each chart.
- Rendered values match the JSON twins for the same window (verified by test or fixture comparison).
- Gap/coverage state from feat(pm-stack): flow analytics computation — time-in-status + weekly throughput per project/epic, JSON-first with stated windows #4829 is visible on the rendered chart.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeMedium: expected under 1 day of workNew feature or capability requestOrdinary priority (the default)Queue task is parked (waiting on CI, time, or an event)Filed or worked by the queue/worker pilotDeliberately paused with a recorded resume conditionQueue packet kind: verify, reproduce, and route this itemQueue worker lifecycle state
Activity
dezren39 commentedon Nov 3, 2026
🤖 Agent note · filed by triage split
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 3, 2026
🤖 Agent note · parked
53 remaining items
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: parked
task: task 6955 (repo-health-code-pilot; worker repo-worker-code; lane code-g)
by: repo-worker-code (lane code-g shift)
at: 2026-11-04T10:29:00Z
state: parked 1800s (not_before 2026-11-04T10:53:37Z); gate revalidated fresh, charts not started
verified: gate issue #4829 is still OPEN (status/blocked, queue/blocked); the flow-analytics JSON twins the #4830 charts render from do not exist yet. Issue #4830 is OPEN with no hard-stop labels.
action: resume when issue #4829 closes; render the charts from its endpoints with stated windows per the packet
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: picked_up
task: task 6955 (repo-health-code-pilot; worker repo-worker-code; lane code-y)
by: repo-worker-code (lane code-y shift)
at: 2026-11-04T11:26:00Z
state: claimed; revalidating gate issue #4829 before starting (packet sequence rule)
verified: issue #4830 OPEN, no hard-stop labels (no held / user/owned / do-not-merge / do-not-auto-edit)
action: if issue #4829 has not landed, park task 6955 with that reason per packet; do not implement the computation here
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: parked
task: task 6955 (repo-health-code-pilot; worker repo-worker-code; lane code-y)
by: repo-worker-code (lane code-y shift)
at: 2026-11-04T11:27:00Z
state: parked 1800s; gate revalidated fresh, charts not started
verified: gate issue #4829 is still OPEN (status/blocked, queue/blocked) at fresh check 2026-11-04T11:25Z; the flow-analytics JSON twins the #4830 charts render from do not exist yet. Issue #4830 is OPEN with no hard-stop labels.
action: resume when issue #4829 closes; render the charts from its endpoints with stated windows per the packet
dezren39 commentedon Nov 4, 2026
task 6955 (queue) picked up by lane code-p and parked in the same pass: the step gate is still closed.
Fresh check 2026-11-04 ~11:56Z: issue #4829 (step 2 — flow analytics computation + JSON twins) is OPEN and its queue work is blocked; no open or merged PR implements issue #4829 (the only related open PR is PR #5182, which is step 1 / issue #1281 WIP caps). Per the task 6955 packet, this step must not start before issue #4829 lands and the computation must not be implemented inside this packet.
Resume condition: issue #4829 closed/landed. task 6955 is parked in the queue with that reason.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked