Changelog

Documented package and revision #

This site documents @coreux/ui version 0.1.0, pinned to commit 06f42fd532ec03a8fa80a320398cd7f006d89dec. The package version comes from the installed package; the full Git revision identifies the implementation used by examples and prop extraction.

Review the exported API (repository access required). Every component’s source link uses this same revision. Browsing and copying this reference is public; installing the package and opening private GitHub source require repository read access.

Initial reference baseline · September 14, 2026 #

The first reference covers all 24 component exports and accounts for all 68 original seed examples. It includes installation, copyable examples, extracted prop contracts, foundation guidance, and explicit documentation of the library’s layout and accessibility limits.

Documentation adaptations include readable wrappers and labels, illustrative data, correct typed DataTable cells, an available bundled font for the UnderWord underline, and a readable dashed GroupFrame composition. These are example changes; the pinned library implementation is unchanged. Inspect each seed decision and destination before comparing screenshots with the original fixtures.

There has been no package upgrade in this release. Existing consumers should keep the reviewed hash and use the one-time styles and dependency setup. Copy the complete example when adopting documentation improvements.

Write useful upgrade notes #

For each future revision, record its package version, full old and new hashes, and date. Explain additions, removals, renamed props, changed defaults or validation, token and font changes, and visible output differences. Include a concrete before/after migration for changes that require consumer action, and link to reviewed source with the repository-access label.

Distinguish a library behavior change from an example correction or a proposed documentation convention. Describe preserved limitations and explicitly replaced seed examples. Follow the pin update and verification workflow; a passing coverage count does not replace API review or visual inspection.