Changelog

This project uses a single latest-docs strategy.

• Docs always describe the current released CLI behavior.
• Version is displayed globally in docs and synced from the root package version.

Current Version

See the version label in the docs footer.

Release Notes Process

1. Update CLI behavior and tests.
2. Update relevant docs pages in the same change.
3. Bump version at the root package.
4. Build and deploy docs.

Historical Changes

For now, historical release notes are tracked in Git history and pull requests. If release volume grows, we can add a dedicated versioned changelog format later.