@astryxdesign/core 0.7.3-canary.fba04ed → 0.7.3

package/src/FieldStatus/FieldStatus.spec.md

@@ -130,9 +130,9 @@ intentional decision.
   region, including on first mount and when message or type changes, without
   moving focus. Inside a mounted live container, `spec:AST-086` FR4 applies.
 - **AR5 — Assistive-technology output.** Claims about whether, when, or how the
-  message is spoken or presented in braille MUST be verified through the real-AT
-  evidence process in `spec:AST-009`; DOM and accessibility-tree checks prove
-  only programmatic exposure and routing.
+  message is spoken or presented in braille are recommended real-AT follow-up
+  under `spec:AST-009`, not a merge or release requirement; DOM and
+  accessibility-tree checks prove programmatic exposure and routing.
 - **AR2 — Visible description.** The rendered message box MUST remain available
   to assistive technology for `aria-describedby` association and MUST NOT become
   its own newly mounted live region.
@@ -182,7 +182,7 @@ change either presentation.
 | FR5, FR6            | `FieldStatus.test.tsx` forwarding and update suites                     | Initial render and rerender                                   | Breaking the released root or update behavior fails compatibility assertions.                                                         | `audit:FieldStatus/behavior`      |
 | AR1                 | `StatusMessage.a11y.test.tsx` and `StatusMessage.a11y.chromium.spec.ts` | Error, warning, and success; post-mount message replacement   | Removing the persistent channel, changing its role/urgency, or dropping a post-mount update fails the shared status-message contract. | `audit:FieldStatus/accessibility` |
 | AR1                 | `FieldStatus.test.tsx` channel-routing suite                            | First non-empty mount; same-instance message and type changes | Breaking FieldStatus's first-use hook call or severity rerouting fails component-specific assertions.                                 | `audit:FieldStatus/accessibility` |
-| AR5                 | Pending/unverified real-AT evidence governed by `spec:AST-009`          | First mount; message replacement; type/urgency change         | Spoken and braille output remain unverified until a durable named AT/browser receipt exists.                                          | `audit:FieldStatus/accessibility` |
+| AR5                 | Recommended real-AT follow-up under `spec:AST-009`                      | First mount; message replacement; type/urgency change         | Spoken and braille output stay unverified until a real-AT receipt exists; this does not block merge or release.                       | `audit:FieldStatus/accessibility` |
 | AR2                 | `FieldStatus.test.tsx`                                                  | Attached/detached visible message and empty message           | The visible description becomes a second live region or is hidden from assistive technology.                                          | `audit:FieldStatus/accessibility` |
 | Theming anatomy map | `scripts/check-knowledge.mjs`                                           | Consumer anatomy and current targets                          | Missing, extra, duplicated, prefixed, or stale mappings fail repository validation.                                                   | `audit:FieldStatus/theming`       |
 

package/src/FieldStatus/__tests__/StatusMessage.a11y.renders.tsx

@@ -10,7 +10,6 @@
  */
 
 import {useEffect, useState, type ReactElement, type ReactNode} from 'react';
-import {ChatSystemMessage} from '../../Chat/ChatSystemMessage';
 import {ProgressBar} from '../../ProgressBar/ProgressBar';
 import {Spinner} from '../../Spinner/Spinner';
 import {Toast} from '../../Toast/Toast';
@@ -198,22 +197,6 @@ function SpinnerHarness({visibleLabel}: {visibleLabel: boolean}) {
   );
 }
 
