-- Intentionally a no-op.
--
-- The materials backfill (material_id + quantity/unit/depth) used to live here as
-- a single full-table UPDATE inside drizzle's migration transaction, with the
-- material_id index created BEFORE the backfill in 0224 — so every updated row
-- also had to maintain that index. It moved out for the same reasons as the
-- plan_id backfill (see 0223).
--
-- 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;
