Skip to content

data(pool): converge the three epic-marking conventions (#1122 adoption) #1265

Closed

Description

@dezren39

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

Acceptance

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.

Activity

  1. added
    kind/featureNew feature or capability request
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    source/humanFiled directly by a human
    priority/normalOrdinary priority (the default)
    effort/sSmall: expected under 2 hours of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 28, 2026
  4. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    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.

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  6. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  7. 12 remaining items

  8. added
    user/reviewNeeds a user-look: Muse reviews first and handles what it can
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 1, 2026
  9. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done — epic markers reconciled

  10. added a commit that references this issue on Nov 2, 2026
  11. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  12. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    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

  13. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up → done (already met; closing)

    Triage verdict — acceptance met; no live work remains

    Every acceptance clause is satisfied on current main, so this closes rather than queues another packet:

    1. Three conventions enumerated — the 2026-11-01 reconciliation on this issue records all three (Project Kind=Epic, the epic label, and meta/epic), with before/after sets over the 360-item pool.
    2. Canonical marker chosen and recorded — pm-stack/README.md § GitHub Project Bump build/buck/preludes/buck2-prelude from 3a02ea3 to 9530656 #4 conventions on main: Kind=Epic is canonical; the epic label is the maintained auto-add gate and mirror; meta/epic is 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 as 6c2ab2d14), which was the only remaining step from the prior run.
    3. Pool migrated, nothing legacy kept — the 2026-11-01 audit ended with Kind=Epic 22 ↔ epic 22, epic-label-only 0, Kind-only 0, pool meta/epic 0, and the outliers listed by number. Re-checked now: meta/epic in the code repo is 0 open issues.

    No blocker and no follow-up packet. Closed as completed.

  14. removed
    task/triageQueue packet kind: verify, reproduce, and route this item
    user/reviewNeeds a user-look: Muse reviews first and handles what it can
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/humanFiled directly by a human

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions