Default branch sweep - a repository we own is not green

[github-actions]

7 of 41 repositories we own do not have a genuinely green default branch.

cancelled, timed_out and startup_failure are not green: such a run proves nothing about the tree. The usual cause is concurrency cancel-in-progress when several merges land at once, so re-run the cancelled run rather than assuming the older success still stands.

This issue is rewritten in place once a day and closed when everything is green. Editing a body does not notify, so a long-lived gap does not become a daily ping.

OpenAdaptAI/OpenAdapt (main)

• Launcher quickstart lifecycle — newest run concluded cancelled on 8abd5cc (run)
• Platform manifest and source boundary — newest run concluded failure on 2e9fddd (run)
• Noncanonical docs guard: stale-green — success, but it tested 2b9707a and head is 2e9fddd -- that pass is evidence about a tree nobody runs any more
• Release and PyPI Publish: stale-green — success, but it tested 2aa387f and head is 2e9fddd -- that pass is evidence about a tree nobody runs any more

OpenAdaptAI/openadapt-capture (main)

• Release and PyPI Publish — newest run concluded failure on 2a3ef96 (run)

OpenAdaptAI/openadapt-cloud (main)

• CI — newest run concluded failure on 60df757 (run)
• Deploy — newest run concluded failure on 10434cc AFTER the workflow was retired (2026-08-29T15:13:34Z), so it failed as currently configured (run)
• Dependency Audit: stale-green — success, but it tested 10434cc and head is 60df757 -- that pass is evidence about a tree nobody runs any more
• Execute live synthetic acceptance: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-19T22:44:59Z, after that run)
• Requalify managed synthetic workflow: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-29T19:45:20Z, after that run)
• Secret Scan: stale-green — success, but it tested 9c14c0f and head is 60df757 -- that pass is evidence about a tree nobody runs any more

OpenAdaptAI/openadapt-desktop (main)

• Production channel admission — newest run concluded failure on bb6580a (run)
• Build managed FFmpeg runtime: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-19T20:13:07Z, after that run)

OpenAdaptAI/openadapt-internal (main)

• Source policy sync — newest run concluded failure on 124e955 (run)
• Qualification evidence store: stale-green — success, but it tested e75cf05 and head is 124e955 -- that pass is evidence about a tree nobody runs any more

OpenAdaptAI/openadapt-ops (main)

• Production DB backup freshness — newest run concluded failure on c827d80 (run)
• Production DB logical backup — newest run concluded failure on c827d80 (run)
• Action pin sweep: stale-green — success, but it tested 03bbe2a and head is c827d80 -- that pass is evidence about a tree nobody runs any more
• Default branch sweep: in-flight — in_progress for 0.0h on c827d80 -- not yet evidence either way
• Docs CI: stale-green — success, but it tested 771c3bf and head is c827d80 -- that pass is evidence about a tree nobody runs any more

OpenAdaptAI/openadapt-web (main)

• CI — newest run concluded failure on e64dedd (run)
• CodeQL — newest run concluded failure on e64dedd (run)
• GitHub link anchors — newest run concluded failure on 30b93cf (run)
• Production lifecycle projection: stale-green — success, but it tested 30b93cf and head is e64dedd -- that pass is evidence about a tree nobody runs any more
• Published claims: stale-green — success, but it tested 30b93cf and head is e64dedd -- that pass is evidence about a tree nobody runs any more

Green, with notes — none of these is a failure

retired and not-push-gated entries are frozen history: GitHub keeps a workflow's last run for ever, so a workflow that stopped running would otherwise be reported red permanently. stale-green passed on an older tree. in-flight has been running for less than 6h.

• OpenAdaptAI/openadapt-evals
  • Release and publish: stale-green — success, but it tested 33347bd and head is fe0524e -- that pass is evidence about a tree nobody runs any more
• OpenAdaptAI/openadapt-flow
  • Paper: stale-green — success, but it tested f38761e and head is 98588e8 -- that pass is evidence about a tree nobody runs any more
  • Release and PyPI Publish: stale-green — success, but it tested fbfa76b and head is 98588e8 -- that pass is evidence about a tree nobody runs any more
  • Validate claims: stale-green — success, but it tested 94e7036 and head is 98588e8 -- that pass is evidence about a tree nobody runs any more
• OpenAdaptAI/openadapt-grounding
  • Release and PyPI Publish: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-20T11:10:24Z, after that run)
• OpenAdaptAI/openadapt-herald
  • weekly-digest: retired — workflow disabled_inactivity; the failure run is frozen history
• OpenAdaptAI/openadapt-retrieval
  • Release and PyPI Publish: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-20T11:10:33Z, after that run)
• OpenAdaptAI/openadapt-viewer
  • Generate Screenshots: stale-green — success, but it tested 01e87e5 and head is 6cfad96 -- that pass is evidence about a tree nobody runs any more
  • Release and PyPI Publish: not-push-gated — no change or schedule trigger, so the failure run says nothing about the tree (retired 2026-08-20T11:10:42Z, after that run)
• OpenAdaptAI/openadapt-wright
  • Deploy Worker: stale-green — success, but it tested 54311b1 and head is 21ec989 -- that pass is evidence about a tree nobody runs any more

Swept 41 repositories in 219 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/33406103346

[github-actions]

Every default branch we own is genuinely green as of https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/31302373936. Closing automatically.