-- Intentionally a no-op.
--
-- The plan_id backfill used to live here as a single full-table UPDATE inside
-- drizzle's migration transaction. Because drizzle wraps ALL pending migrations
-- in one transaction, that UPDATE held an AccessExclusiveLock on "recommendation"
-- (from the ADD COLUMN in 0222) for the entire multi-hour run, blocked unrelated
-- migrations behind it, exhausted EBS IO burst balance, and could not report
-- progress or be resumed.
--
-- The backfill now runs OUTSIDE drizzle, in committed batches, via:
--   npm run backfill:recommendation-denormalization
-- See docs/adr/0001-data-backfills-outside-drizzle.md
SELECT 1;
