@astryxdesign/core 0.7.5 → 0.7.6-canary.bb18c81

package/src/DateInput/__tests__/MonthScrollerSteps.interaction.browser.spec.ts

@@ -0,0 +1,312 @@
+// Copyright (c) Meta Platforms, Inc. and affiliates.
+
+/**
+ * @file MonthScrollerSteps.interaction.browser.spec.ts
+ * @input The built "Default" DateInput story, shown in a bottom sheet, the
+ *   arrows clicked from the page, real mouse and trackpad input and the
+ *   interaction harness
+ * @output Interaction proofs for the month scroller's steps: after the month
+ *   and year wheels close, a trackpad scroll still pages to the next month and
+ *   Reset from four months on still rests on today's month; an arrow step
+ *   through a stalled frame moves exactly one month; under a finger, a swipe
+ *   that crosses the middle of a month as it lifts keeps scroll snapping on
+ *   and rests on the next month.
+ *   (A second arrow step late in the first one's scroll, which WebKit cuts
+ *   short, is proven in MonthScrollerSettle.test.tsx: a loaded page's frames
+ *   are too far apart to aim a click at a share of a 300 ms scroll.)
+ * @position Interaction tests of MonthScroller.tsx
+ *   (`*.interaction.browser.spec.ts`, run by `pnpm test:interaction`)
+ */
+
+import {expect, test, type Locator, type Page} from '@playwright/test';
+import {
+  blockMainThread,
+  drag,
+  openStory,
+  touchDriver,
+  withStorybook,
+} from '@astryxdesign/interaction-harness';
+
+const storybook = withStorybook(test);
+const STORY = 'core-dateinput--default';
+const ARGS = {presentation: 'bottom-sheet'};
+
+/** Waits until the scroller's offset has not moved for ten frames. */
+async function waitForRest(viewport: Locator): Promise<number> {
+  return viewport.evaluate(
+    async element =>
+      new Promise<number>(resolve => {
+        let last = element.scrollLeft;
+        let still = 0;
+        const check = () => {
+          const now = element.scrollLeft;
+          still = now === last ? still + 1 : 0;
+          last = now;
+          if (still >= 10) {
+            resolve(now);
+          } else {
+            requestAnimationFrame(check);
+          }
+        };
+        requestAnimationFrame(check);
+      }),
+  );
+}
+
+/** The month the scroller rests on, as the pane's own grid names it. */
+/**
+ * Waits until a month's grid sits flush with the scroller's edge, the offset
+ * unchanged, for ten frames: the end of the scroller's own settle
+ * correction, however long the page takes to run it. (The panes' width can
+ * be fractional, so the grid's own box is the measure, not the offset.)
+ */
+async function waitForRestOnMonth(viewport: Locator): Promise<number> {
+  return viewport.evaluate(
+    async element =>
+      new Promise<number>(resolve => {
+        let last = element.scrollLeft;
+        let still = 0;
+        const flush = () => {
+          const edge = element.getBoundingClientRect().left;
+          return [
+            ...element.querySelectorAll<HTMLElement>('[role="grid"]'),
+          ].some(
+            grid => Math.abs(grid.getBoundingClientRect().left - edge) < 1,
+          );
+        };
+        const check = () => {
+          const now = element.scrollLeft;
+          still = now === last && flush() ? still + 1 : 0;
+          last = now;
+          if (still >= 10) {
+            resolve(now);
+          } else {
+            requestAnimationFrame(check);
+          }
+        };
+        requestAnimationFrame(check);
+      }),
+  );
+}
+
+async function monthAtRest(viewport: Locator): Promise<string> {
+  return viewport.evaluate(element => {
+    const box = element.getBoundingClientRect();
+    const middle = box.left + box.width / 2;
+    for (const grid of element.querySelectorAll<HTMLElement>('[role="grid"]')) {
+      const r = grid.getBoundingClientRect();
+      if (r.left <= middle && r.right >= middle) {
+        return grid.getAttribute('aria-label') ?? '';
+      }
+    }
+    return '';
+  });
+}
+
+async function openCalendar(page: Page) {
+  await openStory(page, storybook(), STORY, ARGS);
+  await page
+    .getByRole('button', {name: /calendar/i})
+    .first()
+    .click();
+  const viewport = page.locator('[data-scroller="months"]');
+  await expect(viewport).toBeVisible();
+  await waitForRest(viewport);
+  return viewport;
+}
+
+test.use({hasTouch: false, isMobile: false});
+
+/**
+ * Waits until the scroller comes to rest, or until it has gone more than
+ * `limit` past `from`: a scroller that runs on by itself never rests, and
+ * the proof should fail where it ran, not at the test's timeout.
+ */
+async function waitForRestOrRun(
+  viewport: Locator,
+  from: number,
+  limit: number,
+): Promise<number> {
+  return viewport.evaluate(
+    async (element, {from, limit}) =>
+      new Promise<number>(resolve => {
+        let last = element.scrollLeft;
+        let still = 0;
+        const check = () => {
+          const now = element.scrollLeft;
+          still = now === last ? still + 1 : 0;
+          last = now;
+          if (still >= 10 || Math.abs(now - from) > limit) {
+            resolve(now);
+          } else {
+            requestAnimationFrame(check);
+          }
+        };
+        requestAnimationFrame(check);
+      }),
+    {from, limit},
+  );
+}
+
+/**
+ * A stalled frame right after an arrow (a 300 ms block of the main thread)
+ * let the re-center that follows the step land after the scroll had ended,
+ * and WebKit's re-snap after it then paged on by itself, a month every few
+ * frames. The step moves exactly one month.
+ */
+test('an arrow step through a stalled frame moves exactly one month', async ({
+  page,
+}) => {
+  const viewport = await openCalendar(page);
+  const title = page.getByRole('button', {name: /Choose month and year/});
+  const from = await viewport.evaluate(element => element.scrollLeft);
+  const width = await viewport.evaluate(element => element.clientWidth);
+  const box = await page
+    .getByRole('button', {name: 'Next month'})
+    .boundingBox();
+  if (box == null) {
+    throw new Error('no Next month button');
+  }
+  await page.mouse.click(box.x + box.width / 2, box.y + box.height / 2);
+  await blockMainThread(page, 300);
+  const at = await waitForRestOrRun(viewport, from, 2 * width);
+  expect(Math.round((at - from) / width)).toBe(1);
+  await waitForRestOnMonth(viewport);
+  expect(
+    Math.round(((await viewport.evaluate(e => e.scrollLeft)) - from) / width),
+  ).toBe(1);
+  await expect(title).toHaveAccessibleName(
+    new RegExp(await monthAtRest(viewport)),
+  );
+});
+
+/**
+ * Closing the month and year wheels re-asserts the month shown, a steer that
+ * moves nothing. A trackpad scroll after it is the user's: it pages to the
+ * next month and stays there, the title following.
+ */
+test('after the month and year wheels close, a trackpad scroll to the next month stays there', async ({
+  page,
+}) => {
+  const viewport = await openCalendar(page);
+  const toggle = page.getByRole('button', {name: /Choose month and year/});
+  const start = await monthAtRest(viewport);
+  expect(start).not.toBe('');
+  const toggleBox = await toggle.boundingBox();
+  if (toggleBox == null) {
+    throw new Error('no month and year toggle');
+  }
+  const clickToggle = async () =>
+    page.mouse.click(
+      toggleBox.x + toggleBox.width / 2,
+      toggleBox.y + toggleBox.height / 2,
+    );
+  await clickToggle();
+  await expect(toggle).toHaveAttribute('aria-expanded', 'true');
+  await clickToggle();
+  await expect(toggle).toHaveAttribute('aria-expanded', 'false');
+  await waitForRest(viewport);
+
+  const box = await viewport.boundingBox();
+  if (box == null) {
+    throw new Error('no month scroller');
+  }
+  await page.mouse.move(box.x + box.width / 2, box.y + box.height / 2);
+  // A horizontal trackpad scroll of 70 % of a month, as one wheel event: a
+  // burst of small ones reaches a loaded page far enough apart to count as
+  // separate gestures, each snapping back on its own.
+  await page.mouse.wheel(box.width * 0.7, 0);
+  // Past the scroller's own settle correction too, which ends on a month's
+  // boundary.
+  await waitForRestOnMonth(viewport);
+  const next = await monthAtRest(viewport);
+  expect(next).not.toBe(start);
+  await expect(toggle).toHaveAccessibleName(new RegExp(next));
+});
+
+/**
+ * Reset from four months on is a far jump, mounting today's month before the
+ * scroller moves. After the month and year wheels close, whose re-assert is a
+ * steer that moved nothing, the jump still rests on today's month, the title
+ * with it.
+ */
+test('after the month and year wheels close, Reset from four months on rests on today’s month', async ({
+  page,
+}) => {
+  const viewport = await openCalendar(page);
+  const toggle = page.getByRole('button', {name: /Choose month and year/});
+  const today = await monthAtRest(viewport);
+  expect(today).not.toBe('');
+  const clickCentre = async (name: string | RegExp) => {
+    const box = await page.getByRole('button', {name}).boundingBox();
+    if (box == null) {
+      throw new Error(`no ${String(name)} button`);
+    }
+    await page.mouse.click(box.x + box.width / 2, box.y + box.height / 2);
+  };
+  for (let step = 0; step < 4; step++) {
+    await clickCentre('Next month');
+    await waitForRest(viewport);
+  }
+  expect(await monthAtRest(viewport)).not.toBe(today);
+  await clickCentre(/Choose month and year/);
+  await expect(toggle).toHaveAttribute('aria-expanded', 'true');
+  await clickCentre(/Choose month and year/);
+  await expect(toggle).toHaveAttribute('aria-expanded', 'false');
+  await waitForRest(viewport);
+
+  await clickCentre('Reset');
+  // Past the scroller's own settle correction too, which ends on a month's
+  // boundary.
+  await waitForRestOnMonth(viewport);
+  expect(await monthAtRest(viewport)).toBe(today);
+  await expect(toggle).toHaveAccessibleName(new RegExp(today));
+});
+
+test.describe('under a finger', () => {
+  test.use({hasTouch: true, isMobile: true});
+
+  /**
+   * A swipe whose last move crosses the middle of the month makes the
+   * scroller re-center as the finger lifts. The finger drives that scroll, so
+   * the re-center leaves scroll snapping on (turning it off drops the snap
+   * target iOS tracks for the gesture, and the swipe coasted past the month),
+   * and the swipe comes to rest on the next month.
+   */
+  test('a swipe that crosses the middle of a month as it lifts keeps snapping on and rests on the next month', async ({
+    page,
+  }) => {
+    const viewport = await openCalendar(page);
+    const start = await monthAtRest(viewport);
+    const box = await viewport.boundingBox();
+    if (box == null) {
+      throw new Error('no month scroller');
+    }
+    // Every change of the scroller's inline scroll-snap-type from here on.
+    await viewport.evaluate(element => {
+      const changes: string[] = [];
+      (window as unknown as {snapChanges: string[]}).snapChanges = changes;
+      new MutationObserver(() => {
+        changes.push((element as HTMLElement).style.scrollSnapType || 'on');
+      }).observe(element, {attributes: true, attributeFilter: ['style']});
+    });
+    const driver = await touchDriver(page);
+    const y = box.y + box.height / 2;
+    const from = {x: box.x + box.width * 0.8, y};
+    // 55 % of a month toward the next one, the middle crossed by the last
+    // move, lifting a quarter frame after it.
+    await driver.play(
+      drag(from, {x: from.x - box.width * 0.55, y}, {durationMs: 300}),
+    );
+    await waitForRestOnMonth(viewport);
+    const rest = await monthAtRest(viewport);
+    expect(rest).not.toBe('');
+    expect(rest).not.toBe(start);
+    // Snapping was never turned off while the finger drove the scroll.
+    expect(
+      await page.evaluate(
+        () => (window as unknown as {snapChanges: string[]}).snapChanges,
+      ),
+    ).not.toContain('none');
+  });
+});

