Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes

During the 2026-10-30 cutover from muse-dev (nltgxorqwxhgfzseiirt, down in WAL recovery) to muse-dev2 (keihfchslgjetkmnmzra), flipping the canonical Bitwarden supabase.* pointers was NOT sufficient: two fleet tools hardcoded the old project and would have kept hitting the dead instance (supabase-exec returned 403 with the new scoped token against the old ref):

~/tools/supabase-exec.py — REF_DEFAULT = "nltgxorqwxhgfzseiirt" (fixed 2026-10-30: now resolves Bitwarden supabase.project-ref)
~/tools/repo-queue.py — PROJECT_URL = "https://nltgxorqwxhgfzseiirt.supabase.co" (fixed 2026-10-30: now resolves Bitwarden supabase.project-url, new URL kept as fallback)

Related drift found the same day: the Supabase backup config's schemas list omitted engineering (the laptop pg_dump was empirically full-database so no data was lost, but the api transport would have silently skipped that schema).

Ask: audit the remaining fleet tooling (mirror scripts, idea mirror, fleet job bodies, laptop tools) for other hardcoded project refs/URLs or stale schema lists, and convert them to the canonical Bitwarden pointers (supabase.project-ref, supabase.project-url, supabase.service-role-key, supabase.access-token-muse-cli) so the next project move is config-only. Context: code#2767 (fleet queue unreachable during the outage).

Acceptance criteria

A repo-wide audit of fleet tooling (mirror scripts, idea mirror, fleet job bodies, laptop tools) finds every remaining hardcoded old Supabase project ref/URL or stale schema list; each find is either fixed in place or listed on this issue with an owner.
All converted tools resolve the canonical Bitwarden pointers (supabase.project-ref, supabase.project-url, supabase.service-role-key, supabase.access-token-muse-cli) instead of embedded project values.
The two known fixed tools (~/tools/supabase-exec.py, ~/tools/repo-queue.py) are re-verified working against muse-dev2 after the audit.

Cutover-day progress: the audit also found laptop/tools/supabase-mirror/sync_agent_to_turso.py hardcoding the old ref — fixed the same day (now resolves Bitwarden supabase.project-ref; committed in hatch-personal, live laptop copy updated). Remaining audit scope from the issue still stands for other tooling and job bodies.

Intake review

Fleet monitor intake pass (2026-10-30).

Related: Fleet queue unreachable: Supabase PostgREST 503 PGRST002 (schema cache) + 522, 2026-10-30 ~09:19 CDT #2767 / fleet(queue): queue control plane down - PostgREST 400 then 503 PGRST002 / 521, verbs after claim blocked #2768 (the 2026-10-30 queue outage and the muse-dev → muse-dev2 cutover that resolved it). This issue is the follow-up audit those two exposed.
Notes: Still live — verified this run: the queue backend is healthy again on the new project (repo-queue health + live task reads succeed), but the audit itself has not been done; the two named tools were fixed ad hoc during the cutover.
Risks: A missed hardcode stays silent until the next project move or until the old project's data diverges — the failure mode is a tool quietly reading a dead/stale instance.
Suggested approach: Grep the fleet tool dirs and job bodies for the old ref (nltgxorqwxhgfzseiirt) and for supabase.co literals; disposition each hit (convert / intentional-fallback / dead code) on this issue.

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 7363 (triage, queued, priority 50) 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

