kuma encrypts the disk it installs, so this is 0.8.0

Minor rather than patch: `kuma install` gained the ability to encrypt a
disk, which is a thing a machine can now be, and `kuma doctor` gained a
line that says whether it is. The rest of the section is what fell out of
building that and out of following the install path far enough to find
what nobody had checked.

Cargo.lock moves with it. It carries the workspace member's own version,
so bumping only Cargo.toml leaves the two disagreeing and every --locked
call fails, which is most of CI.

Author: Letdown2491

CHANGELOG.md

@@ -5,6 +5,11 @@
 Entries land with the change they describe; the next tag takes this section
 as its release notes.
 
+## v0.8.0 (2026-08-15)
+
+The disk kuma installs can be encrypted, and the machine it makes says what
+it is and what it came from.
+
 ### Added
 
 - `kuma install` says when the image it is installing declares an account

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "kuma"
-version = "0.7.0"
+version = "0.8.0"
 edition = "2021"
 # Set by sha-crypt 0.6, the highest floor anything here asks for. Without
 # it, an older toolchain fails somewhere inside a dependency instead of