package/src/DateRangeInput/DateRangeInput.test.tsx

@@ -18,9 +18,9 @@ function generateThemeTestCSS(theme: Parameters<typeof generateThemeCSS>[0]) {
   const {prose, component} = generateThemeCSS(theme);
   return [prose, component].filter(Boolean).join('\n\n');
 }
-// getButton/queryButton instead of getByRole('button', {name}): the closed
-// popover keeps a two-month Calendar (~85 role=button nodes) mounted, which
-// made every role+name query compute ~85 accessible names through jsdom's
+// getButton/queryButton instead of getByRole('button', {name}): the open
+// popover holds a two-month Calendar (~85 role=button nodes), which makes
+// every role+name query compute ~85 accessible names through jsdom's
 // slow getComputedStyle (~450ms per query). See fastRoleQueries.ts.
 import {getButton, queryButton} from '../__tests__/fastRoleQueries';
 import * as stylex from '@stylexjs/stylex';
@@ -767,6 +767,49 @@ describe('DateRangeInput', () => {
   });
 });
 
+describe('DateRangeInput calendar while the popover is closed', () => {
+  const calendarGrid = () => document.querySelector('[role="grid"]');
+
+  it('renders no calendar until the popover opens, and none after it closes', () => {
+    render(
+      <DateRangeInput
+        label="Range"
+        value={{start: '2026-01-05', end: '2026-01-09'}}
+        onChange={() => {}}
+      />,
+    );
+    const toggle = getButton('Open calendar');
+    expect(calendarGrid()).toBeNull();
+
+    fireEvent.click(toggle);
+    expect(calendarGrid()).not.toBeNull();
+
+    fireEvent.click(toggle);
+    expect(calendarGrid()).toBeNull();
+  });
+
+  it('moves focus into the popover on each open from the toggle', async () => {
+    render(
+      <DateRangeInput
+        label="Range"
+        value={{start: '2026-01-05', end: '2026-01-09'}}
+        onChange={() => {}}
+      />,
+    );
+    const toggle = getButton('Open calendar');
+
+    for (let i = 0; i < 2; i++) {
+      fireEvent.click(toggle);
+      // The first calendar control takes focus, not the dialog surface.
+      await waitFor(() => {
+        expect(getButton('Previous month')).toHaveFocus();
+      });
+      fireEvent.click(toggle);
+      expect(calendarGrid()).toBeNull();
+    }
+  });
+});
+
 describe('DateRangeInput statusVariant forwarding', () => {
   it('defaults to attached (status renders with data-variant="attached")', () => {
     const {container} = render(

package/src/DateRangeInput/DateRangeInput.tsx

@@ -851,18 +851,22 @@ export function DateRangeInput({
               })}
             </div>
           )}
-          <Calendar
-            mode="range"
-            value={optimisticValue}
-            onChange={handleRangeSelect}
-            min={min}
-            max={max}
-            dateConstraints={dateConstraints}
-            maxRangeSpan={maxRangeSpan}
-            minRangeSpan={minRangeSpan}
-            numberOfMonths={numberOfMonths}
-            weekStartsOn={weekStartsOn}
-          />
+          {/* The layer renders its children open or closed, so mount the
+              calendar only while it is open. */}
+          {popover.isOpen && (
+            <Calendar
+              mode="range"
+              value={optimisticValue}
+              onChange={handleRangeSelect}
+              min={min}
+              max={max}
+              dateConstraints={dateConstraints}
+              maxRangeSpan={maxRangeSpan}
+              minRangeSpan={minRangeSpan}
+              numberOfMonths={numberOfMonths}
+              weekStartsOn={weekStartsOn}
+            />
+          )}
         </div>,
         {placement: 'below', alignment: 'start'},
       )}

