Repository navigation
data(pool): effort-label backfill for pm-dashboard and id-train pool items (#1122 adoption) #1263
Description
Summary
Adoption step 5b of the #1122 visualization design: effort labels exist in all four repos but coverage is uneven — measured 2026-10-26 against the live pool (188 items): 120/188 (64%) carry effort/*; pm-dashboard is 93% unsized (~40 items) and id-train has ~25 unsized. Unsized weight renders as a separate honest segment in the weighted rollups — but a project that is almost entirely unsized gets almost no weighted signal.
Work
- Backfill effort/* (xs/s/m/l per the spec weights 1/4/12/40) on open pm-dashboard and id-train pool items, sized from issue scope by the orchestrator/reconciliation path or a one-time agent pass recorded here — not by bulk-guessing: each item sized on its own content.
- Priority: epics and
now/nextitems first (they drive the rollup headlines).
Acceptance
- pm-dashboard and id-train unsized counts drop to near zero for open items (report before/after counts from /api/projects.json); spot-check sample of sizes recorded on this issue. Refs: impl(aggregator+collector): complexity-weighted project visualization (rollup, hands queue, blocked weight, depth graph) #1122, design doc §adoption baseline.
Acceptance criteria
- Every open pm-dashboard and id-train pool item carries an effort/* label sized from its own content (xs/s/m/l per the spec weights 1/4/12/40) — no bulk-guessed sizes.
- Before/after unsized counts from /api/projects.json are recorded on this issue, with pm-dashboard's ~93%-unsized baseline driven to near zero.
- Epics and
now/nextitems are sized first; a spot-check sample of the assigned sizes is recorded on this issue.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeSmall: expected under 2 hours of workNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Filed directly by a humanTriaged and routed (see agent note)Queue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-387
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (2026-10-28T02:40:00Z): this issue was missing a
priority/*label and/or the standard## Acceptance criteriasection and was not yetmeta/enriched. The criteria section has been appended to the body (original text preserved verbatim above it) and labels normalized.Related: Design: #1122 (adoption step 5b); sibling step: #1262 (sub-issue inheritance, 5a).
Notes: Data-backfill item with measured baselines in the body (188 pool items, 64% sized; pm-dashboard ~40 items at 93% unsized, id-train ~25 unsized, measured 2026-10-26). Still live: the one merged-PR search hit (PR #926) is an unrelated sops change whose text contains the number — nothing has done this backfill.
Risks: Bulk-guessing sizes would poison the weighted rollups this exists to fix; the per-item sizing is the work, not a shortcut around it.
Suggested approach: One recorded agent pass over the two pools, epics and now/next first, counts posted here before and after.
🤖 Agent note · state: handed off
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
27 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: verified (task 8062)
source: live
http://amd-6.raptor-pumpkinseed.ts.net:4870/api/projects.json, fetched directly during this run; the feed has no generated-at field.Before / after (no label changes were eligible): pm-dashboard: 24 open pool items, 1 unsized; id-train: 38 open pool items, 1 unsized.
Remaining unsized items, left untouched: #1054 (pm-dashboard) is OPEN and
user/owned(hard stop); #183 (id-train) is OPEN withstatus/blocked,queue/blocked,work/assigned, and assignee dezren39. No other open item in these two feed areas is missingeffort/*.Spot-check of existing sizes: #1056 effort/m (pm-dashboard, Week task); #1111 effort/m (pm-dashboard, Month task); #1115 effort/l (pm-dashboard, Month task); #1118 effort/s (pm-dashboard, Week task); #1149 effort/l (pm-dashboard epic). These are pre-existing labels, not assignments made in this pass.
No code or issue labels were changed. The eligible unsized backlog is empty; task 8062 can complete as already_done. #1263 stays OPEN for future pool drift.
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: done (task 8062; outcome already_done)
user/owned) and Phase 5: persisted incremental tag index #183 (queue/blocked,work/assigned), so neither was eligible for this lane to change. Existing size samples and exceptions are recorded in the verification comment above.