leave the old applied dirs alone: no startup deletion. Refs #5913

docs/agent-lifecycle/config-changes.md

@@ -195,8 +195,8 @@ hive-c0re keeps no copy of an agent's config: the forge's `agent-configs/<name>`
 record what the agent's last successful build pinned, and nothing else.
 
 Older hives also kept an *applied* repo at `applied/<name>` and a *proposed*
-clone at `agents/<name>/config`. The startup migration removes the applied
-repos. Nothing reads the proposed clone any more, and you can delete it.
+clone at `agents/<name>/config`. Nothing reads either any more, and you can
+delete them.
 
 The container's `--flake` ref is `internal/meta` (see "Meta flake" above).
 The agent's `agent-configs/<n>/flake.nix`
@@ -271,9 +271,6 @@ host set up before the current deploy scheme (described above)
 converges to it automatically. Each phase is a no-op
 once already applied:
 
-- **Applied repos**: deletes the per-agent `applied/<n>` repos an earlier hive
-  kept. The deploy markers beside them stay. Non-destructive for everything
-  else — it doesn't touch live containers, state dirs, or claude creds.
 - **Agent files**: refreshes the files that follow the agent set
   (`agent_set::refresh`) from the current agent list. Set
   `HIVE_SKIP_META_MIGRATION=1` on the service to defer this phase.

docs/agent-lifecycle/persistence.md

@@ -547,8 +547,8 @@ Under `/var/lib/hyperhive/applied/` — the hive-c0re-only deploy markers
 `.<name>.hyperhive-rev` and `.<name>.config-rev`: the hyperhive and config
 commits the agent's last successful build pinned. No config lives here; the
 forge's `agent-configs/<name>` is the only copy. A hive that predates this
-finds per-agent `applied/<name>` repos here; `migrate::run` deletes them at
-startup.
+finds per-agent `applied/<name>` repos here. Nothing reads them any more, and
+you can delete them.
 
 Under `/var/lib/hyperhive/meta/` — system-level config files, plain state
 with no git history. The flake agents build from is the