Apply migration 00033 (oracle columns on formulacode_task_overrides) to production #71

Problem

Migration supabase/migrations/00033_task_overrides_oracle_columns.sql is in main (commit 33bebfa, from #29), but it is not applied to the production database.

• A query for the column fails: column formulacode_task_overrides.oracle_speedup does not exist (PostgREST error 42703, checked on 2026-10-20).
• No code on main reads or writes these columns yet. The oracle_speedup names in docker/templates/parser.py are local variables, not database columns. So nothing fails today.
• The schema in main and the schema in production are different. The first code that stores oracle results in the database will fail until the migration runs.

What the migration does

It adds 5 nullable columns to formulacode_task_overrides and one check constraint. It is additive and safe to run again (add column if not exists, and the constraint is added only when it is missing):

alter table formulacode_task_overrides
  add column if not exists oracle_speedup     double precision,
  add column if not exists oracle_trust       text,
  add column if not exists oracle_benchmarks  jsonb,
  add column if not exists oracle_provenance  jsonb,
  add column if not exists oracle_measured_at timestamptz;
-- plus: check constraint fto_oracle_trust_check (oracle_trust in 'trusted', 'marginal', 'untrusted', or null)

Request

1. Apply 00033_task_overrides_oracle_columns.sql to production with the usual migration process. The REST API cannot run schema changes; use the Supabase SQL editor or supabase db push.
2. Check the result with a select on the new columns:

   GET /rest/v1/formulacode_task_overrides?select=oracle_speedup,oracle_trust,oracle_benchmarks,oracle_provenance,oracle_measured_at&limit=1
   

Related

• migrations: add 00031 lsv_baseline_cache, which production already has #70 adds 00031_lsv_baseline_cache.sql to main. Production already has that table, so migrations: add 00031 lsv_baseline_cache, which production already has #70 changes only files.
• Other migrations exist only on branch lsv-cache (00016 to 00019, 00032 lsv_deps_cache). Production does not have lsv_deps_cache, and no code on main uses it, so nothing is needed for them.