Set the boot splash to blob_boot.png during install

docs/install.md

@@ -15,6 +15,7 @@ with `--check`.
 | `install/steps/packages.sh` | repo and AUR packages, and the yay bootstrap |
 | `install/steps/config.sh` | the `BLOB_PATH` symlink, everything under `~/.config`, and the login shell profile |
 | `install/steps/services.sh` | system services, systemd drop-ins, user units |
+| `install/steps/boot.sh` | the Plymouth boot splash |
 | `install/steps/theme.sh` | the wallpaper link, the first theme, the first background |
 | `install/steps/login.sh` | SDDM, the session entry, and the first launch |
 | `install/steps/reload.sh` | reloading systemd, the user services, and a running session |
@@ -78,7 +79,11 @@ with `--check`.
    hold up the login screen, and `plymouth-start.service` and
    `plymouth-quit-wait.service` are masked because an unconfigured plymouth
    holds the console and leaves the machine with neither a greeter nor a TTY.
-   `blob boot` unmasks them when it sets the splash up. See
+   The installer then applies `branding/blob_boot.png` as the boot splash
+   through `blob boot`, which installs the theme, adds the mkinitcpio hook,
+   unmasks the plymouth units and rebuilds the initramfs. It is skipped when
+   the blob theme is already the default with the same image, and once it is
+   in place the plymouth units are no longer masked on later runs. See
    [packages.md](packages.md#the-boot-splash).
 9. **The login screen** is SDDM. It has to be installed first: if
    `sddm.service` is not there, the installer says whether the package is

docs/packages.md

@@ -138,19 +138,18 @@ Omarchy's own package list, because they were installed by hand on this machine:
 
 ## The boot splash
 
-`plymouth` is installed but left inert, and the splash is opt-in through one
-command:
+`install.sh` sets the splash to `branding/blob_boot.png`. To change it later:
 
 ```
-blob boot                    # branding/boot_flash.png
+blob boot                    # branding/blob_boot.png
 blob boot ~/some/image.png   # or any other image
 ```
 
-The reason it is opt-in is that an installed but *unconfigured* plymouth is not
-harmless: it takes the console at boot and never hands it back, and
-`getty@tty1` waits on `plymouth-quit-wait.service`, so the machine reaches
-neither the greeter nor a TTY. `install.sh` therefore masks
-`plymouth-start.service` and `plymouth-quit-wait.service`, and `blob boot`
+An installed but *unconfigured* plymouth is not harmless: it takes the console
+at boot and never hands it back, and `getty@tty1` waits on
+`plymouth-quit-wait.service`, so the machine reaches neither the greeter nor a
+TTY. `install.sh` therefore masks `plymouth-start.service` and
+`plymouth-quit-wait.service` until the splash is configured, and `blob boot`
 unmasks them as part of configuring everything else - the theme in
 `default/plymouth/`, the `plymouth` mkinitcpio hook, and the initramfs rebuild.
 It finishes by printing the kernel parameters your bootloader still needs