remove the legacy meta repo's .git and the meta remotes at startup

docs/agent-lifecycle/config-changes.md

@@ -338,6 +338,10 @@ once already applied:
   repo, and 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.
+- **Legacy meta repo**: deletes the leftover `.git` in
+  `/var/lib/hyperhive/meta/` and the `meta` remote in each proposed repo.
+  The files beside the `.git` stay. The `core/meta` repo on the forge is
+  not touched.
 
 No state loss in either migration: claude creds, `/state/` notes, the
 events DB, and both proposed + applied history all survive. The root

docs/agent-lifecycle/persistence.md

@@ -388,8 +388,9 @@ here from merged config PRs) + any other files those PRs commit.
 denied tag history.
 
 Under `/var/lib/hyperhive/meta/` — system-level config files, plain state
-with no git history that anything reads. The flake agents build from is the
-swarm's `internal/meta`, not here. Contents:
+with no git history. The flake agents build from is the
+swarm's `internal/meta`, not here. A hive that predates this finds a
+leftover `.git` here; `migrate::run` deletes it at startup. Contents:
 
 - `topology.json` — the agent roster (`["alice", "bob", "ruth"]`).
   Written by `topology::reconcile` from `agent_set::refresh`; read by

docs/scheduler/coordinator.md

@@ -320,8 +320,8 @@ The hive keeps no flake of its own. `meta_rev.rs` picks the `internal/meta`
 commit an agent builds from and records it; `agent_set.rs` keeps the
 host-side files that follow the agent set (`topology.json`, the gateway's
 agent-socket map and nginx include) in line with the live agents, and
-`meta.rs` keeps the one remaining commit to the legacy `meta/` git repo, the
-removal of the permission seed files.
+`meta.rs` removes the permission seed files once the swarm has them, and
+`migrate.rs` deletes the legacy `meta/` repo's leftover `.git`.
 
 ---