refactor(hive-c0re): drop the request_init_config tool and InitConfig approval

swarm-controller's `InitAgentConfigRepo` node already covers config-repo
creation, so this deletes a duplicate rather than a capability; old
`init_config` rows are skipped by `collect_lenient` with no migration, by
operator decision.

Refs #4398

docs/agent-lifecycle/agent-hierarchy.md

@@ -21,11 +21,10 @@ Topology lives in the hive-c0re-owned **meta repo**, alongside
 
 `null` = root-level agent. New agents **default to root** — there is no
 structural manager that everything hangs under. Hierarchy is built
-explicitly: an agent that requests a sub-agent gets a
-requester-as-parent edge written at its `init_config` approval (so
-`alice` spawned `bob` above), and the operator can reparent any
-agent, including the bootstrap container (`ruth`) — it's just another
-root. The manager is reparentable like any other agent; there's no
+explicitly: an agent gets a parent edge written before its first spawn,
+or the operator reparents it afterwards (so `bob` above sits under
+`alice`). Any agent is reparentable, the bootstrap container (`ruth`)
+included — it's just another root. The manager is reparentable like any other agent; there's no
 "structurally root" carve-out. Its privileges live on its MCP socket,
 not its tree position (see _Manager special-casing today_ below).
 
@@ -63,10 +62,11 @@ where system-level facts live.
   install that hasn't synced yet).
 - **Reconcile** — runs alongside the periodic meta/flake regeneration.
   New agents default to root unless they already carry an explicit
-  parent edge from an `init_config` approval; Reconcile preserves existing entries
-  (including operator overrides); removed agents drop.
-  Agents that are approved but not yet spawned keep their edge too, so
-  it survives the gap until the container actually appears.
+  parent edge written before their first spawn; Reconcile preserves
+  existing entries (including operator overrides); removed agents drop.
+  Agents whose config repo exists but that haven't spawned yet keep
+  their edge too, so it survives the gap until the container actually
+  appears.
 - **Inject** — hive-c0re exposes each container's parent (if any) to its own
   environment as `HIVE_PARENT`, so the harness / system-prompt
   renderer can see it.
@@ -90,7 +90,6 @@ umount-old / mount-new / restart-cascade step.
 | operation                                                   | who can do it                                                                           |
 | ----------------------------------------------------------- | --------------------------------------------------------------------------------------- |
 | `kill` / `start` / `restart` / `update` (any descendant)    | any ancestor                                                                            |
-| `request_init_config` (spawn a new child)                   | any agent, child added under self                                                       |
 | config change via forge PR (any descendant's config)        | any ancestor                                                                            |
 | `get_logs` (any descendant)                                 | any ancestor                                                                            |
 | moderate reminders (cancel any open thread of a descendant) | any ancestor                                                                            |
@@ -110,15 +109,15 @@ other agents don't:
 - **Naming/bootstrap** — the manager's broker recipient name, state-dir
   key, and nixos-container name are all `ruth` (container `h-ruth`).
   `hive-c0re` spawns it directly at boot if missing, with no operator
-  approval step — every other agent goes through `request_init_config`
-  → approval. Topology-wise, `ruth` is still just another root agent.
+  approval step — every other agent goes through a `Spawn` approval.
+  Topology-wise, `ruth` is still just another root agent.
 - **Wire-protocol** — the privileged `Request` variants
-  (`RequestInitConfig`; `Kill` / `Start` / `Restart` / `Update`;
+  (`Kill` / `Start` / `Restart` / `Update`;
   `GetLogs`; `RequestUpdateMetaInputs`) — marked `*(privileged)*` in
   `hive-core-agent-sock`'s unified `Request` enum — are reachable only
   from the manager's socket flavour today. Planned rule for each is in the
-  table above ("any agent, child added under self" for init-config,
-  "any ancestor" for lifecycle/logs); `RequestUpdateMetaInputs` stays
+  table above ("any ancestor" for lifecycle/logs);
+  `RequestUpdateMetaInputs` stays
   a root-only capability even post-milestone, not a topology rule.
   One exception: `Wake` (inject a `from: <X>` message into the
   caller's own inbox) isn't really privileged — every per-agent daemon