Pulse v1.4.3 — Exit crash fix, custom date range

A small update with fixes reported after 1.4.2.

New

Custom date range in the Timeline (#15). The date filter has a Custom… option: pick a from / to date and time in local time. The range includes the whole "to" minute, works with the other filters, shows on the filter chip (for example 18 Oct 14:05 – 18 Oct 15:30) and is kept in saved searches.
Assistant replies render Markdown. Local models answer in Markdown, and the panel showed it raw. Bold, italic, inline code, headings, lists and code blocks now render. Links are shown as text and are not clickable.

No more crash on exit (#32). When Pulse closed, Windows could send one last message to the Flutter view that was being destroyed, which crashed in flutter_windows.dll and left an Application Error in the event log. The view is now detached before it is destroyed.
Resizable BAR shows Unknown (#31). Windows has no documented way to read it, so Pulse never did, but the GPU panel said "Not supported", which read as "this GPU lacks it". It now says Unknown and points to the GPU maker's control panel.
Enter sends in the Assistant. Enter inserted a new line, so messages could only be sent with the button. Enter now sends; Shift+Enter adds a line.
Clean uninstall. A Pulse running in the tray kept running after Control Panel → Uninstall, and its files stayed until the next restart. The uninstaller now closes the Pulse from its install folder first; copies elsewhere are left alone.
"Pulse" in Task Manager. The app was listed as "Windows Diagnostics", which looked like part of Windows.
Power-on time. The disk health row is labelled Power-on time instead of "Power-On Hours", since it shows days and hours.

Windows x64 Installer

Pulse-Setup-1.4.3-windows-x64.exe

Payload ZIP

Pulse-1.4.3-windows-x64.zip (PulseService is still required; see portable vs service)

Checksums

SHA256SUMS.txt

Pulse remains read-only and local-first: no telemetry, no cloud, no account.