Cut a release: machine mapping, dot sync, and the nix flake are unreleased, so Linux hosts fall back to the minimal profile on clone #95

Summary

The latest release is v0.6.6 (2026-07-27). Eight commits on main since then include user-facing features that multi-machine setups need, and their absence from release binaries produces surprising behavior on fresh installs:

• feat(bootstrap): profile inheritance and hostname-to-profile machine mapping #87 profile inheritance and hostname-to-profile machine mapping
• feat(sync): add dot sync for multi-machine reconciliation #88 dot sync for multi-machine reconciliation
• feat(nix): package the CLI as a flake; expand config paths; layout docs parity #89 nix flake packaging and expanded config paths
• fix(version): report ldflags or module version instead of unknown #90 version reporting fix (--version no longer says unknown)
• feat(planner): reject duplicate target paths across packages #91 duplicate target path rejection
• fix(clone): apply the cloned repository dot config to the same-invocation install #93 cloned repository dot config applied to the same-invocation install

Real-world impact observed

Bootstrapping an Ubuntu 24.04 host (hephaestus) with the v0.6.6 release binary:

dot clone https://github.com/jamesainslie/my-dotfiles.git --dir ~/.dotfiles --batch

The repository has a valid machines: section whose hephaestus* entry names the correct profile, but v0.6.6 predates #87, so the install silently fell back to the minimal default profile (2 packages instead of 13) and the remaining packages had to be managed by hand. The current HEAD behavior (batch clone resolves the profile from the hostname when no explicit profile is given) is exactly right; it just is not in any release.

Linux packaging notes

• Release assets cover dot_<version>_Linux_x86_64 and arm64, which suits Ubuntu hosts installing from the tarball or via go install.
• For NixOS hosts, the feat(nix): package the CLI as a flake; expand config paths; layout docs parity #89 flake is the idiomatic consumption path (for example as a home-manager flake input) instead of an ad hoc go install binary; that only becomes practical once a tagged release includes it.

Since #92 already lets feature commits bump the minor version, cutting the next release should publish all of the above as v0.7.0.