Reference
Versions and support status
Use one exact framework release across the package tree, and read each package status before you adopt its surface.
Verified against smrt 0.55.16
Use one exact release
All framework packages release together. Install the same exact version for every @happyvertical/smrt-* dependency. Do not mix exact and range versions.
- A split package tree can load more than one ObjectRegistry singleton. Objects registered in one copy are then absent from the other copy.
- The package reference shows the verified release on every entry.
- The source link on a package page uses the matching release tag.
Read the status before adoption
A stable package has a released implementation. A foundation package is a required core layer. A source-distribution package needs repository-specific installation. A not-implemented package is a published placeholder and must not be presented as working behavior.
- Package notices state known limitations before the workbench tabs.
- Playground entries appear only when a package publishes or registers a working preview.
- Generated-interface tabs identify packages that do not define a representative resource.
Use source evidence
Treat the package manifest, README, AGENTS.md, exported declarations, and package-owned Playground module as the canonical evidence for a released surface. This site links to that evidence instead of copying an upstream generator output by hand.