drop the proposed config repo: applied seeds from forge main, and the dead pending-init topology list goes with it

docs/agent-lifecycle/persistence.md

@@ -254,11 +254,9 @@ than an accident of storage.
 
 Under `/var/lib/hyperhive/agents/<name>/`:
 
-- `config/` — the proposed nix repo (root-agent-editable). Bind-mounted
-  **read-only** to `/agents/<name>/config` inside the sub-agent's own
-  container so the agent can inspect what defines it and request
-  precise changes from the root agent; RW into the root agent via the
-  `/agents` tree bind.
+- `config/` — unused. Older hives kept a proposed nix repo here; nothing
+  reads it any more, and you can delete it. The agent's config mount at
+  `/agents/<name>/config` is the applied repo, read-only.
 - `claude/` — claude OAuth credentials, bind-mounted RW to
   `/home/<name>/.claude` inside the container.
 - `state/` — durable notes and `hyperhive-harness.json`. Bind-mounted
@@ -487,7 +485,7 @@ boundary a convention rather than a permission.
 
 <!-- vale write-good.Passive = NO -->
 ⚠️ Don't confuse it with the config-repo seeding hive-c0re does at
-spawn (`lifecycle::setup_proposed`): that writes the agent's initial
+spawn (`lifecycle::setup_applied`): that writes the agent's initial
 config repo as **hive-c0re, against the host path**, and `read_only` on a bind
 constrains writers *inside* a container only. The two are unrelated —
 conflating them can lead you to reason your way into thinking this