refactor(format): hoist the relative-time tiers and lock their invariants

Review follow-ups on the tier-shift fix. The table moves to a module-level RELATIVE_UNITS: it is constant, so rebuilding it per call was pure garbage on a path that runs once per rendered timestamp across a virtualized feed. Its ascending order is load-bearing and was unstated — sorting it largest-first would make every timestamp under a year read "just now", silently, the same shape as the bug this branch fixes. It is now documented and asserted, and the suite derives its tier coverage and translation checks from the table itself rather than from its own case list, so a new tier cannot slip in uncovered. The audit log read the empty string for an unreadable date as a value and rendered a blank cell; it now uses the `|| "—"` idiom the channel table already uses, so missing and unreadable dates look alike.
2026-07-20 22:17:51 +02:00
parent da728f0c5e
commit dea63d8fd2
4 changed files with 48 additions and 25 deletions
@@ -48,7 +48,8 @@ export function auditColumns(
          className="text-muted tabular-nums"
          title={r.created_at ? formatDate(r.created_at, i18n.language) : ""}
        >
-          {r.created_at ? relativeTime(r.created_at) : "—"}
+          {/* `|| "—"` not a null check: relativeTime is empty for a missing OR unreadable date. */}
+          {relativeTime(r.created_at) || "—"}
        </span>
      ),
    },