job_queue: add NodeKind::Reparent (topology moves as a queue node, #2719)

hive-c0re/src/job_queue/exec.rs

@@ -89,6 +89,7 @@ pub(super) async fn run_node(coord: &Arc<Coordinator>, claim: &Claim) -> Result<
         NodeKind::Drain { .. } => run_drain(coord, claim).await,
         NodeKind::WriteDropin { .. } => run_write_dropin(coord, claim).await,
         NodeKind::WritePermFile { .. } => run_write_perm_file(coord, claim).await,
+        NodeKind::Reparent { .. } => run_reparent(coord, claim).await,
         NodeKind::DeployWindow { .. } => run_deploy_window(claim),
         NodeKind::MergeVerify { .. } => run_merge_verify(coord, claim).await,
         NodeKind::DeployApply { .. } => run_deploy_apply(coord, claim).await,
@@ -530,6 +531,33 @@ async fn run_write_perm_file(coord: &Arc<Coordinator>, claim: &Claim) -> Result<
     Ok(NodeOutput::default())
 }
 
+/// Apply the node's `(child, new_parent)` moves as one `META_LOCK`-fused
+/// commit (`Coordinator::reparent_bulk_with_notify`, which already handles
+/// both the single- and bulk-move case, sends the per-agent move
+/// notifications, and rescans + diff-emits the container tree). Runs under
+/// the deploy window (`NodeKind::needs_meta_window`), same reasoning as
+/// `run_write_perm_file`: a topology commit landing inside another node's
+/// staged deploy window would sweep the staged lock into its commit.
+async fn run_reparent(coord: &Arc<Coordinator>, claim: &Claim) -> Result<NodeOutput> {
+    let NodeKind::Reparent { moves } = &claim.kind else {
+        anyhow::bail!("run_reparent on a non-Reparent node");
+    };
+    let refs: Vec<(&str, Option<&str>)> = moves
+        .iter()
+        .map(|(child, parent)| {
+            (
+                child.as_str(),
+                parent.as_ref().map(hive_types::Ident::as_str),
+            )
+        })
+        .collect();
+    coord
+        .reparent_bulk_with_notify(&refs)
+        .await
+        .map_err(|e| anyhow::anyhow!(e))?;
+    Ok(NodeOutput::default())
+}
+
 /// The approval id every deploy phase re-reads its approval row by. Fails the
 /// node when the DAG carries none, which would mean a `MergeConfigPr` DAG was
 /// built without going through `templates::approval_deploy`.