kuma installs itself now, so this is 0.7.0

0.6.0 could write a disk but only by handing the partitioning to bootc,
which foreclosed encryption and pulled the image into RAM. This version
owns the table, puts the image on the target, and has been run the way
somebody would actually run it: live ISO booted in a VM with 4G of
memory, `kuma install` from a terminal inside it, onto a 24G disk. The
result boots to its greeter, the account the installer was given logs
in, and `bootc status` shows the machine tracking the published image
rather than the media it came from.

Author: Letdown2491

CHANGELOG.md

@@ -5,6 +5,10 @@
 Entries land with the change they describe; the next tag takes this section
 as its release notes.
 
+## v0.7.0 (2026-08-15)
+
+Kuma installs itself, from media it made, onto a disk it partitioned.
+
 ### Behavior
 
 - `[system].shell` declares the login shell accounts on a machine get. It

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "kuma"
-version = "0.6.0"
+version = "0.7.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