diff --git a/docs/ecosystem/fpkgi.md b/docs/ecosystem/fpkgi.md
index 495eb23..2cb77c7 100644
--- a/docs/ecosystem/fpkgi.md
+++ b/docs/ecosystem/fpkgi.md
@@ -1,10 +1,68 @@
---
-status: placeholder
-wave: 3
+title: fpkgi
+description: Install PS4 / PS5 packages from your RomM library via fpkgi homebrew.
---
# fpkgi
-!!! warning "Placeholder — RomM 5.0 docs overhaul"
- This page is part of the RomM 5.0 documentation overhaul (Wave 3) and
- has not been written yet. See the overhaul plan for status and ownership.
+[fpkgi](https://github.com/CyberYoshi64/fpkgi) is PS4 / PS5 homebrew for installing `.pkg` packages from custom URL feeds. RomM exposes fpkgi-compatible feeds for its PS4 and PS5 libraries.
+
+New in RomM 5.0 — earlier versions didn't have fpkgi feeds.
+
+## Prerequisites
+
+- **PS4 or PS5** with fpkgi installed (requires CFW / jailbreak — setup is out of scope here).
+- **RomM reachable from the console over Wi-Fi** — LAN simplest.
+- Games stored as `.pkg` files — fpkgi, like pkgj, only handles the Sony installer format.
+
+## Feed URL
+
+```text
+{romm_url}/api/feeds/fpkgi/{platform_slug}
+```
+
+Where `{platform_slug}` is:
+
+- `ps4` for PlayStation 4 content.
+- `ps5` for PlayStation 5 content.
+
+Example:
+
+```text
+http://192.168.1.100:3000/api/feeds/fpkgi/ps4
+```
+
+The feed returns JSON in the fpkgi-expected schema — titles, title IDs, content types, URLs back to RomM for the actual downloads.
+
+## Configuring fpkgi
+
+Exact steps depend on the fpkgi version, but the gist:
+
+1. Put RomM's feed URL in fpkgi's config (usually a JSON file on the console; check fpkgi's own docs).
+2. Restart fpkgi.
+3. The RomM library appears in fpkgi's browse view.
+
+Consult [fpkgi's README](https://github.com/CyberYoshi64/fpkgi) for the current config-file location and format — the project moves faster than these docs.
+
+## Authentication
+
+The `/api/feeds/fpkgi/` endpoints support basic auth the same way `/api/feeds/pkgi/` does. Either:
+
+- Set basic-auth credentials in fpkgi's config if it supports them, OR
+- Set `DISABLE_DOWNLOAD_ENDPOINT_AUTH=true` on the RomM server (see the [Tinfoil](tinfoil.md) caveat about public exposure).
+
+## File format — must be `.pkg`
+
+PS4 `.pkg` files specifically — not `.iso`, not compressed. RomM filters to `.pkg` when building the feed. Any other file types are invisible to fpkgi.
+
+## Troubleshooting
+
+- **Feed is empty** — no `.pkg` files on the `ps4` / `ps5` platform. Check your library.
+- **Downloads fail with 401** — auth config mismatch. See Authentication section above.
+- **Downloads succeed but install fails** — `.pkg` is for a different firmware version. Not a RomM problem.
+
+## See also
+
+- [Feeds reference](../reference/feeds.md) — all feed endpoints.
+- [pkgj](pkgj.md) — PS Vita / PSP equivalent.
+- [fpkgi upstream](https://github.com/CyberYoshi64/fpkgi) — installer homebrew.
diff --git a/docs/ecosystem/igir.md b/docs/ecosystem/igir.md
index 37737b2..47a5892 100644
--- a/docs/ecosystem/igir.md
+++ b/docs/ecosystem/igir.md
@@ -1,10 +1,173 @@
---
-status: placeholder
-wave: 3
+title: Igir Collection Manager
+description: Clean up and normalise your ROM collection with Igir before importing into RomM.
---
# Igir Collection Manager
-!!! warning "Placeholder — RomM 5.0 docs overhaul"
- This page is part of the RomM 5.0 documentation overhaul (Wave 3) and
- has not been written yet. See the overhaul plan for status and ownership.
+[Igir](https://igir.io/) is a zero-setup ROM collection manager — sorts, filters, extracts, archives, patches, and reports on collections of any size. Not a RomM companion per se; more a pre-processing tool. Useful for cleaning up a library *before* importing into RomM, so RomM's scans have a better-named, better-organised starting point.
+
+**This is not an official RomM app.** Igir is a separate community project. We document integration here because it's a common workflow and produces a RomM-compatible layout directly.
+
+## When you'd use Igir
+
+- You have a messy collection — inconsistent naming, mixed formats, dumps from multiple sources.
+- You want to **match against No-Intro / Redump DAT files** to verify authenticity and standardise names.
+- You want to **filter** — only retail releases, strip out hacks, keep only one region, etc.
+- You want to move / rename files to RomM's expected platform folder layout.
+
+If your library is already clean, skip Igir. RomM's scans handle naming variations gracefully.
+
+## Directory setup
+
+Igir works on a copy of your ROMs — never in place — to let you iterate on its config without risking the originals.
+
+```text
+.
+├── dats/ # DAT files (No-Intro, Redump)
+├── roms/ # Your original ROM collection (untouched)
+├── roms-unverified/ # Working copy Igir will process
+└── igir-romm-cleanup.sh # the script below
+```
+
+### 1. Make a working copy
+
+```sh
+cp -r roms/ roms-unverified/
+```
+
+### 2. Download DAT files
+
+DAT files are hash-referenced catalogues Igir matches against.
+
+- **Cartridge systems:** [No-Intro daily](https://datomatic.no-intro.org/index.php?page=download&op=daily) — full DAT compilation.
+- **Optical systems (PS1, Saturn, etc.):** [Redump](http://redump.org/downloads/) — per-platform DAT files.
+
+Drop the DAT files into `dats/`. You can use a subset if you only care about specific platforms.
+
+## The cleanup script
+
+Save as `igir-romm-cleanup.sh`:
+
+```bash
+#!/usr/bin/env bash
+set -ou pipefail
+cd "$(dirname "${0}")"
+
+INPUT_DIR=roms-unverified
+OUTPUT_DIR=roms-verified
+
+# https://igir.io/
+# DAT files: https://datomatic.no-intro.org/index.php?page=download&op=daily
+time npx -y igir@latest \
+ move \
+ extract \
+ report \
+ test \
+ -d dats/ \
+ -i "${INPUT_DIR}/" \
+ -o "${OUTPUT_DIR}/{romm}/" \
+ --input-checksum-quick false \
+ --input-checksum-min CRC32 \
+ --input-checksum-max SHA256 \
+ --only-retail
+```
+
+Make it executable:
+
+```sh
+chmod +x igir-romm-cleanup.sh
+```
+
+### What it does
+
+- `move extract` — extract archives and move the results.
+- `test` — verify checksums against DATs.
+- `report` — generate a markdown report of matches / misses.
+- `-o ${OUTPUT_DIR}/{romm}/` — output in RomM's expected platform layout (`{romm}` is Igir's RomM-layout template).
+- `--only-retail` — exclude betas, hacks, unlicensed dumps.
+- `--input-checksum-*` — check files thoroughly (slow but authoritative).
+
+## Run
+
+```sh
+./igir-romm-cleanup.sh
+```
+
+Output:
+
+- `roms-verified/{platform-slug}/{Proper Game Name}.rom` — identified ROMs in RomM layout.
+- `roms-unverified/` — whatever Igir didn't identify, still available for manual review.
+- `report.csv` (or similar) — what matched, what didn't.
+
+## Manually migrate leftovers
+
+Some ROMs Igir won't identify (homebrew, hacks with `--only-retail`, truly unknown dumps). Move them manually preserving the folder shape:
+
+```sh
+npx -y igir@latest \
+ move \
+ -i roms-unverified/ \
+ -o roms-verified/ \
+ --dir-mirror
+```
+
+This keeps the original subfolder structure but normalises extensions.
+
+## Multi-disc reorganisation
+
+Igir outputs multi-disc games as separate folders, which confuses RomM's multi-file game detection. Collapse them:
+
+```sh
+cd roms-verified/ps # or psx, or whatever your PSX slug is
+
+ls -d *Disc* | while read file; do
+ game=$(echo "${file}" | sed -E 's/ ?\(Disc.*//')
+ mkdir -p "${game}"
+ mv "${file}" "${game}"
+ m3u="${game}/${game}.m3u"
+ touch "${m3u}"
+ echo "${file}" >> "${m3u}"
+done
+```
+
+Before:
+
+```text
+Final Fantasy VII (Disc 1) (USA)/
+Final Fantasy VII (Disc 2) (USA)/
+Final Fantasy VII (Disc 3) (USA)/
+```
+
+After:
+
+```text
+Final Fantasy VII (USA)/
+ Final Fantasy VII (Disc 1) (USA)/
+ Final Fantasy VII (Disc 2) (USA)/
+ Final Fantasy VII (Disc 3) (USA)/
+ Final Fantasy VII (USA).m3u
+```
+
+The `.m3u` is a playlist RomM respects for launching multi-disc games.
+
+## Import into RomM
+
+Once `roms-verified/` looks right, mount it as RomM's library:
+
+```yaml
+services:
+ romm:
+ volumes:
+ - /path/to/roms-verified:/romm/library/roms:ro
+```
+
+Read-only is safer — if you need Igir to re-clean, you work in the parallel `roms-unverified/` and re-promote to `roms-verified/`.
+
+Run a scan from RomM. Everything should match cleanly against providers.
+
+## See also
+
+- [Igir docs](https://igir.io/) — the upstream reference.
+- [Folder Structure](../getting-started/folder-structure.md) — what RomM expects on-disk.
+- [Metadata Providers](../administration/metadata-providers.md) — how RomM matches after Igir's done its work.
diff --git a/docs/ecosystem/kekatsu.md b/docs/ecosystem/kekatsu.md
index b5df388..a70f56a 100644
--- a/docs/ecosystem/kekatsu.md
+++ b/docs/ecosystem/kekatsu.md
@@ -1,10 +1,61 @@
---
-status: placeholder
-wave: 3
+title: Kekatsu
+description: Nintendo DS multiboot loader — install DS games from RomM via custom feed.
---
# Kekatsu
-!!! warning "Placeholder — RomM 5.0 docs overhaul"
- This page is part of the RomM 5.0 documentation overhaul (Wave 3) and
- has not been written yet. See the overhaul plan for status and ownership.
+**Kekatsu** is Nintendo DS homebrew for loading games from a custom URL feed. RomM exposes a Kekatsu-compatible feed for its DS library.
+
+New in RomM 5.0.
+
+## Prerequisites
+
+- A Nintendo DS with Kekatsu installed (requires a flashcart or homebrew launcher).
+- **RomM reachable from the DS over Wi-Fi** — the DS's Wi-Fi is WEP / old WPA only, so this typically means a dedicated legacy-SSID on your router or a travel router bridging the DS to your modern network.
+- DS games in `.nds` format.
+
+## Feed URL
+
+```text
+{romm_url}/api/feeds/kekatsu/{platform_slug}
+```
+
+For standard DS content, the platform slug is `nds`:
+
+```text
+http://192.168.1.100:3000/api/feeds/kekatsu/nds
+```
+
+## Configuring Kekatsu
+
+Exact config steps depend on your Kekatsu build; the shared concept is "point the app at this URL and it fetches the manifest". Consult Kekatsu's own docs for the current config-file location.
+
+## File format
+
+`.nds` only. DSi Ware / iQue / other formats aren't listed in the feed.
+
+## Authentication
+
+Kekatsu can send basic auth. Either configure it on the DS side or enable `DISABLE_DOWNLOAD_ENDPOINT_AUTH=true` on RomM (see the [Tinfoil download-auth caveat](tinfoil.md#prerequisites)).
+
+## Why the legacy-Wi-Fi hassle
+
+The DS's original Wi-Fi hardware supports WEP and an older WPA variant only. Modern home routers usually don't. Workarounds:
+
+- **Dedicated DS-friendly SSID.** Many routers allow per-SSID security — add a WEP one just for the DS.
+- **Travel router in bridge mode.** A cheap travel router configured for WEP uplinks to your main (secure) network.
+- **Use a DSi, 3DS, or homebrew replacement driver** — these support modern security.
+
+If none of this is appealing, Kekatsu-over-LAN isn't going to work; fall back to sideloading via flashcart or similar.
+
+## Troubleshooting
+
+- **Feed is empty** — no `.nds` files on the `nds` platform.
+- **DS can't see the network** — see the legacy-Wi-Fi section above.
+- **Downloads fail** — either network timeout (LAN latency over WEP is rough) or disk space. Retry one game at a time.
+
+## See also
+
+- [Feeds reference](../reference/feeds.md) — all feed endpoints.
+- Kekatsu upstream — find via the RomM Discord `#kekatsu` or community links (project moves).
diff --git a/docs/ecosystem/muos-app.md b/docs/ecosystem/muos-app.md
index bfb2bfc..07f3692 100644
--- a/docs/ecosystem/muos-app.md
+++ b/docs/ecosystem/muos-app.md
@@ -1,10 +1,100 @@
---
-status: placeholder
-wave: 3
+title: muOS App
+description: Official RomM app for muOS and EmulationStation handhelds — fetch games wirelessly.
---
+
+
# muOS App
-!!! warning "Placeholder — RomM 5.0 docs overhaul"
- This page is part of the RomM 5.0 documentation overhaul (Wave 3) and
- has not been written yet. See the overhaul plan for status and ownership.
+
+
+
+
+