feat(ui): absolute date/time window picker (#26)

[leo-aa88]

Closes #26

The web UI time window selector only supported relative durations (since / presets). /v1/query/explain, /timeline, /ask, and /compare already accept absolute bounds.

This adds a Relative / Absolute toggle on each .window-form. Relative stays the default. Absolute mode uses datetime-local inputs and sends ISO-8601 UTC:

• Explain / Timeline / Ask: from_time / to_time instead of since
• Compare: window_a_from / window_a_to / window_b_from / window_b_to instead of since + baseline

CLI window flags are unchanged.

  

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[cursor]

Review — PR #52 (UI absolute window)

Acceptance holds: each of the four .window-forms toggles Relative (default, presets/since) vs Absolute (datetime-local). Absolute maps Explain/Timeline/Ask to from_time/to_time and Compare to window_a_*/window_b_*. Unused mode fields are disabled, so FormData cannot send since together with absolute bounds. CLI is untouched. datetime-local is labeled UTC and tagged with Z (known tradeoff). Related unit tests passed (809).

Must-fix

(None)

Should-fix

(None)

Nice-to-have

• JS checks do not lock applyWindowMode disabling relative since/baseline. A regression that only hides those inputs would put both since and from_time in the body.
• datetimeLocalToIso leaves YYYY-MM-DDTHH:MM:SS.sss unchanged (no Z). Default datetime-local is minute precision, so this is rare.

Verdict

Ready to merge (0 must-fix, 0 should-fix)