bvandeusenandClaude Opus 5.5
47fb3f2193
CI and images / lint (push) Successful in 2s
CI and images / extension-version (push) Successful in 2s
CI and images / extension-test (push) Successful in 20s
CI and images / frontend-build (push) Successful in 24s
CI and images / backend-lint-and-test (push) Successful in 35s
CI and images / integration (push) Successful in 2m19s
CI and images / build-agent (push) Successful in 6s
CI and images / sign-extension (push) Successful in 8s
CI and images / build-web (push) Successful in 5s
CI and images / smoke-web (push) Successful in 35s
CI and images / promote (push) Successful in 1s
CI and images / refresh-dev (push) Skipped
CI and images / unattended-failure (push) Skipped
The Sunday refresh failed five weeks running (2026-10-04 to 11-01) and nothing said so; it was found by reading the run list (#6864). It also only ever refreshed :latest: an artifact whose dev source is quiet, the agent most weeks, kept its last build's base layers on :dev, because reuse skips it on every push. - refresh-dev: after promote, a refresh dispatches a forced dev run. That run is an ordinary dev build (lanes, smoke, promote), so :dev gets dev's own source with FC_CHANNEL=dev rather than main's bytes relabelled. - A forced build now pulls fresh bases, as the refresh does; otherwise forcing rebuilds the same image. - unattended-failure: any failed run that is not a push or PR opens an issue (or comments on the open one) naming the run and the failed jobs. - RELEASE_TOKEN's scope list names write:repository, which the dispatch needs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>