Integrate Instruments release seed

Download and verify the selected release during image builds.
Bootstrap it once into the first graphical user's XDG directories.

1 files changed, 19 insertions, 0 deletions

diff --git a/README.md b/README.md
index 0fc3ba4..3fc11c5 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,25 @@ FROM ghcr.io/ublue-os/bazzite-deck:stable
 
 By focusing strictly on file overlays and configuration writing, this build intentionally avoids invasive operations like `dnf5 install/remove`, COPR enablement, akmods pulls, or kernel recompilations. This architectural choice keeps AeroCore OS completely immune to Fedora/COPR dependency drift during major upstream transition windows (e.g., Bazzite 43 to 44).
 
+## AeroCore Booster integration
+
+Image builds download the selected AeroCore Booster release from
+`AeroCore-IO/booster-installer`, verify its published SHA-256 checksum, and
+store the complete release seed under `/usr/share/aerocore-booster-release`.
+The release installer runs once for the first active graphical user and copies
+the application into that user's XDG directories. After bootstrapping, updates
+and uninstallation remain owned by the normal Instruments user-space installer.
+The bootstrap completion marker is stored at
+`/var/lib/aerocore/instruments-bootstrap-complete`, so uninstalling the user
+application does not cause the image seed to reinstall it on the next boot.
+Remove that marker and enable `aerocore-instruments-setup.service` to explicitly
+bootstrap the application again.
+
+Set `INSTRUMENTS_VERSION` to a release tag for reproducible builds, or leave it
+as `latest` for rolling development images. Set `INSTRUMENTS_ENABLED=false` to
+build without Booster. The release repository and API base can be overridden
+with `INSTRUMENTS_RELEASE_REPOSITORY` and `INSTRUMENTS_RELEASE_API_BASE`.
+
 ---
 
 ## Key Features & Optimizations