Repository navigation
pm stack → Supabase phase 5 (#3142): central management surface — inspect / pause / repair every component's state #5008
Description
Phase 5 of epic #3142: central management surface — inspect / pause / repair
Part of epic #3142 (Long-term: migrate the pm stack into Supabase). This is the implementation issue for the phase 5 inspect/pause/repair surface; phases 1, 3 and 4 are filed separately, and phase 2 already has implementation issues (#1744, with #941 in its area).
Scope
- One central management surface over the migrated component state: one schema map (
pm-stack/SHARED-SCHEMA-MAP.md) and one place to inspect, pause, and repair every pm-stack component's state (aggregator, fleet feed, dashboard, orchestration, dispatch, usage hub). - Pause/repair actions respect the existing single-writer rules per component/table.
Dependencies / blocked-by
- Blocked by the merged migration plan preconditions in
pm-stack/SHARED-SCHEMA-MIGRATION-PLAN.md(PR pm-stack: per-service migration plan for the shared schema (#1744 slice 2) #4881): P0 — pmp_links backup legs in place and P1 — target schema vetted againstpm-stack/SHARED-SCHEMA-MAP.md(PR docs(pm-stack): shared-schema inventory + schema map, slice 1 of #1744 #4692). - Ordering: this surface is only meaningful over migrated state, so it follows phases 1–4 — phase 2 (pm stack: centralize all service data as shared tables in one database schema #1744 aggregator stores / shared tables; aggregator(dashboard): comment API accepts self-asserted author identities — anyone can post as Drew into the orchestrator/GitHub flow (PR #920) #941 is in the phase-2 aggregator area), phase 1 (orchestration state), phase 3 (feed DB-first), and phase 4 (backlogs as a view). It is the last phase to start.
Done check
- From one place, an operator can inspect each component's current state, pause it, and perform the documented repair actions, with the schema map at
pm-stack/SHARED-SCHEMA-MAP.mdmatching the live tables.
Acceptance criteria
- The phase's "Done check" in the body above is met and demonstrated against live state (not just code-merged): the before/after behavior is shown on the running pm stack.
- The migration plan preconditions the body names (P0 — pmp_links backup legs in place; P1 — target schema vetted against
pm-stack/SHARED-SCHEMA-MAP.md) are verified in place before the flip, and the verification is recorded on this issue. - The file-based path keeps working until the DB path is verified; the flip is reversible and no big-bang cutover is required.
Activity
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8576 (triage, queued, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
Intake review
Fleet monitor intake (Duty 2), 2026-11-03. (Posted on a delayed retry: the original comment attempts were rejected by a GitHub secondary rate limit; the label/body enrichment itself landed during the run.)
pm-stack/SHARED-SCHEMA-MIGRATION-PLAN.md(PR pm-stack: per-service migration plan for the shared schema (#1744 slice 2) #4881) andpm-stack/SHARED-SCHEMA-MAP.md(PR docs(pm-stack): shared-schema inventory + schema map, slice 1 of #1744 #4692).dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done
Triage findings (verified fresh 2026-11-03 ~20:26Z)
pm-stack/SHARED-SCHEMA-MAP.md(PR docs(pm-stack): shared-schema inventory + schema map, slice 1 of #1744 #4692, merged) andpm-stack/SHARED-SCHEMA-MIGRATION-PLAN.md(PR pm-stack: per-service migration plan for the shared schema (#1744 slice 2) #4881, merged) both exist on current main. Those merges satisfy the "plan filed" precondition only — the operational preconditions P0 (pmp_links backup legs in place) and P1 (target schema vetted against the schema map) are not yet verified on this issue, and per the acceptance criteria that verification belongs to the phase-5 start, not before the state exists.