Quality baseline · 2026-08-21
Quality is a feature, not a finishing pass.
A library-wide quality baseline made accessibility, public APIs, and release confidence part of the product itself.
The work behind a dependable component library is often invisible — until it is missing. This milestone made it explicit.
Explore the components
Accessibility in the delivery loop
Regression coverage strengthened table semantics, tree-menu leaves, lightbox triggers, and named scroll regions so the catalogue is checked for more than appearance.
A public contract
API stability, support, deprecation, and changelog policies clarified how consumers can adopt Opus with confidence as the package evolves.
Release gates that matter
Library quality workflows and tree-shaken package bundles made the standards repeatable instead of relying on a final manual check.