[iamnbutler]

Item 1 from #75.

API: desktop_set_value accepts a string value on AXDateTimeArea, AXDateField and AXTimeField:

• 2026-10-17 is local midnight, 2026-10-17T15:30[:SS] is local time, and Z/±HH:MM sets the zone.
• The TS client (src/date-value.ts) validates the string and normalizes it to UTC to the second (2026-10-17T13:30:00Z). Impossible dates such as Feb 30 are refused.
• The native client refuses a string on any other role and a number/bool on date roles. An unsettable date control is refused with the keyboard route.
• A non-completed date result carries keyboard_route: click the first field, type the digits, Tab to the next field, or step with Up/Down.

Host (peekaboo-date-value.patch, appended): when the element's AXValue is an NSDate and the request is a string, ActionInputDriver takes a date path:

• The string must be the canonical UTC spelling.
• A value that is already equal → confirmedNoChange.
• Otherwise it writes an NSDate via the new setAutomationDate, polls for up to 1 s, and confirms only on the same instant. A mismatch → the usual unverified mutation (unknown).
• The readback is reported as the same string, so the existing signed set-value binding (readback == requested string) applies unchanged, with no bridge changes.

Tests:

• ActionInputDriverTests: 89 pass, including the write, no-change, refused spellings and mismatched-readback cases.
• New test/date-value.test.mjs; npm test and npm run check pass.

Live: pending. The session was locked at last check, and another session's swift test helper is currently holding ~/.peekaboo/global.lock. The signed dev app is built at /tmp/dt/app; I'll check against a TextEdit/Calendar or Settings date picker when possible.

Co-Authored-By: Claude noreply@anthropic.com