dan-claude-bot 4da487e388 fix: the timeout path probes the instance, tells the two stories apart, and cleans up ... Round-1 consensus on #94: timeout only proves the CLIENT overran the budget. incus launch is create-then-start, so a slow-but-progressing launch may already have registered the instance — the old message claimed 'never created' unconditionally and the advised retry would collide with 'Instance already exists'. The 124/137 path now probes 'incus info', narrates the branch it found (true #93 wedge vs slow-launch overrun), best-effort 'incus delete --force's either way so the retry is clean in both worlds, hedges 137 as possibly an outside kill, and BOX_LAUNCH_TIMEOUT is documented in 'box help new' beside the other knobs. Both branches driven live against a shim incus; four new grep-proof checks pin the probe, the cleanup, the overrun story, and the help text. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-19 12:52:41 +00:00
..
box	fix: the timeout path probes the instance, tells the two stories apart, and cleans up	2026-07-19 12:52:41 +00:00