Document Serenity source app container cleanup

docs/planning/SERENITY_CLEANUP_WAVE_1.md

@@ -78,6 +78,7 @@ Live execution on 2026-05-25 established:
 - the Serenity Pi-hole HA stack (`binhex-official-pihole`, `pihole-serenity`, `unbound-pihole-serenity`, `keepalived-pihole-serenity`) was then stopped and removed after live mixed-host DNS checks confirmed the Technitium path remained healthy without it
 - `gamevault` and `gamevault-db` validated healthy on PD, then Serenity `postgresql15` was exported, stopped, archived for rollback, and removed during D7
 - `romm` and `romm-db` validated healthy on PD, then Serenity `MariaDB-Official` was exported, stopped, archived for rollback, and removed during D7
+- the stale stopped Serenity source app container `romm` was then removed as post-cutover cleanup; `gamevault` was already absent from live inventory by that point, so rollback now depends on retained appdata/backup artifacts rather than source containers lingering in `docker ps -a`
 
 ## Wave 1-A: legacy Pi-hole removal
 

docs/servers/SERENITY.md

@@ -72,6 +72,7 @@ Serenity hosts the secondary backup Technitium node on `10.5.30.10`.
 - No GPU; reranker uses CPU-only TEI image
 - Tailscale active — reachable at `100.94.87.79` from any Tailscale node
 - Local Serenity DB containers for the old GameVault and RomM stacks (`postgresql15` and `MariaDB-Official`) were retired on 2026-05-25 after both apps validated healthy on PD.
+- The stale stopped source app containers for those old stacks were cleaned out afterward; rollback now lives in the retained appdata plus `/mnt/user/backups/doris/serenity-d7-db-retire-20260525-213531` rather than in lingering `docker ps -a` entries.
 - Cooldown/rollback artifacts for that retirement were retained on Serenity under `/mnt/user/backups/doris/serenity-d7-db-retire-20260525-213531`, and the original DB appdata paths were left in place rather than deleted immediately.
 
 ## Planned future role