Archive legacy ARR Kubernetes manifests

README.md

@@ -833,10 +833,10 @@ The ARR/media stack is intentionally not deployed by the Kubernetes app
 pipeline. It is better suited to a Docker Compose stack on the Debian host with
 persistent volumes under `/data`, where large media paths, qBittorrent writes,
 and service config directories can survive cluster rebuilds without OpenEBS
-node-affinity or PVC migration concerns. The legacy `apps/arr-stack` manifests
-are retained only as migration reference. The active host-level Compose
+node-affinity or PVC migration concerns. The active host-level Compose
 definition lives under `infra/arr-stack` and stores persistent data under
-`/data/arr`.
+`/data/arr`. Historical Kubernetes manifests are archived under
+`archive/apps/arr-stack` for migration reference only.
 
 ## Storage
 

README.md.tmpl

@@ -833,10 +833,10 @@ The ARR/media stack is intentionally not deployed by the Kubernetes app
 pipeline. It is better suited to a Docker Compose stack on the Debian host with
 persistent volumes under `/data`, where large media paths, qBittorrent writes,
 and service config directories can survive cluster rebuilds without OpenEBS
-node-affinity or PVC migration concerns. The legacy `apps/arr-stack` manifests
-are retained only as migration reference. The active host-level Compose
+node-affinity or PVC migration concerns. The active host-level Compose
 definition lives under `infra/arr-stack` and stores persistent data under
-`/data/arr`.
+`/data/arr`. Historical Kubernetes manifests are archived under
+`archive/apps/arr-stack` for migration reference only.
 
 ## Storage