fix: keep both cases on lakka and retropie

Both run on Linux but inherited RetroArch's case folding, so a core
file differing from a platform name only by case left their packs:
MesenCE's bios.col and np2kai's lowercase 2608_*.wav, which those
cores open with that exact case. They are now case-sensitive, the
shared groups fold only where the platform does, and Lakka gets its
own pack instead of sharing RetroArch's.

wiki/advanced-usage.md

@@ -202,9 +202,9 @@ python scripts/generate_pack.py --all --all-variants --output-dir dist/
 ```
 
 `--all-variants` builds all six combinations in one run, producing names like
-`RetroArch_Lakka_v1.22.2_BIOS_Pack.zip`,
-`RetroArch_Lakka_v1.22.2_Platform_BIOS_Pack.zip` and
-`RetroArch_Lakka_v1.22.2_Truth_Required_BIOS_Pack.zip`.
+`RetroArch_v1.22.2_BIOS_Pack.zip`,
+`RetroArch_v1.22.2_Platform_BIOS_Pack.zip` and
+`RetroArch_v1.22.2_Truth_Required_BIOS_Pack.zip`.
 
 Which one to pick: `full` is the one to ship, since it covers alternate cores
 and optional firmware. `platform` is much smaller and matches exactly what the

wiki/architecture.md

@@ -147,11 +147,13 @@ entries that are out of scope here.
 ## Pack grouping
 
 Platforms that produce identical packs are grouped automatically.
-Two platforms share a pack when they declare the same files and run the same
-emulators. RetroArch and Lakka do, so they produce one combined pack
-(`RetroArch_Lakka_BIOS_Pack.zip`). RetroPie inherits RetroArch's systems but
-ships its own package list, standalone emulators included, so it gets a
-separate pack and a separate install manifest.
+Two platforms share a pack when they declare the same files, run the same
+emulators and see file names the same way. Lakka declares RetroArch's files
+and cores but runs on Linux, where `bios.col` and `BIOS.col` are two files
+that different cores open; RetroArch's pack folds them for Windows and macOS.
+So Lakka gets its own pack. RetroPie inherits RetroArch's systems but ships its
+own package list, standalone emulators included, and is case-sensitive too, so
+it gets a separate pack and a separate install manifest.
 With `--target`, the fingerprint includes target cores so platforms
 with different hardware filters get separate packs. Emulator and system packs
 also retain system identity, `variant_group` and requested region; same-named

wiki/troubleshooting.md

@@ -267,9 +267,11 @@ python scripts/download.py --list
 bash scripts/download.sh --list
 ```
 
-Some platforms share packs (Lakka uses the RetroArch pack). The installer handles
-this mapping automatically, but if you're downloading manually, check which pack
-name corresponds to your platform.
+A pack's name lists every platform it serves. Releases built before
+October 2026 ship RetroArch and Lakka as one `RetroArch_Lakka` pack; later
+ones give Lakka its own, since Lakka runs on Linux where two names that differ
+by case are two files. The installer and the download scripts find the right
+pack either way.
 
 **A pack in several parts will not extract:**