package/src/DateTimeInput/DateTimeInput.spec.md

@@ -3,11 +3,11 @@ schema_version: 3
 template_version: 7
 kind: component
 id: component:DateTimeInput
-authority: draft
+authority: current
 archive_reason: null
 superseded_by: null
-approved_by: null
-approved_at: null
+approved_by: cixzhang
+approved_at: 2026-10-30
 owners: [cixzhang]
 review_triggers: [public-api, behavior, layout, theming, accessibility]
 verified_by:
@@ -16,30 +16,37 @@ verified_by:
     packages/core/src/DateTimeInput/DateTimeInputTouch.test.tsx,
     packages/core/src/DateTimeInput/NativePickerSegments.test.tsx,
     packages/core/src/DateTimeInput/Presentation.test.tsx,
+    packages/core/src/DateTimeInput/DateTimeInput.fr10.test.tsx,
+    packages/core/src/__tests__/BusyOwnerAnnouncement.test.tsx,
     packages/core/src/theme/themingTargets.test.ts,
     scripts/check-knowledge.mjs,
   ]
 modules: []
 families: [family:input-fields, family:overlay-dismissal]
 design_specs: []
-architecture: [architecture:component-theming-surface]
+architecture:
+  [
+    architecture:component-theming-surface,
+    architecture:internationalization,
+    architecture:public-component-api,
+  ]
 contributing: []
