fix(tables): preserve expiration precision during calendar edits

Author: j15z

apps/sim/app/workspace/[workspaceId]/search/components/search-source-setup.test.tsx

@@ -441,10 +441,14 @@ describe('organization setup entry points', () => {
       }),
       expect.any(Object)
     )
-    await click(button('Cancel'))
-    expect(mocks.urlUpdate).toHaveBeenLastCalledWith(
-      expect.objectContaining({ queryString: '?search=keep' })
-    )
+    await act(async () => {
+      button('Cancel').click()
+      await vi.waitFor(() =>
+        expect(mocks.urlUpdate).toHaveBeenLastCalledWith(
+          expect.objectContaining({ queryString: '?search=keep' })
+        )
+      )
+    })
     expect(document.querySelector('[role="dialog"]')).toBeNull()
     expect(mocks.push).not.toHaveBeenCalled()
     expect(

docs/testing/expiration-qa.md

@@ -2,6 +2,8 @@
 
 This is the acceptance matrix for the current Expiration column. Execute against a disposable local database with this branch's migrations. Never run the destructive fixtures or injected failures against an existing development, staging, or production database.
 
+Expiration has not been released, and there are no production tables with Expiration columns. These changes define the initial timestamp contract; numeric-value migration is not a rollout requirement. Malformed stored values in this matrix are deliberately injected fixtures.
+
 ## Invariants
 
 - Only rows with a valid explicit expiration at or before the cleanup run's cutoff can be deleted.
@@ -79,6 +81,8 @@ The results below distinguish automated coverage from live browser, HTTP, and Po
 
 ## Results — September 9, 2026
 
+**Review follow-up: 22 calendar tests and 108 table/search UI tests pass.** Calendar day selection and Today preserve the existing clock time, seconds, and microseconds, including across the Los Angeles daylight-saving gap. The Expiration editor reattaches the stored numeric offset. The failing search setup test now waits for the queued URL update after Cancel before asserting it; production search behavior is unchanged.
+
 **Offset-preservation follow-up: 2,162 regression tests and 23 non-stress PostgreSQL scenarios pass.** The current contract preserves numeric offsets and spells incoming Z as -00:00. Earlier results below were collected before this formatting change; the follow-up section records the new contract checks. Production-environment verification is still separate.
 
 The environment was Chrome plus this worktree's local Next.js application, PostgreSQL 17, and a freshly migrated database named `expiration_qa`. All accounts, keys, tables, and rows were disposable fixtures. Existing application environments were not used. External provider credentials were cleared in the test process. The queue used the real database backend; Trigger.dev and Redis were not configured.

packages/emcn/src/components/calendar/calendar-interaction.test.tsx

@@ -0,0 +1,46 @@
+/**
+ * @vitest-environment jsdom
+ */
+
+import { act, createElement } from 'react'
+import { Calendar } from '@sim/emcn'
+import { createRoot } from 'react-dom/client'
+import { describe, expect, it, vi } from 'vitest'
+
+;(globalThis as { IS_REACT_ACT_ENVIRONMENT?: boolean }).IS_REACT_ACT_ENVIRONMENT = true
+
+describe('Calendar precise date edits', () => {
+  it.each(['07:30:45.123456', '00:00:00.000001', '02:30:00.999999'])(
+    'retains %s when selecting a day and Today',
+    async (time) => {
+      const container = document.createElement('div')
+      document.body.appendChild(container)
+      const root = createRoot(container)
+      const onChange = vi.fn()
+      try {
+        await act(async () =>
+          root.render(
+            createElement(Calendar, {
+              value: `2026-03-07T${time}`,
+              showTime: true,
+              today: '2026-03-09',
+              onChange,
+            })
+          )
+        )
+        const buttons = Array.from(container.querySelectorAll('button'))
+        const nextDay = buttons.find((button) => button.textContent?.trim() === '8')
+        expect(nextDay).toBeDefined()
+        await act(async () => nextDay!.click())
+        expect(onChange).toHaveBeenLastCalledWith(`2026-03-08T${time}`)
+        const today = buttons.find((button) => button.textContent?.trim() === 'Today')
+        expect(today).toBeDefined()
+        await act(async () => today!.click())
+        expect(onChange).toHaveBeenLastCalledWith(`2026-03-09T${time}`)
+      } finally {
+        await act(async () => root.unmount())
+        container.remove()
+      }
+    }
+  )
+})

packages/emcn/src/components/calendar/calendar.test.ts

@@ -20,13 +20,29 @@ describe('parseDateTimeValue', () => {
     expect(parseDateTimeValue('2026-07-06T16:04').time).toBe('16:04')
   })
 
+  it.each(['14:30:00.000001', '14:30:45.123456', '00:00:00.999999'])(
+    'retains the full wall time %s for subsequent date selections',
+    (time) => {
+      expect(parseDateTimeValue(`2026-09-07T${time}`).time).toBe(time)
+    }
+  )
+
+  it('does not reinterpret a literal wall time through a daylight-saving gap', () => {
+    expect(parseDateTimeValue('2026-03-08T02:30:45.123456').time).toBe('02:30:45.123456')
+  })
+
   it('treats a coincidental local midnight as no time for Date instances', () => {
     expect(parseDateTimeValue(new Date(2026, 6, 6)).time).toBeNull()
     expect(parseDateTimeValue(new Date(2026, 6, 6, 16, 4, 55)).time).toBe('16:04:55')
   })
 
+  it('retains early years when reading a literal wall time', () => {
+    expect(parseDateTimeValue('0001-01-01T12:30:00.123456').date?.getFullYear()).toBe(1)
+  })
+
   it('returns nulls for unparseable input', () => {
     expect(parseDateTimeValue('garbage')).toEqual({ date: null, time: null })
+    expect(parseDateTimeValue('2026-99-99T12:30:00.123456')).toEqual({ date: null, time: null })
   })
 })
 

