mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 04:50:59 +00:00
A formatter with no timeZone follows the browser, which is a different question from the one this app answers. Four surfaces had drifted apart that way before anyone noticed, and one of them printed a shared report a day off from the page it came from. The admin host chart went with them rather than onto the allowlist. Server samples are real instants, and an operator reading their own instance should not find a spike at 14:20 here and 15:20 two screens away. Two deliberate limits, both written into the test. It does not match toLocaleString, which in this tree is overwhelmingly a number formatter, and burying four real hits under every thousands separator is how a guard gets silenced. And it cannot tell a Date built from calendar arithmetic — a month label, a weekday header, no instant behind it — from one parsed out of stored data, so those four sites carry a written reason instead. The value is the ratchet: a new bare formatter has to be argued for before it ships.