-system_specs: [spec:AST-043]
+system_specs: [spec:AST-043, spec:AST-085, spec:AST-086, spec:AST-102]
 ---
 
 # DateTimeInput component contract
 
 ## Contract at a glance
 
-| Area                    | Contract                                                                                                                                                                                                  |
-| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Public contract         | One controlled ISO date-time value presented through coordinated date and time segments; `presentation` selects Astryx, native, or adaptive picker surfaces.                                              |
-| Behavior                | Date and time changes emit one combined value; clear emits `undefined`; controlled empty state remains empty in every rendered picker.                                                                    |
-| End-user impact         | People selecting a date and time see one value reflected consistently in the closed field and the active picker, including after clearing.                                                                |
-| Builder impact          | None.                                                                                                                                                                                                     |
-| Compatibility/readiness | Released defaults and deprecated `nativePicker` behavior remain unchanged. The presentation matrix is governed by current `spec:AST-043`; component-local observations remain draft pending owner review. |
-| Review checks           | Reject competing picker selection, date/time output that is not one valid combined value, presentation precedence drift, lost per-segment fallback, or broken segment accessibility.                      |
-| Governing rules         | `spec:AST-043`, `family:input-fields`, `family:overlay-dismissal`, and objective platform accessibility standards.                                                                                        |
+| Area                    | Contract                                                                                                                                                                                                                                                                                 |
+| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Public contract         | One controlled ISO date-time value presented through coordinated date and time segments; `presentation` selects Astryx, native, or adaptive picker surfaces.                                                                                                                             |
+| Behavior                | Date and time changes emit one combined value; clear emits `undefined`; controlled empty state remains empty in every rendered picker.                                                                                                                                                   |
+| End-user impact         | People selecting a date and time see one value reflected consistently in the closed field and the active picker, including after clearing.                                                                                                                                               |
+| Builder impact          | None.                                                                                                                                                                                                                                                                                    |
+| Compatibility/readiness | Records shipped behavior; no API, default, or DOM change. The presentation matrix and deprecated `nativePicker` mapping follow `spec:AST-043`. Fixed segment height, locale time text and parsing, busy paint, and caller handlers while disabled are listed under Current-state impact. |
+| Review checks           | Reject competing picker selection, date/time output that is not one valid combined value, presentation precedence drift, lost per-segment fallback, or broken segment accessibility.                                                                                                     |
+| Governing rules         | `spec:AST-043`, `family:input-fields`, `family:overlay-dismissal`, `spec:AST-085`, `spec:AST-086` FR8, and objective platform accessibility standards.                                                                                                                                   |
 
 This table is a review projection; the body below is authoritative.
 
