Use Depot GitHub Actions runners

[petergstfsn]

What changed

• Route every GitHub-hosted Actions job in this repository to the equivalent Depot runner label.
• Preserve the existing operating-system version and CPU architecture choices.
• Leave workflow behavior, steps, permissions, triggers, and deployment logic unchanged.

Verification

• Ran Actionlint v1.7.12 with the supported Depot labels declared as custom runner labels.
• Ran a migration-focused Actionlint pass across the full workflow set; inherited upstream diagnostics were compared with the base revision and are unchanged.
• Ran git diff --check.
• Confirmed the target branch is an ancestor of the proposed head after refreshing origin.

Review flags

• CI configuration: after merge, jobs require the Depot Managed Runners GitHub app and the organization default runner group to allow this repository. Public repositories also require the runner group's public-repository setting.
• Assumption: the esaueng organization connection shown in Depot onboarding is active for this repository.
• No dependencies, application code, public APIs, schemas, entity IDs, file formats, or production deployments are changed.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	opentos	cdc2678	Commit Preview URL Branch Preview URL	Jul 28 2026, 12:25 AM

[petergstfsn]

Closing after repository-wide review: the Depot-runner jobs have remained queued for more than an hour, so this repository does not currently have verified runner availability. Merging would risk disabling CI and release workflows. Recreate after Depot access is confirmed and the full exact-head check suite completes.