From 6fc5ba4d0adb671ea851ae1471a5d807c9662b5d Mon Sep 17 00:00:00 2001 From: dan-claude-bot Date: Sun, 19 Jul 2026 13:01:49 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20the=20changelog=20entry=20tells=20the?= =?UTF-8?q?=20round-2=20story=20=E2=80=94=20probe,=20branch,=20cleanup?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The entry ended at round 1's unconditional wedge message; the shipped behavior probes the instance, narrates wedge vs overrun, and best-effort deletes so the retry is clean either way. Co-Authored-By: Claude Fable 5 --- CHANGELOG.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 034b727..40b5426 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -217,9 +217,12 @@ which records not just what changed but what each drill run proved. `timeout -k 5 $BOX_LAUNCH_TIMEOUT` (seconds, default 600 — generous: the coldest measured mint is minutes, never an hour; the same scripting-knob shape as `BOX_CPU`/`BOX_MEMORY`), with stdin pinned per the drill's own - trap list. On the budget firing it says exactly what was measured — the - client wedged with no server-side operation, an immediate retry has been - observed to succeed — and points at `box doctor` for the host. The + trap list. On the budget firing it probes whether the instance was ever + registered and tells the two stories apart — the measured #93 wedge (no + server-side operation; an immediate retry has been observed to succeed) + vs a slow launch that overran the budget with the instance already + created — then best-effort deletes either way, so the retry advice is + clean in both worlds, and points at `box doctor` for the host. The `--from` clone path is untouched: `incus copy` of a local instance is a different operation and has never been observed to wedge this way. - **UFW's gateway carve-out converges with the bridge, and the doctor can