Repository navigation
Closed
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workSmall: expected under 2 hours of workkind/featureNew feature or capability requestNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)source/humanFiled directly by a humanFiled directly by a human
Description
Summary
Adoption step 5d of the #1122 visualization design: three different conventions currently mark an epic — Project Kind=Epic (18 items), the epic label (14), and meta/epic — and they disagree on ~4 items. Rollups, the depth graph, and epic drill-downs all key off epic-ness; three sources of truth guarantee quiet divergence (the same failure class as the provenance drift in #1110).
Work
- Converge on ONE canonical marker (recommendation from the design: Project Kind=Epic is canonical for pool items, since Area/Status already live there; the
epiclabel remains the auto-add trigger signal the orchestrator reads, and reconciliation keeps the two in agreement). - Reconcile the ~4 outliers; record the final convention where the design+impl: org-level GitHub Project as the conceptual-project layer — orchestrator-synced, dashboard-read #910 conventions live so future epics are born consistent.
Acceptance
- Kind=Epic set == epic-labeled pool set (verified via /api/projects.json + gh), outliers listed and resolved on this issue; convention written down. Refs: impl(aggregator+collector): complexity-weighted project visualization (rollup, hands queue, blocked weight, depth graph) #1122, design+impl: org-level GitHub Project as the conceptual-project layer — orchestrator-synced, dashboard-read #910, impl(aggregator): epic-level rollups - pool has 16 Kind=Epic items but every page renders flat lists #1164.
Acceptance criteria
- The three epic-marking conventions in current use are enumerated.
- One convention is chosen as canonical, with the choice recorded.
- Every pool item is migrated to the canonical convention; no item keeps a legacy epic marking.
Metadata
Metadata
Assignees
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workSmall: expected under 2 hours of workkind/featureNew feature or capability requestNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)source/humanFiled directly by a humanFiled directly by a human
Activity
developing-today commentedon Oct 27, 2026
CODE-389
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (protocol §5), 2026-10-28. Still live: no merged or open PR references this issue (checked 2026-10-28T01:47Z); nothing has implemented it yet.
Related: part of the #1122 adoption wave recorded on epic #1184; siblings #1264 (mode-label backfill) and #1266 (native blocked-by conversion) are the same data-hygiene pass. This one should land first of the three: #1264's backfill needs to know which marking convention is canonical.
Notes / risks: the body's Acceptance line named the outcome (one canonical convention, every item migrated) but not the intermediate steps; the appended criteria add the enumeration + recorded choice so the migration is auditable. Priority normal, effort/s.
Suggested approach: enumerate the three conventions from live pool items, record the canonical choice on this issue, then migrate and verify by label census.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
12 remaining items
dezren39 commentedon Nov 1, 2026
🤖 Agent note · done — epic markers reconciled
pm-stack/README.md#github-project-4-conventions.Kind=Epic↔ 22 currentepiclabels, zero symmetric difference, zero poolmeta/epic; code-repometa/epicsearch now zero.git diff --checkpassed. CodeRabbit review completed neutral; no test CI configured.Merge pull request #3994 from developing-today/queue/4975-1265-epic-m…
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up → done (already met; closing)
7b47536bTriage verdict — acceptance met; no live work remains
Every acceptance clause is satisfied on current
main, so this closes rather than queues another packet:Kind=Epic, theepiclabel, andmeta/epic), with before/after sets over the 360-item pool.pm-stack/README.md§ GitHub Project Bump build/buck/preludes/buck2-prelude from3a02ea3to9530656#4 conventions on main:Kind=Epicis canonical; theepiclabel is the maintained auto-add gate and mirror;meta/epicis retired. That documentation landed as PR docs(pm-stack): record canonical Project epic marker (#1265) #3994 (queue/4975-1265-epic-markers, merged 2026-11-02 as6c2ab2d14), which was the only remaining step from the prior run.Kind=Epic22 ↔epic22, epic-label-only 0, Kind-only 0, poolmeta/epic0, and the outliers listed by number. Re-checked now:meta/epicin the code repo is 0 open issues.No blocker and no follow-up packet. Closed as completed.