the install section was the only account of how you get kuma

Every image ships /usr/bin/kuma as of 920f5e6, but the README still
described downloading a binary as the way to have one. Someone reading
Install on a kuma machine would curl a copy into /usr/local/bin, which
precedes /usr/bin in PATH, and quietly shadow the binary their own
image is built around with whatever version the release happens to be.

Two sentences. Install says who the download is for and that a kuma
machine already has one; "What needs what" says the same where a reader
checks whether a verb will work, since that is the section someone
consults when they already have a machine and never reaches Install.

Both README tests still pass: the download URL is untouched, and the
first toml block is not what changed.

Author: Letdown2491

README.md

@@ -114,6 +114,10 @@ every desktop asset are compiled into it. The published build is static, so
 it needs nothing installed alongside it. This matters on the machines most
 likely to want kuma, which tend to have podman and no compiler.
 
+This is for the machine you build from. A machine running a kuma image
+already has kuma at `/usr/bin/kuma`, baked in by the build that made the
+image, and a copy in `/usr/local/bin` would shadow it.
+
 ```console
 $ curl -LO https://github.com/Letdown2491/kuma-linux/releases/latest/download/kuma-x86_64-unknown-linux-musl
 $ chmod +x kuma-x86_64-unknown-linux-musl
@@ -148,7 +152,8 @@ made does not show up in the image.
 
 **What needs what.** `init`, `check`, `generate`, and `build` need only
 podman. `switch`, `update`, `rollback`, and `doctor` need to be running on a
-bootc machine. `vm` and `iso` need KVM and sudo.
+bootc machine, and a kuma one already has kuma. `vm` and `iso` need KVM and
+sudo.
 
 ## Quick start