f6bf7b9f5e
Some checks failed
CI / Unit & Component Tests (pull_request) Failing after 1m18s
CI / OCR Service Tests (pull_request) Successful in 20s
CI / Backend Unit Tests (pull_request) Successful in 3m27s
CI / fail2ban Regex (pull_request) Successful in 43s
CI / Semgrep Security Scan (pull_request) Successful in 20s
CI / Compose Bucket Idempotency (pull_request) Successful in 1m2s
The V69 migration added documents.meta_date_precision as NOT NULL with no DB default. Raw-SQL inserts that omit the column (test fixtures, ad-hoc loads) hit a not-null violation — 33 backend CI errors all reading "null value in column meta_date_precision ... violates not-null constraint". Add DEFAULT 'UNKNOWN' to the ADD COLUMN so omitting-column inserts get a sane, CHECK-valid value. Existing rows still get backfilled (DAY when meta_date present, else UNKNOWN) before SET NOT NULL; CHECK constraints unchanged. Entity already sets it via @Builder.Default = DatePrecision.UNKNOWN, so JPA saves stay consistent. Editing V69 in place is safe: unmerged, no shared DB has applied it. Refs #671