-- #160: the filename wall-clock patterns had no year gate, so counters and
-- IDs shaped like YYYYMMDD_HHMMSS (`VID_22290524_080551.mp4`, Facebook's
-- `10530519_101527…_o.jpg`) became dates of record in years like 1053 and
-- 2229. The matcher now rejects years outside 1995..=now+1; this clears
-- the rows it already dated so they're re-resolved by the fixed waterfall.
--
-- Both the legacy pair and the new-contract triple are cleared:
-- `date_taken IS NULL` puts the row back in `backfill_missing_date_taken`,
-- which rewrites all five columns (EXIF / exiftool / fs_time now that the
-- filename no longer matches). Only filename-sourced rows dated outside
-- [1995-01-01, 2028-01-01) UTC are touched; a real date re-resolves to
-- itself anyway.
UPDATE image_exif
SET date_taken = NULL,
    date_taken_source = NULL,
    date_utc = NULL,
    camera_offset_minutes = NULL,
    date_taken_tz_source = NULL
WHERE date_taken_source = 'filename'
  AND (
    date_taken < 788918400 OR date_taken >= 1830297600
    OR date_utc < 788918400 OR date_utc >= 1830297600
  );