astryx

Part of the accessibility & keyboard-management program (#3343). Fixes complex-2 and complex-3. Problem complex-3 — malformed grid ARIA tree.** The Calendar's month view was not a valid APG grid: The weekday cells lived in a `role="grid"role="row"role="gridcell"useGridFocusindex / columnsindex % columnscellSelector: 'button:not([disabled])'minmaxdateConstraintsCalendar.tsxrole="row"role="grid"columnheaderrole="row"role="gridcell"role="gridcell"gridcellrole="rowheader"display: contentsuseGridFocusisCellFocusablegetFocusTargetgridcellrole="grid"role="row"columnheaderrowgridcellrowheaderminpnpm -F @astryxdesign/core typecheckeslintvitest runCalendarDateInputDateRangeInputDateTimeInputpnpm -F @astryxdesign/core buildpnpm check:repo` — all gates pass

What Cleanup of lingering references to the removed feature. The command and the / / flags (and their gap-filing behavior) were removed in #3255 — now prints a short maintainer feedback link (issue tracker + a ready-to-run ) instead of filing gap-report issues. Several docs, help strings, CI probes, and tooling still described the old behavior. This PR brings them in line with the current behavior. Changed — remove the command row, the error-code row, the two type-mapping rows, and the stale config example (replaced with the current key). — remove the usage example. — drop and from the source-tree map and the example in the "does it need an API function?" note. — the swizzle line and the "always use " rule no longer reference the removed flag. — the generated agent-docs help line no longer mentions . / **** — stop probing the removed command (the smoke test asserted a type that no longer exists). — drop the module entry so the sandbox CLI explorer no longer tries to load a deleted module. — removed; it curated -labelled issues that the CLI no longer files. Not touched The historical entry and the released-version notes are intentional release-note history and are left as-is. No runtime behavior changes — this is docs/remnant cleanup only. The codemod comment ("gap reported in #2863") refers to a capability gap filed as an issue, not the removed feature, and is left as-is. Testing — 100 files / 1625 tests pass. , , , — all pass. on the changed code file — clean.

Part of the accessibility & keyboard-management program (#3343). Fixes finding . Problem The shared popover/layer entry animations — (translate + scale keyframes used by DropdownMenu, Popover, HoverCard, Tooltip, Selector and other layer surfaces) and the presets (slideDown/slideUp/fadeIn/scaleIn) — had no guard, unlike the ~20 individual components that do guard their motion. Users who ask for reduced motion still got sliding/scaling overlays. Fix Each animation now disables its keyframe under by setting in that media query (StyleX conditional value). The layer simply appears instead of translating/scaling in. No change for users without the preference. Verification Typecheck, lint, and the StyleX babel build all pass; DropdownMenu/Popover/Tooltip/HoverCard suites green (76 tests). Pure styling change (no behavior/test changes needed in the consumers).