docs(dashboard): graceful stop is live — backend enqueues GracefulStop transient

#1785 landed the real backend: POST /kill/<name>?graceful=1 enqueues a
GracefulStop rebuild-queue transient (one stop-checkpoint turn to flush
state, 3-min timeout falls back to hard stop). Update the dashboard doc note
which still said the backend treated graceful the same as a hard stop. Also
note hivectl --graceful remains a no-op pending a separate gating change.
This commit is contained in:
iris 2026-06-19 11:55:42 +02:00 committed by mara
commit 2dda2f3c74

View file

@ -794,11 +794,15 @@ the per-agent `⋮` menu and the bulk selection bar.
bulk) carries a `stop gracefully — let the agent finish its turn
and flush state before the container stops` checkbox. When ticked,
the action POSTs `/kill/<name>?graceful=1` (the bulk path appends
the flag per-agent); unticked is today's instant hard stop
(`/kill/<name>` with no query). NOTE: the per-agent quiesce is
still being implemented (see the graceful-agent-stop tracker) — the
flag is accepted now so the wire shape is stable, but the backend
currently treats a graceful request the same as a hard stop.
the flag per-agent); unticked is the instant hard stop
(`/kill/<name>` with no query). The backend enqueues a
`GracefulStop` rebuild-queue transient: the harness runs one
stop-checkpoint turn (so the agent can flush `/state`) and then
exits, with a 3-minute timeout that falls back to a hard stop. The
quiescing progress surfaces through the same rebuild-queue
transient + build log the card already reads for a rebuild. (Note:
the `hivectl --graceful` CLI flag is still a no-op pending a
separate gating change — only the dashboard / HTTP path is live.)
### Topology tree