docs(web-ui/dashboard): fix stale /kill/ bare paths → /api/kill/ + graceful=true

The graceful-stop description at the ■ ST0P confirm-dialog paragraph
referenced `/kill/<name>?graceful=1` and `/kill/<name>` (bare, no /api/
prefix; lax bool `1` instead of `true`).

The backend has registered these under /api/ since the /api/-prefix
migration, and the frontend was updated to send `graceful=true` (not `1`)
in commit f2f1a0b3 (fix: send graceful=true not =1 for the kill query param).
Align the docs with shipped code.
This commit is contained in:
iris 2026-06-23 21:40:47 +02:00 committed by mara
commit 4634094502

View file

@ -838,9 +838,9 @@ the per-agent `⋮` menu and the bulk selection bar.
**Graceful stop** — the `■ ST0P` confirm dialog (per-agent and
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 the instant hard stop
(`/kill/<name>` with no query). The backend enqueues a
the action POSTs `/api/kill/<name>?graceful=true` (the bulk path
appends the flag per-agent); unticked is the instant hard stop
(`/api/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