@@ -71,13 +78,16 @@ Consumer migration instructions belong in consumer docs and release notes.
 - Applying component-local date-time bounds, date constraints, time precision,
   typed-time stepping, and optional preset-time behavior.
 - Emitting `onChange` before an optional optimistic `changeAction`.
+- The disabled-reason Tooltip composition, which `family:input-fields` assigns
+  to the member.
 
 **Does not own / non-goals**
 
-- Field label, description, status, disabled-reason, and clear-button presentation —
-  owned by `component:Field` and `component:FieldStatus`.
+- Field label, description, status, and clear-button presentation —
+  owned by Field under `family:input-fields` (shared owner section) and
+  `component:FieldStatus`.
 - Calendar-grid rendering and date-cell interaction — owned by
-  `component:Calendar`.
+  Calendar.
 - Popover and sheet hosting or dismissal — owned by the composed layer components
   and `family:overlay-dismissal`.
 - Cross-component picker-presentation vocabulary and deprecated-prop mapping —
@@ -95,18 +105,17 @@ Consumer migration instructions belong in consumer docs and release notes.
 
 ## Behavioral and layout contract
 
-Draft requirements identify their basis so observed code is not mistaken for an
-intentional decision.
-
-| ID  | Candidate invariant                                                                                                                                                                                                                       | Basis                                                                 | Draft review state                                     |
-| --- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ------------------------------------------------------ |
-| FR1 | DateTimeInput MUST reflect one controlled date-time value across its visible segments and active picker, and MUST NOT reveal a competing selected date after the parent accepts a clear.                                                  | Public docs, controlled component seam, current source, focused tests | Verified observation; owner approval pending           |
-| FR2 | Every committed date or time change MUST emit one valid combined ISO date-time value; clearing MUST emit `undefined`; changing time while no date is committed MUST emit nothing.                                                         | Public types, docs, current source, focused tests                     | Verified observation; owner approval pending           |
-| FR3 | `presentation`, deprecated `nativePicker`, precedence, pointer adaptation, forced surfaces, and per-segment native fallbacks MUST follow `spec:AST-043` FR1–FR4.                                                                          | `spec:AST-043`                                                        | Inherited current authority                            |
-| FR4 | When `changeAction` is present, every value-change path MUST call `onChange` first, show the proposed controlled value optimistically, and contribute to one busy state until the controlled value accepts or replaces it.                | `family:input-fields/FR6`                                             | Inherited current authority                            |
-| FR5 | The two pointer segments share one row while each retains its intrinsic basis; when the container is narrower, flex wrapping moves them into separate full-width rows.                                                                    | Public docs, current source, focused layout tests                     | Verify rendered geometry; class-level behavior covered |
-| FR6 | Date-time bounds and date constraints MUST prevent invalid commits. Native controls MAY receive platform hints, but JavaScript validation remains the final commit boundary; calendar-only options MAY be unavailable on native surfaces. | Public docs, current source, focused presentation tests               | Verified observation; owner approval pending           |
-| FR7 | A preset-time listbox MUST remain optional, preserve typed entry, expose one selected option independently from keyboard highlight, and limit offered values to the selected date's effective minimum and maximum.                        | Public docs, current source, focused interaction tests                | Verified observation; owner approval pending           |
+| ID  | Invariant                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Basis                                                                                                   |
+| --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- |
+| FR1 | DateTimeInput MUST reflect one controlled date-time value across its visible segments and active picker, and MUST NOT reveal a competing selected date after the parent accepts a clear.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Public docs, controlled component seam, current source, focused tests                                   |
+| FR2 | Every committed date or time change MUST emit one valid combined ISO date-time value; clearing MUST emit `undefined`; changing time while no date is committed MUST emit nothing.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Public types, docs, current source, focused tests                                                       |
+| FR3 | `presentation`, deprecated `nativePicker`, precedence, pointer adaptation, forced surfaces, and per-segment native fallbacks MUST follow `spec:AST-043` FR1–FR4.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `spec:AST-043`                                                                                          |
+| FR4 | When `changeAction` is present, every value-change path MUST call `onChange` first, show the proposed controlled value optimistically, and contribute to one busy state until the controlled value accepts or replaces it.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | `family:input-fields/FR6`                                                                               |
+| FR5 | The two pointer segments share one row while each retains its intrinsic basis; when the container is narrower, flex wrapping moves them into separate full-width rows. Each segment is the shared element height for its size, as a minimum that grows with a set text size under `spec:AST-102` FR4. Implementation gap: the height is fixed at that size.                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Public docs, current source, focused layout tests; `spec:AST-102` FR4                                   |
+| FR6 | Date-time bounds and date constraints MUST prevent invalid commits. Native controls MAY receive platform hints, but JavaScript validation remains the final commit boundary; calendar-only options MAY be unavailable on native surfaces.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | Public docs, current source, focused presentation tests                                                 |
+| FR7 | A preset-time listbox MUST remain optional, preserve typed entry, expose one selected option independently from keyboard highlight, and limit offered values to the selected date's effective minimum and maximum. Time text and typed times MUST follow the active locale's digits, separator, and day-period words (`architecture:internationalization` INV1a, INV8). Implementation gap: time text, preset options, and the stepped-time announcement use ASCII digits, a `:` separator, and a fixed English "AM"/"PM", and the typed time parser takes no locale.                                                                                                                                                                                                                                              | Public docs, current source, focused interaction tests; `architecture:internationalization` INV1a, INV8 |
+| FR8 | Base props and `ref` MUST reach the date segment's input; a caller `aria-describedby` joins the component's own descriptions, and a caller DOM handler runs after the field's own handler. `container*` reaches the Field box and `control*` the segment row; root `xstyle`, `className`, and `style` are not accepted.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | `family:input-fields` FR10; `DateTimeInput.fr10.test.tsx`                                               |
+| FR9 | A disabled field MUST keep both segments focusable with `aria-disabled` and no native `disabled`, block every value-changing path, keep the calendar button's tab stop, and paint the keyboard focus ring. Explicit `isLoading` makes every surface inert the same way; a pending `changeAction` does so only on the popover surface, and the bottom sheet and any field with a native date segment keep accepting edits. The busy start is announced once. Implementation gap: a caller `onKeyDown` and other DOM handlers on the date segment still run while disabled (`spec:AST-085` FR2). Implementation gap: a busy field that is not disabled takes the disabled paint (half opacity), on every surface while `isLoading` and on the popover while a `changeAction` is pending, against `spec:AST-085` FR6. | `spec:AST-085` FR1, FR2, FR6; `spec:AST-086` FR8; current source and tests                              |
 
 ### Allowed variation
 
