Description
OnchainKit exposes a growing set of components, hooks, and utilities, but the documentation does not clearly indicate which APIs are considered stable and which may change over time. This makes it harder for developers to confidently adopt certain parts of the library in production environments.
Proposed Solution
Add clear documentation that labels APIs as stable, evolving, or experimental, either through a dedicated section or inline annotations. The guidance should explain what each label means in terms of expected stability and change frequency.