Maurice 041997e5e6 fix(feed): keep the TZID when a clock already carries seconds ...

fmtDateTime's time-only branch appended '00' for seconds no matter what it was
given. The booking import stores what KItinerary hands it, which is '10:00:00',
so the value came out 17 characters long. dtLine only attaches the TZID to a
well-formed 15-character value, so those events lost their zone and went out as
floating times, which is the #1453 regression by another route.

It pads the way the ISO branch above it already does, so every caller is covered
rather than only the rental markers.

2026-08-13 16:10:25 +02:00

..

e2e

fix: eleven reported bugs across atlas, budget, collections, journey, vacay and the LLM settings (#1923)

2026-08-13 14:06:35 +02:00

fixtures

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

helpers

refactor(server): fold the _shared MCP helpers into an injectable guards provider; delete the last bridge

2026-08-11 23:11:34 +02:00

integration

fix: eleven reported bugs across atlas, budget, collections, journey, vacay and the LLM settings (#1923)

2026-08-13 14:06:35 +02:00

unit

fix(feed): keep the TZID when a clock already carries seconds

2026-08-13 16:10:25 +02:00

websocket

refactor(server): shrink the seam bridges to their live exports

2026-08-11 16:23:46 +02:00

setup.console-noise.ts

refactor(server): fold airports and distance, drop the boot-time backfill cycle (#1834)

2026-08-07 21:07:14 +02:00

setup.ts

Finish the contract ratchet, the upload bridge and the client leftovers

2026-08-10 19:54:46 +02:00