Repository navigation
pm stack → Supabase phase 1 (#3142): orchestration state into Supabase tables, orchestration.json becomes a generated export #5005
Description
Phase 1 of epic #3142: orchestration state into Supabase
Part of epic #3142 (Long-term: migrate the pm stack into Supabase). This is the implementation issue for phase 1; phases 3, 4 and 5 are filed separately, and phase 2 already has implementation issues (#1744, with #941 in its area).
Scope
- Move orchestrator tier/classification state and the run log from the local files (
orchestration.json/orchestrator-state.json/orchestrator-log.mdin the goal workspace) into Supabase tables (automation schema or a dedicated pm schema, per the migration plan). orchestration.jsonbecomes a generated export for the dashboard contract — the impl(aggregator): slice 2 — mobile, needs-Drew/needs-orchestrator tiers, time-granular roadmap, session clarity #898 orchestration shape is preserved; only the backing store changes.- Keep the current file-based path working until the DB path is verified, then flip (no big-bang).
Evidence at filing
- Phase 1 is still file-based at current main:
nixos/services/pm-stack/default.nix:238(ORCHESTRATION_PATH) andpm-stack/aggregator/src/server.ts:1563(verified by triage task 8194 at origin/main 8912c83).
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 against phase 2: the phase-2 centralization work in pm stack: centralize all service data as shared tables in one database schema #1744 defines the shared-table conventions this phase follows; coordinate table naming/ownership with pm stack: centralize all service data as shared tables in one database schema #1744 before creating tables. aggregator(dashboard): comment API accepts self-asserted author identities — anyone can post as Drew into the orchestrator/GitHub flow (PR #920) #941 (aggregator comment API identity) is phase-2 area and does not block this phase directly.
Done check
- Orchestrator state + run log are read/written from Supabase in production;
orchestration.jsonon disk is a generated export, not the only copy; dashboard renders the same impl(aggregator): slice 2 — mobile, needs-Drew/needs-orchestrator tiers, time-granular roadmap, session clarity #898 shape from the export.
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.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeLarge: multi-day or open-ended; expect staged check-insIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Filed by the new-issue-creator jobTriaged and routed (see agent note)Queue packet kind: verify, reproduce, and route this item
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 8575 (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).7 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
agent-note:v1
opencode. Handed off to the laptop opencode claimant, which launches the bound session to triage issue pm stack → Supabase phase 1 (#3142): orchestration state into Supabase tables, orchestration.json becomes a generated export #5005 at current main.dezren39 commentedon Nov 4, 2026
agent-note:v1
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: picked_up
task: 8575 (triage, repo-health-code-pilot; repo-worker-code; OpenChamber scheduled lane aea12c82-c5af-4e5a-9b66-f8e360f87177)
session: ses_e5e5b125581ffe5FYJfppHLLtG
state: Claimed for fresh triage. Issue #5005 is OPEN with a complete phase-1 specification, no linked PR, and no hard-stop labels. Parent epic #3142 is OPEN; shared-schema migration plan PR #4881 and schema map PR #4692 are merged. Next: verify P0/P1 migration preconditions, phase-2 conventions/order, and current-main implementation overlap before recording a disposition.
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: triaged
task: 8575 (triage, repo-health-code-pilot; repo-worker-code; OpenChamber scheduled lane aea12c82-c5af-4e5a-9b66-f8e360f87177)
session: ses_e5e5b125581ffe5FYJfppHLLtG
verdict: CONFIRMED live and correctly scoped; no implementation found and no linked PR on #5005.
evidence: Fresh GitHub main is ac14972 (2026-11-04T05:01:15Z). nixos/services/pm-stack/default.nix:259 still sets ORCHESTRATION_PATH to the goal workspace's hidden_files/orchestration.json; pm-stack/aggregator/src/server.ts:1731-1744 still serves /api/orchestration.json via source.orchestration(). Code search for orchestrator-state.json returned no hits. Thus the phase-1 file-backed orchestration state is not migrated at current main. #5005 remains OPEN, with no linked PR. Scope is distinct from siblings #5006 (fleet-feed), #5007 (backlog), and #5008 (management surface), all still OPEN.
blockers/order: #3142 and phase-2 issue #1744 remain OPEN/in-progress; coordinate table naming/ownership with #1744 before creating tables. Migration-plan PR #4881 and schema-map PR #4692 are MERGED, but current pm-stack/SHARED-SCHEMA-MIGRATION-PLAN.md still names P1 target-schema vetting/creation (muse-dev2 table groups and column contracts) as a precondition before flip; no repository evidence verifies those tables/contracts are live, so record that verification on #5005 before cutover. The map and plan still say the pmp_links archive manifest has no backup leg; complete and verify all three backup legs before any migration that touches pmp_links (P0 is registry-specific; this phase is orchestration state). Keep the file-backed path working until DB behavior is demonstrated live, then flip reversibly and retain orchestration.json as generated export.
next: Implementation can proceed as the separately scoped phase-1 slice only after shared-table conventions and target schema are resolved; do not perform the production flip until the issue's P1/live verification is recorded. No code, branch, or worktree changed.
dezren39 commentedon Nov 4, 2026
agent-note:v1
event: done (triaged)
task: 8575 (triage, repo-health-code-pilot; repo-worker-code; OpenChamber scheduled lane aea12c82-c5af-4e5a-9b66-f8e360f87177)
session: ses_e5e5b125581ffe5FYJfppHLLtG
state: Completed triage as CONFIRMED/live and correctly scoped. Current-main evidence and blockers/order are recorded in the triage comment above. No code, branch, or worktree changed.
labels: status/triaged set; queue/claimed, status/in-progress, and work/assigned removed.
resume: Implementation may proceed as the separate phase-1 slice after shared-table conventions/target schema are resolved; record live P1 verification before cutover, and land/verify the P0 pmp_links backup before any link-registry migration.