@@ -119,13 +128,13 @@ intentional decision.
 
 ### Representative states
 
-| State                       | Required invariant                                                                                        | Allowed variation                          |
-| --------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
-| Empty                       | Both segments and every active picker expose no committed selection.                                      | Placeholder and selected surface.          |
-| Date-time value             | Date segment, time segment, and active picker reflect the same committed value.                           | Locale, hour format, and time precision.   |
-| Cleared after picker change | Closed field is empty and reopening the picker reveals no selected date or retained committed time.       | Picker focus date may remain navigational. |
-| Busy                        | Proposed value remains visible; mutation paths are unavailable; both editable segments expose busy.       | Explicit loading or pending action source. |
-| Focusable disabled          | Both segments remain focusable enough to expose the reason while every value-changing path stays blocked. | Disabled-reason text.                      |
+| State                       | Required invariant                                                                                                                                                                                          | Allowed variation                          |
+| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
+| Empty                       | Both segments and every active picker expose no committed selection.                                                                                                                                        | Placeholder and selected surface.          |
+| Date-time value             | Date segment, time segment, and active picker reflect the same committed value.                                                                                                                             | Locale, hour format, and time precision.   |
+| Cleared after picker change | Closed field is empty and reopening the picker reveals no selected date or retained committed time.                                                                                                         | Picker focus date may remain navigational. |
+| Busy                        | Proposed value remains visible; both editable segments expose busy. With explicit `isLoading`, mutation paths are unavailable on every surface; with a pending `changeAction`, only on the popover surface. | Explicit loading or pending action source. |
+| Focusable disabled          | Both segments stay focusable with `aria-disabled` while every value-changing path stays blocked.                                                                                                            | Disabled-reason text.                      |
 
 ### Transformation and precedence order
 
