feat(ui): prepare 3.2 with accessible controls, forms, and native QA

.github/workflows/ci.yml

@@ -43,52 +43,22 @@ jobs:
           # the next corrective run rebuild the observability stack from zero.
           cache-on-failure: true
 
-      # Track the current ps-qa release so UI coverage cannot silently remain
-      # on an obsolete harness — but build each tool against the dependency set
-      # it was published with.
+      # The host is the browser, and the browser is not a crate a site can
+      # install: `chuzz-headless` is built from source by the composite action
+      # below, which also installs the driver. That replaced `qa-inspect-host`,
+      # which was a second headless browser with the web platform in only the
+      # other one -- no `URLSearchParams`, no `matchMedia`, no storage, no
+      # observers -- so every gap closed for the browser had to be closed a
+      # second time there by hand, or the sweep measured a browser nobody
+      # ships.
       #
-      # Resolving these fresh picks the newest `ps-blitz-*` that satisfies the
-      # requirements, and those crates are not compatible across minor versions:
-      # `qa-inspect-host` ended up compiled against `ps-blitz-script` 0.4.1
-      # while its `tauri-runtime-blitz` expected 0.3.x, so the same type
-      # existed twice and every call between them failed to typecheck. That
-      # broke this step, and because everything below depends on it, Lint, Type
-      # Check, Build and the whole test suite were skipped rather than failed —
-      # a green-looking pipeline that had verified nothing.
-      #
-      # `--locked` is gone, and it did cost currency: a lockfile is frozen at
-      # publication, so the host was pinned to whatever engine existed the day
-      # it was released. A renderer fix could then never reach this gate without
-      # a host release, and that is not hypothetical -- `ps-blitz` 0.4.3 fixes
-      # three defects in checkbox activation, and the host published before it
-      # kept installing 0.4.2, so `switch`, `checkbox` and `radio` went on
-      # failing here against an engine that had already been fixed.
-      #
-      # The mismatch `--locked` was added for is gone with it: it happened when
-      # `qa-inspect-host` wanted `ps-blitz` 0.4.x while its `tauri-runtime-blitz`
-      # wanted 0.3.x, so the same type existed twice. Both now require `^0.4`
-      # and resolve to one copy.
-      #
-      # One command per tool, deliberately. `cargo install a b --locked`
-      # resolves the two together and downgrades to satisfy both — it picks
-      # `qa-inspect-host` 0.1.4 instead of 0.1.8. Installed separately they
-      # each get their own resolution and stay current.
-      - name: Install native QA tools
-        env:
-          # cargo install otherwise builds in disposable temporary directories,
-          # which leaves rust-cache nothing useful to restore on the next run.
-          CARGO_TARGET_DIR: target/qa-tools
-        run: |
-          # Pinned to a floor, not left to "latest".
-          #
-          # The sweep needs `--headless` and a host that can replace a text
-          # field without a font catalogue. Installing whatever is newest meant
-          # a version without those failed as `unexpected argument`, which
-          # reads as a broken workflow rather than a tool that is too old --
-          # and a host that silently appended to a field would not have failed
-          # at all until a check disagreed about a value.
-          cargo install ps-qa --version "^0.6.2"
-          cargo install qa-inspect-host --version "^0.1.12"
+      # 0.1.12 is still on crates.io, so nothing broke when the crate was
+      # deleted from source; this is the last consumer to move off it.
+      - name: Headless browser host
+        id: qa
+        uses: pathscale/chuzz/.github/actions/headless-host@master
+        with:
+          token: ${{ secrets.SIBLING_REPOS_TOKEN }}
 
       - name: Install Dependencies
         run: bun install
@@ -110,23 +80,20 @@ jobs:
         run: bun run build
 
       # Native renderer outcomes replace jsdom interaction tests as the release
-      # gate. One headless host per component keeps the complete sweep below two
-      # minutes while preserving a clean document between components.
+      # gate. One headless host per component preserves a clean document.
       - name: Rendered component outcomes
         env:
           # A shared runner takes longer than a local machine for outcomes that pass
           # locally well inside the budget. This widens scheduling deadlines only; every
           # declared rendered-state transition is still required.
           QA_TIMEOUT_SCALE: 2
-          # This runner has no font catalogue, and it should not have one: a
-          # component library that needs a GUI stack installed to be tested is
-          # a component library nobody can test. With no fonts every glyph
-          # shapes to nothing, so anything sized by its text lays out flat and
-          # every paint assertion fails for a reason that says nothing about
-          # the component. The headless profile asks the same questions about
-          # layout instead; the full profile keeps the visual half and runs
-          # where there are fonts. See `PROFILES` in generate-checks.ts.
-          QA_PROFILE: headless
+          # The shared host action installs fonts without a desktop stack.
+          # Keep actual paint assertions in the release gate.
+          QA_PROFILE: full
+          # The harness looks for `chuzz-headless` on PATH; here it is the
+          # build the composite action above just made, so it is named
+          # outright.
+          QA_HOST: ${{ steps.qa.outputs.host }}
         run: |
           bun run qa:checks
           bun run qa:entries