-function ChatSystemMessageHarness() {
-  const initial = 'Conversation started';
-  const [message, setMessage] = useState(initial);
-  return (
-    <Frame>
-      <TransitionButton name="show" onClick={() => setMessage(initial)} />
-      <TransitionButton
-        name="replace"
-        onClick={() => setMessage('A file was shared')}
-      />
-      <TransitionButton name="clear" onClick={() => setMessage('')} />
-      <ChatSystemMessage>{message}</ChatSystemMessage>
-    </Frame>
-  );
-}
-
 function ProgressHarness({
   initial,
   progressValue = 40,
@@ -289,7 +272,6 @@ export const CORE_STATUS_MESSAGE_STATE_RENDERS: Record<
     <SpinnerHarness visibleLabel={false} />
   ),
   'spinner-visible-label-mounted': () => <SpinnerHarness visibleLabel />,
-  'chat-system-status-mounted': () => <ChatSystemMessageHarness />,
   'progress-loading-to-complete': () => <ProgressHarness />,
   'progress-custom-range': () => (
     <ProgressHarness

package/src/FieldStatus/__tests__/StatusMessage.a11y.states.ts

@@ -14,7 +14,6 @@ export type CoreStatusMessageBinding =
   | 'Toast card'
   | 'FieldStatus announcement channel'
   | 'Spinner'
-  | 'ChatSystemMessage'
   | 'ProgressBar';
 
 export interface CoreStatusMessageBindingDefinition {
@@ -188,20 +187,6 @@ export const CORE_STATUS_MESSAGE_BINDING_STATES = [
     }),
     storyId: 'a11y-status-message-pattern--spinner-visible-label-mounted',
   },
-  {
-    id: 'chat-system-status-mounted',
-    binding: 'ChatSystemMessage',
-    summary: 'a chat status notice is mounted with its live-region content',
-    facts: liveFacts({
-      role: 'status',
-      politeness: 'polite',
-      initialMessage: 'Conversation started',
-      message: 'Conversation started',
-      replacement: 'A file was shared',
-      semanticTransitions: ['replace', 'clear'],
-    }),
-    storyId: 'a11y-status-message-pattern--chat-system-status-mounted',
-  },
   {
     id: 'progress-loading-to-complete',
     binding: 'ProgressBar',
@@ -279,10 +264,10 @@ export const CORE_STATUS_MESSAGE_EXCLUSIONS = [
       'A composing control that marks Spinner aria-hidden owns the surrounding busy semantics; the decorative ring is not another status message.',
   },
   {
-    owner: 'ChatSystemMessage divider',
-    part: 'date or section separator',
+    owner: 'ChatSystemMessage',
+    part: 'chat notice or date separator',
     reason:
-      'A divider does not report success, results, waiting, progress, or an error. Its current forced status role is tracked as a separate ownership mismatch rather than adopted here.',
+      'spec:AST-086 FR4: a notice added to a chat log is delivered by the log, so neither the notice row nor the divider carries its own live role; a date or section separator is ordinary transcript content.',
   },
   {
     owner: 'ChatMessageList and streaming logs',

package/src/FieldStatus/__tests__/StatusMessage.a11y.test.tsx

@@ -128,7 +128,6 @@ describe('Core status-message binding inventory', () => {
         ),
       ].sort(),
     ).toEqual([
-      'ChatSystemMessage',
       'FieldStatus announcement channel',
       'ProgressBar',
       'Spinner',
@@ -141,7 +140,7 @@ describe('Core status-message binding inventory', () => {
     expect(CORE_STATUS_MESSAGE_EXCLUSIONS.map(entry => entry.part)).toEqual([
       'visible validation text',
       'aria-hidden decorative spinner',
-      'date or section separator',
+      'chat notice or date separator',
       'role=log transcript updates',
       'composer errors and tool-run states',
       'busy announcement',

package/src/Markdown/Markdown.helpers.perf.test.ts

@@ -357,17 +357,17 @@ describe('Markdown helper performance', () => {
         }),
       ];
 
-      // Timed on the transform stage alone and compared at the FASTEST
-      // sample of each side: this is a few hundred microseconds against a
-      // parse of milliseconds, so measuring the whole parse buries it, and
-      // a minimum is the least-disturbed sample each side achieved.
+      // Timed on the transform stage alone: this is a few hundred
+      // microseconds against a parse of milliseconds, so measuring the whole
+      // parse buries it. Each side is compared at its FASTEST sample, the
+      // least-disturbed run it achieved, and the two sides alternate sample by
+      // sample so a slow stretch of the machine reaches both instead of one.
       const root = parseMarkdownAst(source);
-      const fastestTransform = (
+      const transformOnly = (
         plugins: ReadonlyArray<ReturnType<typeof createMarkdownPlugin>>,
-      ): number => {
+      ) => {
         const prepared = prepareMarkdownPlugins(plugins);
-        let fastest = Number.POSITIVE_INFINITY;
-        for (let sample = 0; sample < 60; sample++) {
+        return () => {
           const start = performance.now();
           benchmarkSink ^= applyMarkdownTransforms(
             root,
@@ -376,18 +376,24 @@ describe('Markdown helper performance', () => {
             true,
             'block',
           ).children.length;
-          fastest = Math.min(fastest, performance.now() - start);
-        }
-        void benchmarkSink;
-        return fastest;
+          return performance.now() - start;
+        };
       };
-
-      const single = plugin('scale-single', gaps);
-      const double = plugin('scale-double', doubled);
-      // Warm both before either is recorded.
-      fastestTransform(single);
-      fastestTransform(double);
-      const ratio = fastestTransform(double) / fastestTransform(single);
+      const single = transformOnly(plugin('scale-single', gaps));
+      const double = transformOnly(plugin('scale-double', doubled));
+      let fastestSingle = Number.POSITIVE_INFINITY;
+      let fastestDouble = Number.POSITIVE_INFINITY;
+      for (let sample = 0; sample < 80; sample++) {
+        // The first rounds only warm both sides.
+        const singleTime = single();
+        const doubleTime = double();
+        if (sample >= 20) {
+          fastestSingle = Math.min(fastestSingle, singleTime);
+          fastestDouble = Math.min(fastestDouble, doubleTime);
+        }
+      }
+      void benchmarkSink;
+      const ratio = fastestDouble / fastestSingle;
       console.log(
         `  ${sections} sections, ${doubled.length} ranges over ${gaps.length}: ${ratio.toFixed(3)}`,
       );

package/src/Table/plugins/columnResize/useTableColumnResize.spec.md

@@ -227,17 +227,17 @@ without a target of its own.
 
 ## Verification map
 
-| Contract           | Verification                                                                                                   | Representative states                                                                                            | Mutation or failure expectation                                                                                                                                                           |
-| ------------------ | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| FR1, FR6           | `useTableColumnResize.test.tsx` boundary-presence cases plus hover-capability and coarse-primary cases         | Resizable, opted-out, and generated columns; hover-capable, coarse-primary with keyboard, and coarse-only inputs | A boundary appears on a non-resizable column, disappears from a resizable one, the hover reveal fires where no pointer can hover, or the control is absent where an input can operate it. |
-| FR2                | Browser measurement of scroll-region vertical overflow with the plugin enabled                                 | Short and tall tables, wrapped and single-line headers, dense and default                                        | The indicator ends below the last row or the scroll region gains vertical scroll that the same table lacks without resize.                                                                |
-| FR3-FR5, FR9, ORD1 | New focused tests for resting, header-hovered, pointer-on-boundary, focused, and dragging states               | Rest, header hover, hover plus pointer on one boundary, keyboard focus with no pointer in the row, drag          | A resting header draws boundaries, header hover misses a boundary, the pointed/focused boundary fails to outrank the hint, or focus alone draws a neighbor.                               |
-| FR10, ORD0         | Scroll-gate test driving the scroll region with a stationary pointer over the header                           | Pointer resting over a header while the region scrolls and after it settles                                      | Boundaries reveal mid-scroll, an existing hint survives the scroll, or disclosure fails to resume once scrolling stops.                                                                   |
-| FR7                | Snapshot or assertion that header hover changes no other header or row treatment                               | Header hover over a sortable and a selectable header                                                             | Header hover changes background, label, cursor, width, or another control's state.                                                                                                        |
-| FR8, AR1-AR3, AR6  | Existing keyboard and ARIA suites, a coarse-primary keyboard case, plus assistive-technology spot check        | Tab to boundary, arrow resize, screen-reader navigation of the header, coarse-primary device with a keyboard     | The boundary leaves tab order on any input that can operate it, loses its name or values, or the hint reaches the accessibility tree.                                                     |
-| PR1, PR2           | Render-count assertion around header pointer enter/leave and during a scroll; listener and observer inspection | Pointer enters and leaves the header repeatedly; the region scrolls under a resting pointer                      | Disclosure rerenders the Table, the scroll gate sets React state, more than one scroll listener or any timer is added, or the extent measurement observes what it resizes.                |
-| Plugin composition | Test mounting the resize and sticky-columns plugins together in both insertion orders                          | Pinned start column with resize enabled, before and after a drag                                                 | A pinned column loses `position: sticky` in either order, or the composition depends on caller insertion order.                                                                           |
-| Record shape       | `scripts/check-knowledge.mjs`                                                                                  | Colocated module record, canonical id and filename, parent backlink                                              | A missing, misnamed, mis-parented, or unlinked record passes validation.                                                                                                                  |
+| Contract           | Verification                                                                                                                      | Representative states                                                                                            | Mutation or failure expectation                                                                                                                                                           |
+| ------------------ | --------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| FR1, FR6           | `useTableColumnResize.test.tsx` boundary-presence cases plus hover-capability and coarse-primary cases                            | Resizable, opted-out, and generated columns; hover-capable, coarse-primary with keyboard, and coarse-only inputs | A boundary appears on a non-resizable column, disappears from a resizable one, the hover reveal fires where no pointer can hover, or the control is absent where an input can operate it. |
+| FR2                | Browser measurement of scroll-region vertical overflow with the plugin enabled                                                    | Short and tall tables, wrapped and single-line headers, dense and default                                        | The indicator ends below the last row or the scroll region gains vertical scroll that the same table lacks without resize.                                                                |
+| FR3-FR5, FR9, ORD1 | New focused tests for resting, header-hovered, pointer-on-boundary, focused, and dragging states                                  | Rest, header hover, hover plus pointer on one boundary, keyboard focus with no pointer in the row, drag          | A resting header draws boundaries, header hover misses a boundary, the pointed/focused boundary fails to outrank the hint, or focus alone draws a neighbor.                               |
+| FR10, ORD0         | Scroll-gate test driving the scroll region with a stationary pointer over the header                                              | Pointer resting over a header while the region scrolls and after it settles                                      | Boundaries reveal mid-scroll, an existing hint survives the scroll, or disclosure fails to resume once scrolling stops.                                                                   |
+| FR7                | Snapshot or assertion that header hover changes no other header or row treatment                                                  | Header hover over a sortable and a selectable header                                                             | Header hover changes background, label, cursor, width, or another control's state.                                                                                                        |
+| FR8, AR1-AR3, AR6  | Existing keyboard and ARIA suites and a coarse-primary keyboard case; an assistive-technology spot check is recommended follow-up | Tab to boundary, arrow resize, screen-reader navigation of the header, coarse-primary device with a keyboard     | The boundary leaves tab order on any input that can operate it, loses its name or values, or the hint reaches the accessibility tree.                                                     |
+| PR1, PR2           | Render-count assertion around header pointer enter/leave and during a scroll; listener and observer inspection                    | Pointer enters and leaves the header repeatedly; the region scrolls under a resting pointer                      | Disclosure rerenders the Table, the scroll gate sets React state, more than one scroll listener or any timer is added, or the extent measurement observes what it resizes.                |
+| Plugin composition | Test mounting the resize and sticky-columns plugins together in both insertion orders                                             | Pinned start column with resize enabled, before and after a drag                                                 | A pinned column loses `position: sticky` in either order, or the composition depends on caller insertion order.                                                                           |
+| Record shape       | `scripts/check-knowledge.mjs`                                                                                                     | Colocated module record, canonical id and filename, parent backlink                                              | A missing, misnamed, mis-parented, or unlinked record passes validation.                                                                                                                  |
 
 Browser, render-count, and assistive-technology evidence are pending. Passing this
 specification pull request proves record integrity only.

package/src/Table/plugins/rowStatus/useTableRowStatus.spec.md

@@ -214,8 +214,9 @@ add semantic/custom cases to representative Table render and no-op update budget
 - **AR5 — Supplemental tooltip.** Tooltip may repeat `label` as pointer help, but
   the indicator's accessible name MUST remain sufficient without opening it. The
   current indicator is not focusable, so tooltip presence is not keyboard evidence.
-- **AR6 — Row context.** Assistive-technology verification MUST confirm the named
-  status is encountered in its row context without duplicate announcements.
+- **AR6 — Row context.** The named status is exposed in its row context without a
+  duplicate name, proved at the accessibility tree. Assistive-technology
+  observation of the announcement is recommended follow-up under `spec:AST-009`.
 
 ## Design relationships
 
@@ -259,7 +260,7 @@ own AST-002 review and synchronized consumer anatomy.
 | FR3, FR4, FR6            | Add public-subpath compile fixtures for the unchanged interface, declaration merging and extension, semantic interface, callback union, missing labels, unknown statuses, and forbidden mixtures. | Stable custom annotations/extensions; all semantic statuses.                           | `TableRowStatus` changes or stops merging, semantic usage is inaccessible, or supported status mixes with custom fields.                                           |
 | FR3-FR5                  | Extend row-status runtime tests with semantic-looking custom colors, raw/palette dots, explicit custom icons, all semantic statuses, and active-theme substitution.                               | Custom dot, custom icon, and three semantic outcomes.                                  | Custom color selects an implicit glyph, semantic status bypasses shared resolution, or variant becomes caller/theme input.                                         |
 | FR7, ORD2-ORD4, PR4      | Runtime tests under development and production modes with repeated mixed objects, rows, and renders.                                                                                              | `status + color`, `status + icon`, and all three fields.                               | Custom input overrides supported status, forbidden fields affect output, production warns, or development warns more than once per loaded module instance.         |
-| AR1-AR6                  | Existing role/name tests plus browser axe, forced-colors, tooltip modality, and VoiceOver table-navigation evidence.                                                                              | Semantic glyphs, custom icon, custom dot, `null`, light/dark, and every shipped theme. | Header or indicator loses its name, nested glyph is announced twice, glyph distinctions disappear, tooltip becomes sole meaning, or row context duplicates status. |
+| AR1-AR6                  | Existing role/name tests plus browser axe, forced-colors, tooltip modality, and accessibility-tree row-context evidence; VoiceOver table navigation is recommended follow-up.                     | Semantic glyphs, custom icon, custom dot, `null`, light/dark, and every shipped theme. | Header or indicator loses its name, nested glyph is announced twice, glyph distinctions disappear, tooltip becomes sole meaning, or row context duplicates status. |
 | PR1-PR3                  | Extend `Table.perf.test.tsx` with semantic/custom initial render and no-op update cases.                                                                                                          | Stable rerender, mixed rows, and theme substitution.                                   | Resolution adds measurement/resources, creates a parallel registry, or exceeds existing representative Table budgets.                                              |
 | Structural ownership     | `scripts/check-knowledge.mjs`.                                                                                                                                                                    | Colocated module, canonical filename/id, and parent backlink.                          | A missing, duplicate, orphaned, mis-parented, misnamed, or undiscovered record passes validation.                                                                  |
 | Public hygiene and scope | Prettier, `check:knowledge`, checker tests, `check:repo`, changed-file scan, and public-content scan.                                                                                             | Parent backlink plus one module specification; no Changeset.                           | Runtime/docs files, private context, invalid record shape, or unrelated changes enter this contract proposal.                                                      |