@@ -220,24 +229,38 @@ leading clock glyph uses `date-time-input-clock-icon`.
 
 ## Verification map
 
-| Contract            | Verification                                                                            | Representative states                                         | Mutation or failure expectation                                                                                                      | Audit section                     |
-| ------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------- |
-| FR1–FR2             | `DateTimeInput.test.tsx`                                                                | empty, calendar selection, typed date/time, clear             | A stale Calendar selection, partial output, or invalid mutation makes a public-state test fail.                                      | `audit:DateTimeInput/behavior`    |
-| FR3, FR6            | `Presentation.test.tsx`, `NativePickerSegments.test.tsx`, `DateTimeInputTouch.test.tsx` | forced, adaptive, legacy, native fallback, constrained commit | A substituted surface, precedence drift, or invalid commit makes a presentation test fail.                                           | `audit:DateTimeInput/surfaces`    |
-| FR4, AR4            | `DateTimeInput.test.tsx`, `DateTimeInputTouch.test.tsx`                                 | pending, loading, disabled reason                             | Mutation during busy/disabled state or stale optimistic output makes a state test fail.                                              | `audit:DateTimeInput/state`       |
-| FR5                 | `DateTimeInput.test.tsx`                                                                | intrinsic row, narrow-container wrap classes                  | Removing the intrinsic basis or wrap styles makes the class-level layout assertions fail; rendered geometry remains review evidence. | `audit:DateTimeInput/layout`      |
-| FR7, AR1–AR3        | `DateTimeInput.test.tsx`, `DateTimeInputTouch.test.tsx`                                 | popovers, time options, keyboard/focus                        | Wrong role, name, state, keyboard behavior, or focus behavior makes a focused interaction test fail.                                 | `audit:DateTimeInput/interaction` |
-| Theming anatomy map | `scripts/check-knowledge.mjs`, `themingTargets.test.ts`                                 | root, segments, icons, listbox, options                       | Missing, undocumented, or wrongly placed targets fail knowledge or target checks.                                                    | `audit:DateTimeInput/theming`     |
+| Contract            | Verification                                                                                                 | Representative states                                         | Mutation or failure expectation                                                                                                                                                                    | Audit section                     |
+| ------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- |
+| FR1–FR2             | `DateTimeInput.test.tsx`                                                                                     | empty, calendar selection, typed date/time, clear             | A stale Calendar selection, partial output, or invalid mutation makes a public-state test fail.                                                                                                    | `audit:DateTimeInput/behavior`    |
+| FR3, FR6            | `Presentation.test.tsx`, `NativePickerSegments.test.tsx`, `DateTimeInputTouch.test.tsx`                      | forced, adaptive, legacy, native fallback, constrained commit | A substituted surface, precedence drift, or invalid commit makes a presentation test fail.                                                                                                         | `audit:DateTimeInput/surfaces`    |
+| FR4, FR9, AR4       | `DateTimeInput.test.tsx`, `DateTimeInputTouch.test.tsx`; `BusyOwnerAnnouncement.test.tsx` DateTimeInput case | pending, loading, disabled reason                             | Mutation during busy/disabled state or stale optimistic output makes a state test fail. Evidence gap: no test asserts that caller handlers still run while disabled.                               | `audit:DateTimeInput/state`       |
+| FR5                 | `DateTimeInput.test.tsx`                                                                                     | intrinsic row, narrow-container wrap classes                  | Removing the intrinsic basis or wrap styles makes the class-level layout assertions fail; rendered geometry remains review evidence. Evidence gap: no test asserts segment heights or text growth. | `audit:DateTimeInput/layout`      |
+| FR7, AR1–AR3        | `DateTimeInput.test.tsx`, `DateTimeInputTouch.test.tsx`                                                      | popovers, time options, keyboard/focus                        | Wrong role, name, state, keyboard behavior, or focus behavior makes a focused interaction test fail. Evidence gap: no test asserts locale-specific time text or parsing.                           | `audit:DateTimeInput/interaction` |
+| FR8                 | `DateTimeInput.fr10.test.tsx`                                                                                | each surface; caller id, describedby, onClick, onKeyDown      | A base prop off the date input, a dropped caller description, or styling on the wrong part fails.                                                                                                  | `audit:DateTimeInput/api`         |
+| Theming anatomy map | `scripts/check-knowledge.mjs`, `themingTargets.test.ts`                                                      | root, segments, icons, listbox, options                       | Missing, undocumented, or wrongly placed targets fail knowledge or target checks.                                                                                                                  | `audit:DateTimeInput/theming`     |
+
+## Current-state impact
+
+- **Fixed height (FR5).** Segments hold the fixed shared element height instead
+  of growing with a set text size, against `spec:AST-102` FR4.
+- **Time text and parsing (FR7).** Time text, preset options, and the stepped
+  announcement use ASCII digits, a `:` separator, and English "AM"/"PM", and
+  typed times parse without the locale, against
+  `architecture:internationalization` INV1a and INV8.
+- **Busy paint (FR9).** A busy field that is not disabled takes the disabled
+  half-opacity paint, against `spec:AST-085` FR6.
+- **Caller handlers while disabled (FR9).** Caller DOM handlers on the date
+  segment, such as `onKeyDown`, still run while disabled, against
+  `spec:AST-085` FR2.
 
 ## Decision log
 
-No component-local decision is asserted by this draft. Current cross-component
-picker decisions remain in `spec:AST-043`.
+No component-local decision. Cross-component picker decisions live in
+`spec:AST-043`.
 
 ## Open questions
 
-None. Owner review may accept, amend, or reject the observational component-local
-rows without changing inherited current authority.
+None.
 
 ## Content boundary