redbear-mini: raise filesystem_size 512 -> 2048 MB to fit the package set

The mini package set (~350 MB compressed pkgars) extracts to well over 512 MB
uncompressed on the RedoxFS image. Once the "Package base not found" installer
bug was fixed (base now installs), image assembly reached file extraction and
aborted with "No space left on device (os error 28)" filling the 512 MB image.
The installer uses filesystem_size as the literal image size (no content-based
auto-sizing), so it must be large enough for the extracted set plus live
writable headroom. 2048 MB fits with margin. Packages are grown-into, never
trimmed (project ABSOLUTE RULE).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

config/redbear-mini.toml

@@ -10,7 +10,14 @@
 include = ["minimal.toml", "redbear-legacy-base.toml", "redbear-netctl.toml", "redbear-device-services.toml", "redbear-boot-stages.toml"]
 
 [general]
-filesystem_size = 512
+# The mini package set (base + full driver/daemon set, brush/bash/zsh, coreutils,
+# console net/diagnostic tools, iwlwifi/bluetooth firmware) is ~350 MB *compressed*
+# pkgars; the RedoxFS image holds the uncompressed extraction plus live writable
+# headroom, which overflows a 512 MB image (installer aborts with os error 28,
+# "No space left on device"). The installer does not content-size the filesystem —
+# this value is the literal image size — so it must fit the package set. 2048 MB
+# leaves comfortable headroom for a text-only live/recovery target.
+filesystem_size = 2048
 
 [users.messagebus]
 uid = 100