Repository navigation
Open
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/choreRoutine maintenance, housekeeping, dependency hygieneRoutine maintenance, housekeeping, dependency hygienemeta/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)queue/claimedQueue worker lifecycle stateQueue worker lifecycle statesource/humanFiled directly by a humanFiled directly by a humanstatus/in-progressQueue worker lifecycle stateQueue worker lifecycle statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Description
Finding
Dependency and parentage across the fleet are still mostly text-derived (issue bodies, backlog prose) - the orchestrator derives blockedBy hourly from text + classification (documented in #910 design Q&A), while GitHub offers native sub-issues and blocked-by relations that render in the UI, survive edits, and are API-clean for the collector to consume (see epic-rollups issue).
Proposal
Migration pass for the 16 pool epics: children become native sub-issues of their epic; known dependency pairs become native blocked-by. Orchestrator reconciliation prefers native relations, falling back to text derivation. Record per-epic completion on this issue; the lifecycle protocol doc gets the "new epics use native relations at filing" rule.
Acceptance
- All 16 epics have native sub-issue children (or a recorded exception each).
- One orchestrator run's blockedBy output is shown to match native relations on a sampled chain.
Refs: design+impl: org-level GitHub Project as the conceptual-project layer — orchestrator-synced, dashboard-read #910.
Acceptance criteria
- All 16 pool epics have their children as native GitHub sub-issues (or a recorded exception per epic on this issue) — restating the body's Acceptance section as the criteria section.
- Known dependency pairs across the 16 epics are recorded as native blocked-by relations.
- One orchestrator run's blockedBy output is shown to match the native relations on a sampled chain, with text derivation kept only as fallback.
- Per-epic completion is recorded on this issue, and the lifecycle protocol doc gains the "new epics use native relations at filing" rule.
Metadata
Metadata
Assignees
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/codeeffort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-inskind/choreRoutine maintenance, housekeeping, dependency hygieneRoutine maintenance, housekeeping, dependency hygienemeta/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)queue/claimedQueue worker lifecycle stateQueue worker lifecycle statesource/humanFiled directly by a humanFiled directly by a humanstatus/in-progressQueue worker lifecycle stateQueue worker lifecycle statetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Activity
developing-today commentedon Oct 27, 2026
CODE-302
dezren39 commentedon Oct 28, 2026
Intake review
kind/chore+app/pm-stackbefore this pass.## Acceptancesection; an## Acceptance criteriasection restating it has been appended (original body preserved verbatim above it).priority/normal,effort/l(16-epic migration + verification),source/human,status/needs-triage,meta/enriched.64 remaining items
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
Task 7643 was launched and bound to OpenCode session
ses_e5e5c664809ffeuBevReG3fyo2byopencode-claimant. It is executing asrepo-worker-codeand has the packet, prior triage evidence, and project-scope blocker in its prompt.dezren39 commentedon Nov 3, 2026
🤖 Agent note · triage — STILL LIVE, partially complete
Fresh verification at 2026-11-03T22:58Z: issue #1166 is still open. The repository's current
mainis7a8500417188465deea72339db81fcf1a92c8448(latest commit at 22:55:27Z).Evidence and scope
/issues/1149/sub_issuesand/issues/3142/sub_issuesboth return an empty list. Fresh issue search still finds legacy body-onlyPart of epicreferences under epic(quota-plane): Stage 2 — 15-minute quota gathering in the PM stack, token adapters, automated pool decisions #1149 (feat(quota-plane): plan-store / tracker / measured reconciliation diff (daily) #1270, perf(quota-plane): parallel provider fetching + per-provider timeout budget for the 15-min tick #1268, feat(quota-plane): split gatherer rows per pool — OpenCode Go per-workspace + Antigravity pool grouping for the /quota overlay #1331, feat(quota-plane): quota credential lifecycle — expiry watch, renewal surfacing, per-provider renewal paths #1269, fix(quota-plane): opencode-serve boot verification + quota CLI per-provider resilience (no wholesale transport failure) #1251, feat(quota-plane): Meta adapter Phase 1 — laptop-side quota exporter (subscription-quota API, 15-min file export) #1301) and under Long-term: migrate the pm stack into Supabase — refactor component state into schemas for central management #3142 (pm stack → Supabase phase 1 (#3142): orchestration state into Supabase tables, orchestration.json becomes a generated export #5005–pm stack → Supabase phase 5 (#3142): central management surface — inspect / pause / repair every component's state #5008). The body/native-parent gap therefore remains; pm stack → Supabase phase 1 (#3142): orchestration state into Supabase tables, orchestration.json becomes a generated export #5005–pm stack → Supabase phase 5 (#3142): central management surface — inspect / pause / repair every component's state #5008 are directly identifiable from the Long-term: migrate the pm stack into Supabase — refactor component state into schemas for central management #3142 bodies.dependencies/blocked_byand GraphQLIssue.blockedByreads agree on the sampled chain: id(world): F11.16 replay self-check (id world verify) #544 ← id(roc): F11.18 pin the Roc compiler for checked-in example modules and rebuild them in CI #541, id(roc): F11.18 pin the Roc compiler for checked-in example modules and rebuild them in CI #541 ← id(roc): F11.15 smaller example modules (wasm-opt -Os, strip, <=400 KB) #555, id: validation — Phases 0–8 + platform completion acceptance audit #1075 ← id(ci): F11.4 fast CI lane under 15 minutes #551, id(ci): F11.4 fast CI lane under 15 minutes #551 ← Bulk LogSync test retries a mid-stream reset instead of explaining it #241. Current-mainpm-stack/aggregator/src/projects.tsqueries and maps nativeblockedBy/blockingfields (lines 38, 143–169). This confirms API parity for the sample, but the acceptance still needs an actual orchestrator-output comparison at closeout.planning/templates/epic-intake.md:8andplanning/README.md:65require native sub-issues, with body text only as a readable mirror.Check run at current main
Ran
bun run scripts/check-epic-conformance.tsfrompm-stack/aggregator/using source at7a8500417188465deea72339db81fcf1a92c8448. It exited 1:0/53 conforming; 53 need attention. The audit explicitly skipped Project #4 membership becauseghlacksread:project; this audit checks epic metadata, not native sub-issue completion.Blocker and order
A fresh Project v2 query is denied for missing
read:project, so Project-only child lists cannot be resolved here. Do not infer children or record exceptions without that evidence.read:project, resolve the remaining Project-only epic children and attach native sub-issues, or record an explicit per-epic exception on this issue.No implementation was performed in this triage; #1166 remains the tracker.