packages/emcn/src/components/calendar/calendar.tsx

@@ -131,8 +131,9 @@ function timeOfDayFrom(date: Date): string {
 
 /**
  * Parses a date value into its local day plus an optional time-of-day. Bare
- * `YYYY-MM-DD` strings are pure days (no time). Datetime strings parse through
- * `Date` so an explicit offset (`Z`, `-07:00`) resolves to the **local** day —
+ * `YYYY-MM-DD` strings are pure days (no time). Offset-free ISO datetimes keep
+ * their literal clock and fractional precision. Explicit offsets (`Z`, `-07:00`)
+ * parse through `Date` and resolve to the **local** day —
  * unlike {@link parseDateValue}'s date-slice fast path, which would read the
  * UTC day.
  *
@@ -153,6 +154,17 @@ export function parseDateTimeValue(value: string | Date | undefined): {
   }
   const parsed = value instanceof Date ? value : new Date(value)
   if (Number.isNaN(parsed.getTime())) return { date: null, time: null }
+  if (typeof value === 'string') {
+    const wallTime =
+      /^\d{4}-\d{2}-\d{2}T((?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d{1,9})?)?)$/.exec(value)
+    if (wallTime) {
+      const time = wallTime[1]
+      return {
+        date: parsed,
+        time: time.length === 8 && time.endsWith(':00') ? time.slice(0, 5) : time,
+      }
+    }
+  }
   if (typeof value === 'string' && value.includes('T')) {
     return { date: parsed, time: timeOfDayFrom(parsed) }
   }
@@ -206,12 +218,12 @@ interface CalendarSingleProps extends CalendarBaseProps {
   value?: string | Date
   /**
    * Called with the picked date in `YYYY-MM-DD` format — or, with `showTime`
-   * and a set time, the local wall time `YYYY-MM-DDTHH:mm[:ss]`.
+   * and a set time, the local wall time `YYYY-MM-DDTHH:mm[:ss[.fraction]]`.
    */
   onChange?: (value: string) => void
   /**
    * Adds a time-of-day input under the grid. Day picks keep the current time
-   * (seconds included when the seeded value had them); time edits re-emit on
+   * (seconds and fractional seconds included when supplied); time edits re-emit on
    * the selected (or today's) day. Without a time set, day picks emit bare
    * `YYYY-MM-DD` days.
    */