docs: capture Serenity majority migration plan

docs/planning/PD_FUTURE_STATE_ARCHITECTURE.md

@@ -164,7 +164,6 @@ Media / library:
 - Seerr
 - RomM
 - GameVault
-- Wizarr
 - Shelfmark
 - Notifiarr
 
@@ -201,8 +200,8 @@ Optional elsewhere:
 - high-risk security experiments on a future dedicated lab node if the school/lab workload outgrows PD-hosted segmented VMs
 
 ### Move off Serenity early; does not need the storage cutover
-- Wizarr -> PD or retire if no longer useful
-- Hawser + dockersocket -> PD or retire as a pair
+- retire Wizarr if it is still present; rebuild later only if onboarding need returns
+- Notifiarr -> PD only if PD headroom makes the move worth it
 - netdata -> keep only where it still adds monitoring value
 
 These are low-risk peel-off candidates because they are not part of the storage-local torrent/media locality lane.
@@ -258,7 +257,7 @@ Suggested policy posture:
 ### Phase 1: document and reduce Serenity sprawl now
 - document current host roles and future-state design
 - classify Serenity services into keep / move / retire
-- move low-risk non-storage-tied apps off Serenity first (`Wizarr`, `Hawser` + `dockersocket`, and possibly `netdata`)
+- retire or peel off only the smallest low-risk items first (`Wizarr`, maybe `Notifiarr`, and possibly `netdata`) while leaving `Hawser` + `dockersocket` in place as the Dockhand management path
 
 ### Phase 2: build upgraded PD
 - install TrueNAS Scale on the new PD hardware
@@ -279,8 +278,8 @@ Suggested policy posture:
 
 ### Phase 5: move or redesign the remaining special cases
 - move reranker onto PD if AI core lands there
-- redesign backup DNS so Serenity is no longer required
-- preserve at least one off-PD Technitium node on NOMAD
+- redesign backup DNS so Serenity is no longer required, likely by introducing a small dedicated Raspberry Pi 4B resolver lane while preserving an off-PD Technitium failure domain
+- preserve at least one off-PD Technitium node outside PD even after Serenity retires
 
 ### Phase 6: retire Serenity
 - verify pool adoption is complete
@@ -301,6 +300,6 @@ Suggested policy posture:
 
 For the current Serenity Docker review, the guiding rule is:
 - remove obvious sprawl from Serenity now
-- peel off the miscellaneous low-risk apps before touching the storage-locality lane
+- retire dead weight and peel off only the smallest miscellaneous low-risk apps before touching the storage-locality lane
 - do not over-optimize the final placement around Serenity permanence
 - remember that once PD directly owns the storage, the qbit/ARR locality argument flips to PD