agent-note:v1
state: picked_up
Found via: OpenChamber scheduled lane
Task: 7363 (repo-health-code-pilot)
Worker: repo-worker-code
Lane: 8ac61616-3815-4e7b-b33d-840a3829154a
Session: ses_e5e5c374d17ffezowNmwt2RE2W
Next: Audit the old Supabase project ref/URL and stale schema lists across fleet tooling, then verify remaining known tools against muse-dev2.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-v
Session / ID: task 7363, cron repo-queue-worker-shift-v run 2026-11-04 05:09 CST
Found via: queue claim
Task: handing task 7363 (triage of issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796, Supabase project-ref audit) back to the opencode execution lane with fresh CI state for PR fix(supabase-export): resolve project ref from Bitwarden #5359
Expectation: the bound opencode session diagnoses the PR fix(supabase-export): resolve project ref from Bitwarden #5359 CI failure — fresh check 2026-11-04T11:47Z: PR fix(supabase-export): resolve project ref from Bitwarden #5359 OPEN at head 33f03ad, contract corpus SUCCESS, aggregator tests and typecheck FAILURE, CodeRabbit NEUTRAL; issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 OPEN
Links: PR fix(supabase-export): resolve project ref from Bitwarden #5359 fix(supabase-export): resolve project ref from Bitwarden #5359

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-a
Session / ID: task 7363
Found via: queue claim
Task: task 7363 (triage for issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796, audit fleet tooling for hardcoded old Supabase project ref/URL) is assigned to the opencode execution lane; handed off to the laptop claimant, which launches the bound opencode session.
Expectation: effort m; done = audit findings posted on issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 against fresh state, with routed follow-up tasks for any remaining hardcodes.
Links: issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796, branch queue/7363-2796-supabase-audit (from prior progress; claimant to verify)

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-i
Session / ID: task 7363
Found via: queue claim
Task: task 7363 (Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 triage, Supabase ref audit) assigned to the opencode execution lane; handing off to the laptop claimant. Re-verified fresh: issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 OPEN with claimed labels in place; PR fix(supabase-export): resolve project ref from Bitwarden #5359 OPEN on branch queue/7363-2796-supabase-audit; CI re-checked — aggregator tests and typecheck FAIL, contract corpus PASS (run 41798739400). The bound session owns diagnosing that failure.
Expectation: claimant launches the bound opencode session and resumes from branch queue/7363-2796-supabase-audit at head 33f03ad.
Links: PR fix(supabase-export): resolve project ref from Bitwarden #5359

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-g
Session / ID: task 7363
Found via: queue claim
Task: task 7363 (triage for issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796) assigned to the opencode execution lane; handing off to the opencode claimant, which launches the bound session that drives task 7363 to its terminal state. Prior state: PR fix(supabase-export): resolve project ref from Bitwarden #5359 is OPEN for issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 with aggregator tests/typecheck failing — the bound session must revalidate fresh, including that PR fix(supabase-export): resolve project ref from Bitwarden #5359 shows author dezren39, before touching it.
Expectation: claimant launches the bound opencode session for task 7363; if unlaunched by lease expiry, task 7363 returns to the queue.
Links: issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796, PR fix(supabase-export): resolve project ref from Bitwarden #5359

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-n
Session / ID: task 7363
Found via: queue claim
Task: Handing task 7363 (triage for issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796, fleet tooling hardcoded old Supabase project ref/URL audit) to the opencode execution lane per the lane assignment; the bound opencode session drives it to a terminal state. Revalidated fresh this claim: issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796 is OPEN with queue/claimed + work/assigned + status/in-progress and no hard-stop labels; PR fix(supabase-export): resolve project ref from Bitwarden #5359 is OPEN at head 33f03ad with checks settled — contract corpus SUCCESS, aggregator tests and typecheck FAILURE, CodeRabbit NEUTRAL — the failure is the bound session's to diagnose. Attempts 24/24 — AT CAP: if the claimant does not finish before this lease expires, task 7363 becomes unclaimable and needs a cap raise.
Expectation: m — claimant launches the bound opencode session and diagnoses the PR fix(supabase-export): resolve project ref from Bitwarden #5359 aggregator tests/typecheck failure.
Links: issue Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796; PR fix(supabase-export): resolve project ref from Bitwarden #5359; queue task 7363

🤖 Agent note · handed off

Agent: fleet monitor
Session / ID: task 7363 (repo-fleet-monitor run 2026-11-05T15:39:47Z)
Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
Task: Claim evaporated: task 7363 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
Expectation: The next lane claim picks task 7363 up from the queued state and posts a fresh pickup note.

Navigation Menu

Repository navigation

Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796

Acceptance criteria

Intake review

24 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Fleet tooling hardcoded the old Supabase project ref/URL — audit for remaining hardcodes #2796

Description

Acceptance criteria

Activity

dezren39 commented on Oct 30, 2026

dezren39 commented on Oct 30, 2026

Intake review

developing-today commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

24 remaining items

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions