Install the boot splash theme and set up GRUB without Limine

docs/install.md

@@ -74,9 +74,10 @@ with `--check`.
    avahi, docker, power-profiles-daemon, and oomd.
    `NetworkManager-wait-online.service` is masked so a slow DHCP lease cannot
    hold up the login screen, and `plymouth-start.service` and
-   `plymouth-quit-wait.service` are masked because Blob configures no boot
-   splash: an unconfigured plymouth holds the console and leaves the machine
-   with neither a greeter nor a TTY. See [packages.md](packages.md).
+   `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
+   [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
    missing or whether systemd has simply not re-read its units yet, and carries

docs/packages.md

@@ -72,7 +72,7 @@ Two are worth knowing about:
 `install.sh` installs what is missing before it writes any config:
 
 ```
-packages/blob.packages       121 packages from core, extra, multilib
+packages/blob.packages       123 packages from core, extra, multilib
 packages/blob-aur.packages    11 packages with no official equivalent
 ```
 
@@ -136,23 +136,27 @@ Omarchy's own package list, because they were installed by hand on this machine:
 
 `playerctl` is in official `extra`, so it sits in the repo list.
 
-## No boot splash
+## The boot splash
 
-`plymouth` is deliberately not on either list. Blob configures no splash: there
-is no mkinitcpio hook, no kernel command line, and `default/plymouth/` ships no
-theme assets, so `blob-plymouth-set` has nothing to publish either. 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` masks `plymouth-start.service` and `plymouth-quit-wait.service` for
-that reason, which un-breaks a machine that already has the package. To go
-further:
+`plymouth` is installed but left inert, and the splash is opt-in through one
+command:
 
 ```
-sudo pacman -Rns plymouth
+blob boot                    # branding/boot_flash.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`
+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
+(`quiet splash vt.global_cursor_default=0`), because that line is the one thing
+it will not rewrite for a bootloader other than GRUB.
+
 ## Updating
 
 ```