Support
Component support
Component stability
Lifecycle stability is separate from adapter availability. FileUpload is Stable under the Automated Core profile. Every other catalog entry remains Beta in this release; Tabs, DataTable, and the overlay family remain the named P1 migration boundary after the 1.0.2 release.
Automated browser gate
Lyra v1.0 requires an automated gate using Playwright 1.62.1 with Chromium revision 1234
(151.0.7922.34), Firefox revision 1538 (153.0), and WebKit revision 2336 (26.5). Current CI
runs this pinned Chromium, Firefox, and WebKit matrix inside the existing test job.
Manual assistive technology
Under the active Automated Core beta profile, manual Windows/NVDA and macOS/VoiceOver evidence is
deferred-by-release-profile: it is non-blocking post-release evidence and is not a pass. No
assistive-technology review is claimed as completed. The optional Full profile retains those
manual records and the conditional mobile procedures as stricter requirements.
What support means
The matrix uses only the CSS, Alpine-enhanced, React, and Unsupported levels. A level describes the documented adapter contract, not cross-adapter parity. Support means the applicable contract covers keyboard interaction, focus management and semantic markup; SSR and hydration; themes, forced colors, RTL, reduced motion, zoom, and reflow. Every Unsupported entry exposes its missing capability, reason, user impact, fallback, evidence status, and reevaluation owner.
Blade timing
Blade cells publish the CSS or Alpine-enhanced behavior present in the released
lyra-ds/blade v0.10.0 artifact and its repository API snapshot. They do not claim parity with a
future Lyra v1 contract. After an affected React contract stabilizes, Blade requires a separate
compatibility update and evidence record. Blade is an existing downstream adapter and does not block
Lyra v1.0.