Runs used GitHub's artifact storage and cache service, which ran out of
the monthly included quota and blocked publishing. Caches and job
handoffs now stay on the self-hosted runner host, the desktop release
hands builds over through its draft release, and Windows waits for a
self-hosted runner instead of a GitHub-hosted one. A test enforces it.
Claude-Session: https://claude.ai/code/session_01R8L4XgqjAemFR2remB5hVY
Co-authored-by: Claude <noreply@anthropic.com>
Every main push since the concurrency change cancelled two of the three
image builds: the build job's concurrency group named only the ref, so
the app, updater and computer legs of one run shared it and cancelled
each other, and the publish job never ran. Main has not published an
edge image since. The build and publish groups now name the matrix leg.
The Playwright report publisher also read the jobs of a run's latest
attempt, so a re-run already in progress made it fail on an empty
conclusion. It now reads the attempt that finished.
Claude-Session: https://claude.ai/code/session_01R8L4XgqjAemFR2remB5hVY
Co-authored-by: Claude <noreply@anthropic.com>
Switch PR/push CI, Playwright, image publish validation, and manual
workflows from GitHub-hosted labels to the repo's online self-hosted
runners (evo Linux, air/mini macOS). release-desktop keeps
windows-2022 only when Windows signing credentials are configured;
there is no self-hosted Windows runner.
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: cynarAI <cynarAI@users.noreply.github.com>
