b52bf60913
Some checks failed
CI / Unit & Component Tests (pull_request) Failing after 3m2s
CI / OCR Service Tests (pull_request) Successful in 24s
CI / Backend Unit Tests (pull_request) Failing after 3m54s
CI / fail2ban Regex (pull_request) Successful in 47s
CI / Semgrep Security Scan (pull_request) Successful in 20s
CI / Compose Bucket Idempotency (pull_request) Successful in 1m6s
Owner decision (#668): when two documents share a meta_date, order them by title ascending instead of createdAt ascending. title is @Column(nullable=false) so it is always present, giving a deterministic, human-meaningful total order. Only the DATE-sort fast path changes; the in-memory SENDER/RECEIVER/RELEVANCE comparators are untouched. ORDER BY meta_date <dir> NULLS LAST, title ASC Tests assert title-asc tiebreaking for same-date rows in BOTH directions, with a fixture whose title order is the OPPOSITE of insertion (createdAt) order so the test fails if the tiebreaker reverts to createdAt. The integration test drives the production resolveSort against real Postgres. Refs #668