v0.9.0

Highlights

Tidycraft can now run without the desktop app.

The new tidycraft command uses the same scanner and rules as the app, which means it can now be used in CI, scripts, or other automated workflows.

tidycraft check .
tidycraft check . --fail-on warning

The CLI currently has four read-only commands:

• check — scan a project and report problems
• rules — show available rules and their current configuration
• explain — explain a rule
• scan — dump the asset inventory

None of these commands modify project files.

CI support

tidycraft check has predictable exit codes, configurable failure thresholds, and output in text, JSON, SARIF, or GitHub Actions annotations.

There's also a small composite GitHub Action included in the repo.

Baselines

Projects with existing findings can now record them as a baseline.

This makes it possible to start using Tidycraft on an existing project without fixing everything first: old findings stay quiet, while new ones introduced by later changes can still fail the check.

Duplicate groups are tracked by content, so simply renaming or removing an existing duplicate won't create unnecessary changes in the baseline.

Incomplete scans are now visible

A scan can sometimes miss files — for example when Git LFS files haven't been fetched, or when an asset can't be read properly.

Tidycraft now reports these cases instead of quietly pretending the scan was complete. --strict can be used if an incomplete scan should count as a failure.

CLI installation

Installing Tidycraft on Windows, Debian, or RPM-based Linux now also installs the tidycraft command.

The desktop executable itself has been renamed to tidycraft-desktop, so tidycraft can be used for the CLI.

macOS and AppImage users can use the standalone CLI binary from the release assets for now.

Tags now survive project moves

Tag bindings used to store absolute paths, which meant moving a project to another drive or opening it on another machine could leave the tags behind.

They are now stored relative to the project root.

Tag files are also written in a stable order, which should make diffs and merges a little cleaner. Existing files are converted the next time they are saved.

Other fixes

• Cloud AI runs now wait until the price estimate is shown. If the estimate fails, the run won't start.
• Tag changes that fail to save are no longer kept in memory as if they had succeeded.

Downloads

• Windows: .msi installer or -setup.exe installer (both install; there is no portable build)
• macOS (Apple Silicon): _aarch64.dmg
• macOS (Intel): _x64.dmg
• Linux: .deb, .rpm or .AppImage