CLI Changelog

[Unreleased]

Reworked Tailwind token deduplication in init to use CLI-managed CSS block markers instead of content sentinels, making sync idempotent and resilient to future token bundle shape changes.

Returned non-zero exit codes for fatal CLI command outcomes (add without config and init with unsupported Svelte), so automation and CI can fail correctly.
Normalized missing-component handling in motion-core add by mapping unresolved slugs to a typed ComponentNotFound error, preserving graceful CLI failure output instead of bubbling a generic internal error.
Stopped implicit conflict overwrites in non-interactive add; conflicting files now require explicit --yes approval (or MOTION_CORE_CLI_ASSUME_YES).
Removed duplicate package installation attempts when the same dependency was required in both runtime and dev scopes during motion-core add.
Hardened Tailwind CSS discovery in init to skip unreadable/binary .css files instead of aborting workspace setup.
Guarded package-manager execution against Unknown backend to prevent fallback commands from reporting false-positive success.
Replaced panic-prone config serialization in save_config with explicit error propagation (ConfigError::Serialize).
Cleared strict Rust linting debt across CLI and core (pedantic, nursery, perf) with targeted refactors and API docs, keeping cargo clippy clean under -D warnings.

Resolved strict Clippy warnings across CLI core modules to keep builds and CI checks clean under stricter lint settings.

Enhanced error reporting and overall CLI stability for a smoother user experience.

Reduced binary size and improved execution speed by removing unused dependencies and enabling Link Time Optimization (LTO).
Optimized default build features to ensure a lighter executable footprint.
Expanded test suite coverage to ensure higher reliability of core commands.

Added automatic injection of CSS variables (tokens) into the project’s global CSS file during component installation.

Fixed an issue where test-specific imports could leak into the production build.

Implemented a safety check that detects modifications in existing components before overwriting them.
Added support for partial updates to component files.

Added capability to install shared utility types and TypeScript definitions required by certain components.

Added support for installing complex components that consist of multiple entry files (e.g., flip-grid).

Established cross-platform End-to-End testing to ensure consistent behavior on Windows, macOS, and Linux.

Fixed command execution issues when invoking package managers (npm, pnpm, yarn, bun) on Windows.

Extended CLI capabilities to automatically download and place necessary static assets (images, 3D models) for components.

Fixed asset path resolution to prevent redundant category directories in the public folder.

Introduced a caching mechanism for initialization to improve performance and reliability.
Added semantic version compatibility checks for dependencies prior to installation.

Standardized component templates to use the registry-provided cn utility for class merging.
Cleaned up internal dependencies.