Every protected web build archived the build it replaced and never
removed one, at 50 to 200 MB each: the local POC had collected 284 MB
in three backups. A successful build now keeps the build it replaced,
which the receipt names as the rollback target, one earlier build and
the newest failed build; the receipt lists what it removed. Removal is
best effort: a directory it cannot remove waits for the next build.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Detect actual service and Runner readiness, restore LAN access after network changes, protect production web builds with rollback, honor cancellation during executor startup, and show truthful cached-data and credential states.