docs: record Serenity created container pruning

docs/planning/SERENITY_CLEANUP_WAVE_1.md

@@ -72,7 +72,7 @@ From the live Serenity audit:
 
 Live execution on 2026-05-25 established:
 - `Huntarr` and `omegabrr` were low-risk stale stopped containers and were removed from Serenity
-- the recent non-running `Created` containers (`calibre-web`, `SuggestArr`, `Cleanuparr`, `calibre`, `agregarr`) were not blindly pruned because their metadata was touched recently and they may represent intentional but inactive templates
+- the recent non-running `Created` containers (`calibre-web`, `SuggestArr`, `Cleanuparr`, `calibre`, `agregarr`) were metadata-verified and then removed after confirming they were still only `Created`, had `restart=no`, and were not live workloads
 - `Unraid-Cloudflared-Tunnel` was audited, stopped, and removed after verification showed it was only transport-alive and no current public traffic depended on it
 - 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
 

docs/planning/SERENITY_DOCKER_AUDIT.md

@@ -83,7 +83,7 @@ These should be treated as cleanup targets unless a specific live dependency is
 ## Not-running / stale containers seen in `docker ps -a`
 These did not appear live and should be reviewed for deletion after confirming their data is not needed.
 
-Created only:
+Created only (retired on 2026-05-25 after metadata verification):
 - `calibre-web`
 - `SuggestArr`
 - `Cleanuparr`