feat: pivot config to Sanity singletons (Phase A)

[codercatdev]

Phase A: Pivot Config to Sanity Singletons

Replaces the Supabase config tables approach with Sanity singleton documents. Alex already lives in Sanity Studio — config editing is free, changes propagate instantly via Live Content API, and no new infrastructure needed.

Changes (+519 / -487, 11 files)

6 new Sanity singleton schemas in sanity/schemas/singletons/:

Schema	Fields	Key Defaults
pipelineConfig	8	geminiModel='gemini-2.0-flash', qualityThreshold=50, visibility='private'
remotionConfig	6	awsRegion='us-east-1', timeout=240s, memory=2048MB
contentConfig	7	8 RSS feeds, Cleo Abram system instruction, 3-5 scenes
sponsorConfig	4	cooldown=14d, 3 rate card tiers, email template
distributionConfig	4	notification emails, YouTube template + tags
gcsConfig	2	bucket + project ID

Rewrote lib/config.ts — Sanity writeClient.fetch instead of Supabase. Same API surface (getConfig, getConfigValue, invalidateConfig), same 5-min stale-while-revalidate caching.

Updated lib/types/config.ts — camelCase field names, _id/_type/_updatedAt instead of id/updated_at.

Registered all 6 singletons in sanity.config.ts schema.types + singletonPlugin().

Removed:

• supabase/migrations/003_config_tables.sql (no longer needed)
• app/api/dashboard/config/invalidate/route.ts (Sanity handles propagation)

Type check

Zero new TS errors. Only pre-existing: sanity-plugin-media, @vercel/analytics, @vercel/speed-insights.

Why Sanity over Supabase

• Alex already lives in Sanity Studio — config editing for free
• Instant propagation via Live Content API (no 5-min cache delay)
• Follows existing dashboardSettings singleton pattern
• Keeps Supabase focused on auth + cron

Closes Phase A task for spec MBYYpe5Y.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
codingcat-dev	Ignored		Mar 5, 2026 5:40am