[snaketech-tu]

What

Fixes the From and To fields of the time range menu from 0.7.0, and releases 0.7.1 when merged.

Bug 1: typed times were wiped. The menu filled its fields from the range on screen inside an effect that also tracked that range. The range moves with the clock and the store (the oldest stored line), so every few seconds the effect ran again and put both fields and the typed range back. A time being entered vanished before it could be shown. The fields are now filled only when the menu opens.

Bug 2: the date fields were hard to type into. Chromium's datetime-local splits the value into small parts; the year part takes up to six digits, so typing a date and a time in one go never reached the time. From and To are now plain text fields with a calendar button that opens the browser's own picker (showPicker()).

• Type 2026-11-10 08:15, 10.11. 8:15, yesterday 14:00, 14:00 or 2h ago. The line under each field shows how it was read, or "Not a time yet".
• Enter shows the range. Up and down move a minute, Shift an hour.
• An empty To means "until now".

Tests

The 0.7.0 test set the fields with Playwright fill(), which writes the value directly and never waited through a refresh. That is why it passed. New tests:

• From and To are typed key by key in a German locale, the test waits 16 s through the page's refreshes, checks both values are still there, then presses Enter and checks the exact range in the address.
• An empty To runs until now, the arrows move the time, and bad input is refused with a message.
• The calendar button calls the browser picker, and a picked time lands in the field. Headless Chromium draws no picker window, so the pick itself is simulated.

UI tests 36/36 (read-only project included), npm run check clean.

Release

Bumps the version to 0.7.1 (Cargo, ui, desktop) and adds the CHANGELOG section. Merging releases it.