diff --git a/hive-c0re/src/server.rs b/hive-c0re/src/server.rs
index 2204a5f4..5e88d8a1 100644
--- a/hive-c0re/src/server.rs
+++ b/hive-c0re/src/server.rs
@@ -637,14 +637,14 @@ async fn handle_start(
 /// Restart containers hive-wide (`hivectl restart`) — the DAG-based
 /// sibling of [`handle_stop`]/[`handle_start`], replacing the old
 /// client-side stop-then-start composition (issue tracker "dagify hivectl
-/// commands"). Each targeted agent gets exactly one atomic `Restart`
-/// template DAG in the common (non-graceful) case, so it survives a
-/// dropped `hivectl` connection the same way `handle_restart_all` already
-/// does. `graceful` has no single-DAG template yet, so it falls back to
-/// submitting the graceful-stop DAGs, waiting them out server-side, then
-/// submitting the start DAGs — still one daemon call end to end, unlike
-/// the old CLI-side compose. Infra containers have no lease/DAG and
-/// restart synchronously (stop then start).
+/// commands"). Each targeted agent gets exactly one atomic DAG submitted
+/// up front: the `Restart` template (mechanical stop + reconcile) in the
+/// common case, or `GracefulRestart` (signal → drain → mechanical stop →
+/// reconcile) with `graceful` set — no "submit a DAG, wait for it, submit
+/// another" composition on either path, so a dropped `hivectl` connection
+/// never strands an agent, the same way `handle_restart_all` already
+/// avoids it. Infra containers have no lease/DAG and restart
+/// synchronously (stop then start).
 async fn handle_restart_scoped(
     coord: &Arc<Coordinator>,
     scope: &LifecycleScope,