README.md

@@ -28,7 +28,7 @@ yarn add @pathscale/ui solid-layouts && yarn add -D rsbuild-plugin-solid-layouts
 
 ## Setup
 
-`@pathscale/ui` 2.x is a compiled Layout bundle. Configure the application compiler before
+`@pathscale/ui` 3.x is a compiled Layout bundle. Configure the application compiler before
 Solid transforms JSX:
 
 ```ts
@@ -58,11 +58,22 @@ import "@pathscale/ui/index.css";
 
 export const Example = () => (
   <Flex direction="col" gap="sm">
-    <Button variant="primary" size="md">Primary</Button>
+    <Button variant="solid" flavor="primary" size="md">Primary</Button>
   </Flex>
 );
 ```
 
+In the application's Tailwind v4 stylesheet, register the package as a source
+(adjust the relative path from that stylesheet):
+
+```css
+@source "../node_modules/@pathscale/ui";
+```
+
+This includes the published `dist/responsive-classes.txt` scanner input. Grid and
+Flex compose responsive classes at runtime, so scanning only the compiled JavaScript
+misses utilities such as `md:grid-cols-3`.
+
 ## Theming
 
 Two themes ship with the library: `light` (the default when no attribute is set) and `dark`.

docs/api-contract.md

@@ -11,7 +11,7 @@ invisible for a day behind a doc that looked correct the whole time.
 When an API change is intentional, run `bun run check:api -- --write`, read the
 diff, and commit it. The diff is the review.
 
-186 components. An empty list means the component adds nothing beyond
+187 components. An empty list means the component adds nothing beyond
 HTML attributes and `UIBaseProps`; that is an assertion, not a gap.
 
 ---
@@ -226,6 +226,7 @@ _No props beyond HTML attributes and `UIBaseProps`._
 ### Calendar
 
 ```ts
+dateNames?: DateNames
 defaultValue?: Date
 disabled?: boolean
 isDateUnavailable?: (date: Date) => boolean
@@ -253,11 +254,14 @@ elevation?: CardElevation
 flavor?: Flavor
 footer?: JSX.Element
 header?: JSX.Element
+href?: string
 isInteractive?: boolean
 material?: Material
 padding?: Space
 radius?: Radius
+rel?: string
 state?: CardState
+target?: JSX.AnchorHTMLAttributes<HTMLAnchorElement>["target"]
 variant?: Variant
 ```
 
@@ -287,11 +291,14 @@ elevation?: CardElevation
 flavor?: Flavor
 footer?: JSX.Element
 header?: JSX.Element
+href?: string
 isInteractive?: boolean
 material?: Material
 padding?: Space
 radius?: Radius
+rel?: string
 state?: CardState
+target?: JSX.AnchorHTMLAttributes<HTMLAnchorElement>["target"]
 variant?: Variant
 ```
 
@@ -446,8 +453,12 @@ wheelClass?: string
 
 ```ts
 class?: string
+color?: ColorValue | string
+defaultColor?: ColorValue | string
+disabled?: boolean
 id?: string
 mode?: ColorWheelFlowerMode
+onChange?: (color: ColorValue) => void
 palette?: readonly string[]
 ```
 
@@ -645,6 +656,7 @@ _No props beyond HTML attributes and `UIBaseProps`._
 ### DatePicker
 
 ```ts
+dateNames?: DateNames
 defaultOpen?: boolean
 defaultValue?: Date
 disabled?: boolean
@@ -665,6 +677,7 @@ weekdayFormat?: CalendarWeekdayFormat
 ### DateRangePicker
 
 ```ts
+dateNames?: DateNames
 defaultOpen?: boolean
 defaultValue?: DateRangeValue
 disabled?: boolean
@@ -890,6 +903,7 @@ id?: string
 ### DrawerTrigger
 
 ```ts
+as?: ValidComponent
 children: JSX.Element
 ```
 
@@ -912,6 +926,12 @@ placement?: DropdownPlacement
 children: JSX.Element
 ```
 
+### FieldErrorMessage
+
+```ts
+message?: string
+```
+
 ### FieldGroup
 
 ```ts
@@ -936,6 +956,7 @@ _No props beyond HTML attributes and `UIBaseProps`._
 
 ```ts
 extensionUrl?: string
+icon?: string | JSX.Element
 onDismiss?: () => void
 onInstall?: () => void
 storageKey?: string
@@ -1051,6 +1072,7 @@ i18n: I18nStore
 ```ts
 flavor?: Flavor
 height?: number
+label?: string
 src?: string | JSX.Element
 width?: number
 ```
@@ -1537,6 +1559,7 @@ variant?: RadioGroupVariant
 ### RangeCalendar
 
 ```ts
+dateNames?: DateNames
 defaultValue?: RangeCalendarValue
 disabled?: boolean
 isDateUnavailable?: (date: Date) => boolean
@@ -1729,6 +1752,7 @@ variant?: TabsVariant
 ### Text
 
 ```ts
+as?: TextAs
 children?: JSX.Element
 family?: TextFamily
 leading?: TextLeading