From 4634094502e80e82a21a17655759081be69be9d1 Mon Sep 17 00:00:00 2001 From: iris Date: Tue, 23 Jun 2026 21:40:47 +0200 Subject: [PATCH] =?UTF-8?q?docs(web-ui/dashboard):=20fix=20stale=20/kill/?= =?UTF-8?q?=20bare=20paths=20=E2=86=92=20/api/kill/=20+=20graceful=3Dtrue?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The graceful-stop description at the ■ ST0P confirm-dialog paragraph referenced `/kill/?graceful=1` and `/kill/` (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. --- docs/web-ui/dashboard.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/web-ui/dashboard.md b/docs/web-ui/dashboard.md index 78fb338d..3271c08d 100644 --- a/docs/web-ui/dashboard.md +++ b/docs/web-ui/dashboard.md @@ -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/?graceful=1` (the bulk path appends -the flag per-agent); unticked is the instant hard stop -(`/kill/` with no query). The backend enqueues a +the action POSTs `/api/kill/?graceful=true` (the bulk path +appends the flag per-agent); unticked is the instant hard stop +(`/api/kill/` 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