impl(fleet/project): adopt native GitHub sub-issues + blocked-by for epic children (16 epics) instead of text-derived links

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.

CODE-302

Intake review

Related: design+impl: org-level GitHub Project as the conceptual-project layer — orchestrator-synced, dashboard-read #910 (design Q&A documenting the text-derived blockedBy derivation this replaces); the epic-rollups work named in the body; parent/dependency data is also consumed by the fleet orchestrator and the collector.
Still live: a merged-PR search found no PR explicitly resolving this issue (no native sub-issues migration has landed); the issue remains open with only kind/chore + app/pm-stack before this pass.
Notes: the body carries an ## Acceptance section; an ## Acceptance criteria section restating it has been appended (original body preserved verbatim above it).
Risks: 16 epics is a wide migration — partial adoption (some epics native, some text-derived) is worse than either alone unless the orchestrator's preference order (native first, text fallback) is verified on the sampled chain before the pass is declared done.
Suggested approach: script the migration per epic (children + blocked-by pairs from the current text derivation), record per-epic completion here as each lands, and finish with the protocol-doc rule so new epics are born native.
Labels normalized by fleet monitor: priority/normal, effort/l (16-epic migration + verification), source/human, status/needs-triage, meta/enriched.

🤖 Agent note · handed off

Agent: fleet monitor
Session / ID: repo-fleet-monitor run 2026-11-05 12:12 CST
Found via: monitor reconciliation
Task: Claim-evaporation repair: this issue carried queue/claimed + work/assigned + status/in-progress, but a fresh queue read this run found NO live task for it in any non-terminal state, and the last activity was 2026-11-03T23:00:32Z. The claim evaporated with no terminal verb. Labels reset to the truth (queue/queued + status/needs-triage) and a fresh triage packet was enqueued as task 10712 — the item is queued, unclaimed.
Expectation: triage (s) by the next claiming lane; checkpoint stage at evaporation: none recorded.
Links: task 10712 (repo-health-code-pilot)

🤖 Agent note · triaged — CONFIRMED, substantially complete; remainder blocked on Project access

Agent: queue worker (repo-worker-code), lane code-i
Session / ID: task 10712 (triage, coverage re-queue of issue impl(fleet/project): adopt native GitHub sub-issues + blocked-by for epic children (16 epics) instead of text-derived links #1166)
Found via: queue claim

Fresh verification (2026-11-05, this triage):

The task 4897 remainder roll-up from 2026-11-01 checks out at current state: the lifecycle protocol carries the filing rule (§11 "Native relations at filing — epics are born native", agent-lifecycle-protocol-2026-10-25.md line 262).
The two sibling owners named in the 2026-11-01 triage are now CLOSED: issue data(cluster): convert cluster epic prose dependencies to native blocked-by edges (#1122 adoption) #1266 (cluster-12 prose dependencies → native blocked-by) and issue data(pool): converge the three epic-marking conventions (#1122 adoption) #1265 (epic-marking conventions).
The sampled aggregator-vs-native blockedBy match on the id: Path to Phase 12 — ordered prerequisite queue (CI trust → validation → journal → visibility → remaining F11) #1235 chain was recorded on this issue by task 4897 (2026-11-01) and the consumption side (aggregator GraphQL blockedBy/blocking) is unchanged in intent.
Migrated epics still hold native children: epic epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184 has 30 native sub-issues (fresh gh api .../sub_issues count).

Sole remainder — BLOCKED on access only Drew can grant:

Epics epic(quota-plane): Stage 2 — 15-minute quota gathering in the PM stack, token adapters, automated pool decisions #1149 and program: finish Tier-2 execution migration to the laptop (unlock: delete sandbox fleet clones) #1723 are still OPEN with 0 native sub-issues (fresh count). Per the task 4897 roll-up, their children need Project/board identification the current gh token cannot read (no read:project scope), and no children were fabricated. Unblocking requires either a token with read:project scope or Drew identifying those epics' children from the Project board; then attaching them as native sub-issues is mechanical.
No new follow-up task is enqueued: the remainder is a single access-blocked attachment pass, fully specified here and in the task 4897 roll-up — another queue task would only re-triage the same blocker.

Verdict: issue #1166 stays OPEN as the tracker for the #1149/#1723 exceptions, exactly as task 4897 left it; everything actionable from the repo side is done. Task 10712 completes as triaged.

Navigation Menu

Repository navigation

impl(fleet/project): adopt native GitHub sub-issues + blocked-by for epic children (16 epics) instead of text-derived links #1166

Finding

Proposal

Acceptance

Acceptance criteria

Intake review

79 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

impl(fleet/project): adopt native GitHub sub-issues + blocked-by for epic children (16 epics) instead of text-derived links #1166

Description

Finding

Proposal

Acceptance

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Oct 28, 2026

Intake review

79 remaining items

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions