topology: drop the parent field and the hierarchy it fed

`topology.json` was a map of `name -> parent | null`, and that value fed
the whole agent hierarchy: `<parent>` / `<children>` recipient sentinels,
the reparenting API (CLI verb, wire verb, dashboard endpoints, DAG node),
the dashboard tree, the rebuild depth sort, and an unconditional
bind-mount grant giving every agent RW on its direct children's state.

Per the operator's ruling the field goes, and with it all of the above.
The file survives as what remains once the value is gone: the roster of
agent names, which is the set `ManageRootAgent` grants mounts over. It is
now a JSON array; `read` still accepts the old map shape and keeps its
keys, so a hive that upgrades across this does not blank its roster (and
so no capability holder loses its mounts for the length of that window).

Two sites kept their behaviour under a different recipient rather than
losing it. Both addressed `<parent>`, which the broker already resolved to
`operator` for a root agent, and every agent is now what that fallback
called a root:

- the harness's turn-failure / plugin-failure notification
  (`Surface::send_to_parent` -> `send_to_operator`), and
- the send allow-list's always-permitted escape hatch, so an agent with a
  restrictive allow-list still has a way to say it is stuck.

What is NOT preserved, deliberately: an agent with no capability no longer
sees any other agent's dirs. `ManageRootAgent`'s own grant is unchanged --
still every agent in the roster, still state RW + config RO, still no
`harness`.

The dashboard's reparenting control (the M0V3 picker) is deleted with its
CSS. The tree rendering that reads `ContainerView.parent` is left for the
frontend owner -- it degrades to a flat list with the field gone.

hive-c0re/src/job_queue/templates.rs

@@ -597,27 +597,6 @@ pub fn meta_update(builder: &JobBuilder, inputs: Vec<String>, approval_id: Optio
     }
 }
 
-/// Topology move(s) as a single-node DAG. `moves` is `(child, new_parent)`
-/// pairs — len 1 for `set-parent`, len N for `set-parent-bulk`, applied
-/// uniformly by the one [`NodeKind::Reparent`] node (which holds the global
-/// meta window for its duration, same precedent as [`NodeKind::WritePermFile`]).
-/// No rebuild subgraph: `topology.json` is read live by every consumer
-/// (dashboard tree, `<parent>`/`<children>` sentinel routing, permission
-/// checks), so a parent move needs no container rebuild to take effect.
-/// No transient pill either — the node is agentless (no lease to hang one
-/// off of) and near-instant. No tail node: the write is the whole effect.
-///
-/// Returns the single node's guid so a caller can wait on it.
-pub fn reparent(
-    builder: &JobBuilder,
-    moves: Vec<(hive_types::Ident, Option<hive_types::Ident>)>,
-) -> hive_jobq::NodeGuid {
-    builder
-        .node(NodeKind::Reparent { moves })
-        .needs(Resource::MetaWindow)
-        .guid()
-}
-
 // The boot is assembled inline in `workers/auto_update.rs::submit_boot_tree`
 // as ONE `Boot` DAG (a sweep `MetaLock` root that grows rebuild subgraphs
 // in-DAG, plus a `Reconcile` root per drifted agent) — no anchor node and no