Time Range Field always returns AM

### Describe the bug Time Range Field in 12H mode (default) will always return an AM time when modifying the hour. For example, if the current time is set to `2:00 PM`, typing `1` in the hour position will return `2026-03-11 2026-03-11T01:00:00`, resulting in `1 AM`. By contrast, modifying the minute field will return the correct time. For example, if the current time is set to `2:00 PM`, typing `30` in the minute position will return `2026-03-11T14:30:00`, resulting in `2:30 PM`. You can reproduce this in the docs examples at: https://bits-ui.com/docs/components/time-range-field Edit: This same issue exists in https://bits-ui.com/docs/components/time-field ### Reproduction https://bits-ui.com/docs/components/time-range-field ### Logs ```bash ``` ### System Info ```bash System: OS: macOS 15.3 CPU: (8) arm64 Apple M1 Pro Memory: 161.06 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 24.11.0 - /Users/erik/.nvm/versions/node/v24.11.0/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 11.6.1 - /Users/erik/.nvm/versions/node/v24.11.0/bin/npm pnpm: 7.25.1 - /opt/homebrew/bin/pnpm bun: 1.0.2 - /Users/erik/.bun/bin/bun Deno: 1.25.3 - /opt/homebrew/bin/deno Browsers: Chrome: 145.0.7632.162 Firefox: 147.0.3 Safari: 18.3 npmPackages: @sveltejs/kit: ^2.49.0 => 2.49.0 bits-ui: ^2.14.3 => 2.14.3 svelte: ^5.39.11 => 5.53.7 ``` ### Severity annoyance