[Supabase] Baseball schema drift — 12 columns queried by code are missing in prod DB

[njrini99-code]

Detected by the Mission Control sweep — Supabase postgres logs, 2026-07-01 ~17:40–17:41Z.

The (shared golf-prod) DB is throwing a live cluster of column ... does not exist errors — deployed code is querying columns that don't exist in the database. Root cause is the known pattern: migrations committed but not applied ahead of the code (several current baseball PRs note "migration committed only, not applied").

Missing columns — 12 distinct, ~50 errors in one minute:

• baseball_teams.program_type — ~35×, dominant
• baseball_practice_effectiveness_reviews.disposition
• baseball_practice_effectiveness_reviews.focus_area
• baseball_stat_sources.source_name
• baseball_fielding_events.measured_at
• baseball_fielding_events.chance_difficulty
• baseball_baserunning_events.measured_at
• baseball_baserunning_events.runner_id
• baseball_catching_events.measured_at
• baseball_catching_events.catcher_id
• baseball_plate_appearances.data_context
• baseball_decision_log.detail

Triage (human): verify each column via information_schema (NOT schema_migrations history — unreliable), then apply the missing migrations to prod. Do not auto-apply DDL.

Filed automatically by Mission Control · reads fail gracefully (not a hard outage) but this is a feature-breakage / data-integrity risk.

[coderabbitai]

🔗 Related PRs

#25 - fix(migration): make 037_baseball_missing_tables replay-safe [closed]
#31 - hotfix(coachhelm): P0 sweep — 16 fixes from 2026-05-23 audit [closed]
#38 - Wave 7A: CoachHelm lifecycle cron + index sweep + pattern backlog [closed]
#421 - fix: CodeRabbit-planned GitHub issues batch (#107–#418) [merged]
#517 - fix(baseball): dedup baseball_event_acknowledgements RLS policies (unblocks Supabase CI on main) [merged]
#613 - fix(baseball): add baseball_player_stats.import_run_id (Player Today recent-stats query) (net-new) [merged]
#618 - fix(baseball): coach-notes uses real archived_at/updated_at columns [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[njrini99-code]

🤖 Mission Control — schema-drift recurrence (cluster 3)

The 2-hour sweep (2026-07-02 ~18:31Z) observed 3 more column … does not exist errors on the shared golf-prod Postgres DB — same root cause as this issue (migrations committed-not-applied, code ahead of schema). These columns are not in the original 12 here, nor in cluster 2 (team_members.role / players.jersey_number / games.home_team_id):

• baseball_program_settings.brand_accent — ~17× (2026-07-02 16:55–16:57Z)
• baseball_catching_events.event_type — ~8× (2026-07-02 16:52–16:57Z)
• column p.team_id does not exist (aliased p; likely a baseball players/program join) — 1× (2026-07-02 17:13Z)

Reads fail gracefully (not a hard outage) but this is continued feature-breakage / data-integrity drift. Logged in Notion Incidents as "Baseball schema drift (cluster 3)". Triage unchanged: verify each column via information_schema (not schema_migrations history) and apply the missing migrations to prod — do not auto-apply DDL.

Filed automatically by Mission Control · no new issue opened (folded into this umbrella per dedup).

[njrini99-code]

🤖 Mission Control sweep — 2026-07-03 ~04:03 UTC

This drift is still firing at high volume ~11h after cluster 3 was filed. baseball_program_settings.brand_accent remains the dominant column … does not exist error in the postgres logs — ≥85 occurrences in a 4-min sample (~03:58–04:03 UTC) — surfacing as HTTP 400 on GET /rest/v1/baseball_program_settings?select=brand_accent,appearance_theme. Still Unresolved; the missing migrations have not been applied.

• New column in the same drift class this sweep: baseball_integration_configs.display_name (1×).
• Still present: baseball_catching_events.event_type.

Remediation unchanged (umbrella): verify each column via information_schema, apply the missing migrations to prod — do not auto-apply DDL. Notion incident "cluster 3" updated with fresh last-seen (Events → 110).