DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision

Recorded decision: DIY backup `api` transport deliberately omits the Supabase platform schemas

Filed by Lane E (2026-11-07) while killing the backup schema-list trap at the source (#5695 / #6619), so the partial list is a recorded decision rather than a silent gap a future audit can misread.

Facts (verified against the actual 2026-11-06T10:47:11Z pgdump, parsed directly)

The dump contains 16 schemas with COPY tables. The backup config schemas list (now 12) covers every fleet-owned schema: public, agent, ci, ideas, ainventory, engineering, automation, finance, home, research, alerts, cron.

The four schemas NOT in the list are Supabase platform schemas. In the dump, every user-facing table in them is empty; the only nonzero tables are platform bookkeeping:

schema	nonzero tables in dump	user tables
auth	auth.schema_migrations (82)	all 0 rows (users, sessions, identities, ...)
storage	storage.migrations (80)	all 0 rows (buckets, objects, ...)
realtime	realtime.schema_migrations (91)	subscription 0 rows
vault	(vault.secrets 0)	0 rows

Semantics (the part that was misread before)

The pgdump transport ignores the schemas list entirely (pg_dump runs with no --schema flag; full-database dumps) — platform schemas ARE in every pgdump backup regardless of the list.
The api transport (sandbox) filters its DDL/row/sequence exports by the list, so api-transport backups do not carry these four schemas. That is deliberate: they are platform-managed, hold no fleet data, and are left behind at decommission per the migration program disposition.

Decision

Keep the exclusion. If a future change ever needs api-transport coverage of a platform schema, amend the list and this record in the same pass — do not infer coverage from the list for pgdump backups, and do not treat the api list as the backup-coverage statement for the fleet.

Acceptance criteria

This recorded decision stays the reference for backup schema coverage: the api transport list (12 fleet-owned schemas) deliberately excludes the Supabase platform schemas auth/storage/realtime/vault.
Any future change that needs api-transport coverage of a platform schema amends the list and this record in the same pass.
No code change is required by this issue itself; it closes when the decision record is acknowledged in the backup/migration documentation it informs.

CODE-2184

Intake review

Related: issue design: move tiny config/KV tables (sources registries, public.muse_notes) from Supabase to D1 — gated on §9.4 Q2 #5695 / issue infra: repo-queue PostgREST timeout: global failures lane-visible again — recurrence after #6450 closed (2026-11-06 21:15-21:31Z) #6619 (the backup schema-list trap this record was filed while killing).
Notes: Decision record, not a defect: facts were verified by the filer against the 2026-11-06 pgdump (16 schemas; the four excluded platform schemas hold no fleet data). The key semantics — pgdump ignores the list, api transport filters by it — are stated in the body.
Risks: A future audit misreading the api list as total backup coverage; this record exists to prevent exactly that.
Suggested approach: No implementation work; keep as the citable decision record and reference it from backup coverage audits.
Acceptance criteria appended by the fleet monitor intake pass; meta/enriched applied.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code, lane code-l)
Session / ID: task 11433
Found via: queue claim
Task: Triage issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 — assigned_lane=opencode; handed off to the opencode claimant, which launches the bound session.
Expectation: claimant session drives task 11433 to its terminal state.
Links: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off

Agent: repo-worker-code-o (lane code-o)
Task: task 11433 (triage, issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 — DIY backup api transport platform-schema exclusion, recorded decision) — execution-lane assignment is opencode (§1b); handed off to the claimant.
Next: claimant session records the triage verdict on issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 per the packet acceptance.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-q
Session / ID: task 11433
Found via: queue claim; execution-lane assignment returned opencode
Task: Triage for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (DIY backup api transport: platform schemas deliberately excluded — recorded decision). Revalidated fresh 2026-11-08T02:13Z via REST: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 OPEN with no hard-stop labels. Handed off to the opencode claimant per the execution-lane assignment; this lane did not work it directly.
Expectation: claimant launches the bound opencode session; task 11433 parked 20 minutes for the claimant to bind.
Links: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

Agent note — handed off (task 11433)

Lane code-c claimed task 11433 (triage, issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935); execution-lane assignment returned assigned_lane=opencode.
Checkpointed handed_off; claimant launches the bound opencode session. This lane does not work the task directly.

🤖 Agent note · handed off

