Repository navigation
data(cluster): convert cluster epic prose dependencies to native blocked-by edges (#1122 adoption) #1266
Description
Summary
Adoption step 5e of the #1122 visualization design: there are ZERO native blocked-by edges on the sampled epics — every dependency lives as prose in epic bodies (e.g. #1080 "gates epics 5 and 6"). Prose can't feed the blocked-weight and longest-chain views; only 3 items carry even the status/blocked label.
Work
- Convert the stated dependencies in the 12 basement-cluster epics (epic(cluster): hardware inventory & first-node selection #1080–epic(cluster): ESP32 wing #1093) from body prose into native GitHub blocked-by/blocking relationships, keeping the prose (it explains WHY; the edge carries the structure).
- Where a stated dependency has no issue yet, leave the prose and list it here rather than inventing an issue.
Acceptance
- Native edges exist for every prose-stated dependency among the 12 epics (list them on this issue); the impl(aggregator+collector): complexity-weighted project visualization (rollup, hands queue, blocked weight, depth graph) #1122 blocked-weight/longest-chain acceptance can run against real edges. Refs: impl(aggregator+collector): complexity-weighted project visualization (rollup, hands queue, blocked weight, depth graph) #1122, docs(dashboard): build out the Basement cluster project section (/program/lab-cluster) #1124, project-structure spec layer 4.
Acceptance criteria
- Converting the cluster epic's prose dependencies to native blocked-by links is a single action.
- After the conversion, zero of the cluster epic's dependencies exist only as prose.
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 humanQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-390
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; direct siblings #1265 (converge the three epic-marking conventions) and #1264 (mode-label backfill) are the same data-hygiene pass over pool items — the three are cheapest done together, in any order.
Notes / risks: the body's Acceptance line was already precise; the appended section restates it in criteria form. Risk is low and mechanical, but the conversion should use the same link semantics the Project reconciler reads, or the native links will not change reconciliation behaviour. Priority normal, effort/s.
Suggested approach: enumerate the cluster epic's prose dependencies, create the native blocked-by links in one pass, then verify a prose-only count of zero.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · done
blocked_byand zeroblockingedges on every one. Every dependency is prose-only, as filed.6 remaining items
dezren39 commentedon Nov 1, 2026
Attached and verified exactly the 15 native blocked-by edges (blocked <- blocker):
Fresh API reads of blocked_by and blocking across all 12 epics return this exact set, with no extras or missing edges. #1086's body is unchanged (digest verified).
Intentionally no edge for #1091, which is independent and may serve as a witness, or #1093, whose telemetry supports epic 9 but does not gate it. The generic #1080 “feeds every other epic” statement also remains non-structural. No issue bodies or the roadmap were edited.
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:v1
state: done
Resume, not restart: the edge conversion was already completed by queue task 4977 (2026-11-01) and verified again fresh today — the issue was simply never closed. Triaged and closed under queue task 7667 (coverage pass 2026-11-03).
Fresh verification (2026-11-03,
dependencies/blocked_by+dependencies/blockingacross all 12 epics): exactly 15 native edges, no extras, no missing:Reverse reads match (
1080blocks 1081/1084/1085/1086;1087blocks 1088/1090/1092; …), and every edge has a matching prose sentence in the target epic's## Dependenciessection — the "zero dependencies that exist only as prose" criterion holds.Deliberately non-structural, kept as prose (per this issue's own rule: do not invent edges):
Downstream: #1122 (blocked-weight / longest-chain views) is closed and the graph it needed now exists in native form, so its acceptance can be re-run against real edges whenever the next rollup pass happens.
No issue bodies were edited; prose kept (it explains why, the edges carry the structure). Closing as complete.
Found via: queue claim (coverage triage)