Repository navigation
impl(orchestrator): sub-issue Area/Status inheritance in Project reconciliation (#1122 adoption) #1262
Description
Summary
Adoption step 5a of the #1122 visualization design (~/workspace/pm-stack-visualization-design-2026-10-26.md): the 13 native sub-issues of the basement-cluster epics (#1094–#1106, children of #1080/#1081/#1083) sit in org Project #4 with Area=null and Status=null. The aggregator's effectiveArea inheritance (design step 1–3) makes them count toward lab-cluster at render time, but the Project's own data should eventually agree — board views, filters, and any other consumer still can't see them.
Work
- Extend the orchestrator's hourly reconciliation (single writer for Project Bump build/buck/preludes/buck2-prelude from
3a02ea3to9530656#4) so a pool item with a native parent inherits Area (and is checked for Status) from its parent epic, unless it carries its own explicit Area. - Idempotent, label/convention-driven like the existing auto-add; never overwrite an explicit Area.
- Verify on the 13 known children first: after one reconciliation run, task(cluster): design the hardware inventory record (schema + template) #1094–task(cluster): basement cleanup + rack layout for the first nodes #1106 show Area=lab-cluster in the Project (cross-check GraphQL vs /api/projects.json).
Acceptance
- Reconciliation change live; the 13 children carry inherited Area; a newly added sub-issue of any epic inherits on the next run; explicit Areas are never clobbered. 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, design doc §adoption.
Acceptance criteria
- The orchestrator's Project Bump build/buck/preludes/buck2-prelude from
3a02ea3to9530656#4 reconciliation inherits Area from a native parent epic for pool items that carry no explicit Area, and checks Status the same way — idempotently, on the normal hourly run. - After one reconciliation run, the 13 known basement-cluster children (task(cluster): design the hardware inventory record (schema + template) #1094–task(cluster): basement cleanup + rack layout for the first nodes #1106) show Area=lab-cluster in Project Bump build/buck/preludes/buck2-prelude from
3a02ea3to9530656#4, cross-checked via GraphQL and /api/projects.json. - A newly added sub-issue of any epic inherits on the next run; an explicit Area on a child is never overwritten.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeMedium: expected under 1 day of workNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Queue or user escalation stateHas a queued task in the Supabase agent queueFiled directly by a humanQueue or user escalation stateQueue or user escalation state
Activity
developing-today commentedon Oct 27, 2026
CODE-386
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (2026-10-28T02:40:00Z): this issue was missing a
priority/*label and/or the standard## Acceptance criteriasection and was not yetmeta/enriched. The criteria section has been appended to the body (original text preserved verbatim above it) and labels normalized.Related: Design: #1122 (visualization design, adoption step 5a); sibling adoption step: #1263 (effort backfill, 5b). Parent epics: #1080/#1081/#1083; children: #1094–#1106.
Notes: Implementation (not design) item from the #1122 adoption series. Still live: no merged PR references it (search this run: 0). Note the standing fleet context: the org Project reconcile has been timing out in recent orchestrator passes (filed as #1408) — that timeout may gate the verification step here and is worth checking first.
Risks: Project #4 is single-writer (the orchestrator); the change must stay inside that writer and remain idempotent, or board data and aggregator renders will diverge.
Suggested approach: Extend the reconciliation's existing auto-add path with parent-Area inheritance, verify on the 13 named children first, then let the general rule run.
🤖 Agent note · state: handed off
dezren39 commentedon Nov 1, 2026
🤖 Agent note · triaged — CONFIRMED live; follow-up task 4974 enqueued
/api/projects.json— the aggregator's own Project pool read): all 13 children task(cluster): design the hardware inventory record (schema + template) #1094–task(cluster): basement cleanup + rack layout for the first nodes #1106 have Area = null; parents epic(cluster): hardware inventory & first-node selection #1080/epic(cluster): firmware / BIOS / BMC audit & standardization #1081/epic(cluster): basement power & space #1083 all carry Area = lab-cluster. The children do carry Status (Todo/Done), so the reconciliation pass writes Status but has no Area-inheritance step — exactly the gap this issue names. (ghCLI cannot read Project Bump build/buck/preludes/buck2-prelude from3a02ea3to9530656#4 directly from this token — missingread:projectscope — so the aggregator pool read is the evidence surface; it is also the follow-up's verification surface.)effectiveArearender-time inheritance from design steps 1–3 — noeffectiveAreasymbol exists anywhere in the repo at current main (grep, zero hits). The follow-up first locates where render-time inheritance actually lives (or establishes its absence) so the write-side rule mirrors it: explicit Area always wins.program.ts:77), plus the Status consistency check; proof = one pass makes the 13 children read lab-cluster, a second pass changes nothing. This issue stays open as the tracker.dezren39 commentedon Nov 1, 2026
🤖 Agent note · state: picked up
ses_e5e671686ccffeQbtUrJqbsWZM, queue task 4974dezren39 commentedon Nov 1, 2026
🤖 Agent note · state: blocked / escalated
ses_e5e671686ccffeQbtUrJqbsWZM, queue task 497470a595a7735c208ccbb1ad0de115b3156cd572d4, the code repo has no Project reconciliation implementation; its Project pool code is read-only. The sole writer is/home/user/hatch-personal/workspace/goals/keep-the-four-repos-healthy/hidden_files/project-reconcile.sh, outside this repo, and its header reserves--applyto the orchestrator.developing-today commentedon Nov 3, 2026
🤖 Agent note · blocked / escalated
user/escalated+queue/blocked+status/blockedfrom the task 4974 escalation (2026-11-01, comment 6564012531): the sole Project-reconciliation writer isproject-reconcile.shoutside this repo and its--applyis reserved to the orchestrator. Task 6838 blocked with reason classescalated-to-user; the decision (where Area/Status inheritance lives / who may write) is Drew's.