- Shipped
- August 10, 2026 at 7:52 PM UTC
- Author
- kamo
- Commit
- 3d6e23b
The most useful thing a scheduling dialog can say is "you already have something then", and the endpoint to answer it existed all along with nothing calling it. The dialog now asks as the times change — debounced, because the datetime inputs fire per keystroke — and reports the clash inside the When card, directly under the controls that caused it, rather than as a banner somewhere else or an error after saving. Editing passes excludeEventId so an event does not report itself. Two more things that were two-field edits and are now one tap: - Today and Tomorrow move the event to that day while keeping its time and duration. "Same time tomorrow" is a far more common intent than picking a date out of a widget. - The save shortcut is shown in the footer, rendered per platform, so it is discoverable rather than folklore. Every string is an existing key: conflictsWith already carried a {names} placeholder for the week and day views, and common.time supplied the day labels. The shortcut hint is symbols, so it needs none. Verified with a production build in a detached worktree — another session holds the in-tree build lock.