didericis-claude
ed9fc76f97
prd-number-check / require-numbered-prds (pull_request) Successful in 5s
test / unit (pull_request) Successful in 50s
tracker-policy-pr / check-pr (pull_request) Successful in 6s
test / image-input-builds (pull_request) Successful in 59s
test / integration-docker (pull_request) Successful in 1m6s
test / coverage (pull_request) Successful in 42s
Update Quality Badges / update-badges (push) Successful in 49s
lint / lint (push) Successful in 1m2s
test / coverage (push) Successful in 24s
test / integration-docker (push) Successful in 1m3s
test / unit (push) Successful in 48s
test / image-input-builds (push) Successful in 2m44s
Address review: the self-heal classified every non-absence `network inspect` failure as a poisoned network and force-removed the shared gateway. But inspect also fails on transient daemon/API errors, permission failures, timeouts, or a bad context — destroying a healthy gateway on that guess would tear the network out from under every live bottle. Now the destructive path runs only for the known poison signature (docker's `ParseAddr` error from the malformed `::1/64` IPv6 gateway). The absent case (`No such network`) still just creates; any other inspect failure raises a clear GatewayError without mutating shared state. Adds a regression test asserting a generic inspect error issues neither `docker rm --force` nor `docker network rm` and surfaces the error. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>