Agent: repo queue worker, lane code-u (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-u run 2026-11-08 14:24 CST; task 11433
Found via: queue claim · task 11433
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (verified via App-token read). Execution-lane assignment returned opencode - handed off to the opencode claimant, which launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state. Attempts 10/12.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off

Agent: repo queue worker, lane code-w (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-w run 2026-11-08; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage — DIY backup api transport: platform schemas deliberately excluded, recorded decision). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Prior verdict on the checkpoint: record confirmed accurate; acknowledgment step outstanding; no code change wanted. Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off (second handoff)

Agent: queue worker (repo-worker-code), lane code-l
Session / ID: task 11433
Found via: queue claim
Task: Triage of issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (DIY backup api transport: platform schemas) — execution-lane assignment returned opencode again, so this task is handed off to the laptop opencode claimant a second time (previous handoff: earlier lane code-l shift, note 6726505483 on issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935; the park expired without a bound session driving it).
Expectation: the claimant's bound session performs the triage and drives task 11433 to its terminal state under this queue's worker id.
Links: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (open, no held/user/owned/do-not-merge/do-not-auto-edit labels — verified fresh this shift)

🤖 Agent note · handed off

Agent: repo queue worker, lane code-v (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-v run 2026-11-08; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state. Attempts 10/12.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-y
Session / ID: task 11433
Found via: queue claim
Task: Handing task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 to the opencode claimant — execution lane assigned opencode per fleet queue lane; issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 re-verified OPEN with no held / user/owned / do-not-merge / do-not-auto-edit labels.
Expectation: claimant launches the bound opencode session and drives task 11433 to a terminal state.
Links: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 11433
Found via: queue claim
Task: Handed off to opencode claimant per §1b lane assignment (assigned_lane=opencode); worker does not work this task directly. Posted via developing.today App (gh user token repeatedly secondary-rate-limited this shift).
Expectation: claimant launches the bound opencode session for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935
Links: task 11433

🤖 Agent note · handed off

Agent: repo queue worker, lane code-x (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-x run 2026-11-08; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels verified this shift. Handed off to the opencode claimant; this lane does not work it directly. (User-token comment hit GitHub's secondary rate limit; posted via the developing.today GitHub App per the rate-limit fallback order.)
Expectation: claimant session drives task 11433 to a terminal state.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

agent-note:v1 - task 11433 (queue repo-health-code-pilot), lane code-t - stage: handed_off - #6935 revalidated fresh via REST: open, no hard-stop labels. Execution lane opencode; handed off to laptop opencode claimant and parked 1200s. Next: claimant works task 11433 to terminal state.

🤖 Agent note · handed off

Agent: repo queue worker, lane code-v (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-v run 2026-11-08; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 OPEN, no hard-stop labels (verified this shift via REST); prior verified evidence stands in task progress. Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

agent-note:v1 - task 11433 (queue repo-health-code-pilot), lane code-t - stage: handed_off - #6935 revalidated fresh via REST: open, no hard-stop labels. Execution lane opencode; handed off to laptop opencode claimant and parked 1200s. Next: claimant works task 11433 to terminal state.

🤖 Agent note · handed off

Agent: repo queue worker, lane code-e (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-e run 2026-11-08; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Attempts 10/12. PR: none; branch queue/11433-6935-diy-backup-api-transport per packet progress. Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

🤖 Agent note · handed off

Agent: repo queue worker, lane code-m (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-m run 2026-11-08 18:42 CST; task 11433
Found via: claimed task 11433 this shift; execution-lane assignment returned opencode
Task: Claimed task 11433 (triage) for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (attempt 10/12). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Handed off to the opencode claimant — the claimant launches the bound opencode session; this lane does not work it directly. Task 11433 parked 1200s in the same pass.
Expectation: claimant session drives task 11433 to a terminal state.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

agent-note:v1
task: 11433
lane: code-b
state: handed_off
summary: Claimed by lane code-b 2026-11-09T01:26Z; execution lane assignment is opencode. Issue #6935 verified OPEN fresh, no hard-stop labels; existing branch queue/11433-6935-diy-backup-api-transport and worktree ~/git/fleet/11433 noted from prior progress. Handing off per runbook 1b; parked 1200s. This was the 20th and final task of lane code-b's bundle this shift.
next: opencode claimant launches bound session for task 11433 (triage of #6935 DIY backup api transport schemas).

🤖 Agent note · handed off

Agent: repo queue worker, lane code-j (repo-worker-code)
Session / ID: cron repo-queue-worker-shift-j run 2026-11-08 19:10 CST; task 11433
Found via: queue claim · task 11433
Task: task 11433 for issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 (triage). Fresh check: issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit). Prior-session verdict stands in the task progress: CONFIRMED, record accurate, no code change wanted; close condition is tied to issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976 landing doc/backups. Execution-lane assignment returned opencode - handed off to the opencode claimant, which launches the bound opencode session; this lane does not work it directly.
Expectation: claimant session drives task 11433 to a terminal state. Attempts 10/12.
Links: task 11433 · issue DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935 · issue Docs migration batch: backup scripts & backup documentation (hatch → code) #5976

Triage verdict: CONFIRMED

Re-verified against current �[1morigin/main�[0m (a97c23c, 2026-11-08): �[1mdoc/fleet/queue-turso-cutover.md:358-363�[0m still records the four Supabase platform schemas (41 tables) as RETIRE with no fleet consumer; �[1mdoc/2026-10-11_design_atlas_scaler_revision/...:631�[0m carries the same disposition. The issue thread's pgdump-vs-api transport distinction is consistent: no code change is warranted.

The acceptance acknowledgment is still outstanding: �[1mdoc/backups/�[0m is absent from current main, and issue #5976 remains open for the backup docs migration (task 10506). Keep #6935 open until that migration lands and its backup docs cite this decision; then close #6935 pointing to the canonical documentation. No small_fix packet is appropriate for this decision-only triage.

Navigation Menu

Repository navigation

DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

Recorded decision: DIY backup `api` transport deliberately omits the Supabase platform schemas

Facts (verified against the actual 2026-11-06T10:47:11Z pgdump, parsed directly)

Semantics (the part that was misread before)

Decision

Acceptance criteria

Intake review

102 remaining items

Triage verdict: CONFIRMED

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

DIY backup api transport: platform schemas (auth/storage/realtime/vault) deliberately excluded — recorded decision #6935

Description

Recorded decision: DIY backup api transport deliberately omits the Supabase platform schemas

Facts (verified against the actual 2026-11-06T10:47:11Z pgdump, parsed directly)

Semantics (the part that was misread before)

Decision

Acceptance criteria

Activity

developing-today commented on Nov 7, 2026

dezren39 commented on Nov 7, 2026

Intake review

developing-today commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

102 remaining items

developing-today commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

dezren39 commented on Nov 8, 2026

developing-today commented on Nov 8, 2026

dezren39 commented on Nov 9, 2026

developing-today commented on Nov 9, 2026

developing-today commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

dezren39 commented on Nov 9, 2026

Triage verdict: CONFIRMED

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Recorded decision: DIY backup `api` transport deliberately omits the Supabase platform schemas