6 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.
- Release and PyPI Publish — newest run concluded failure on
2a3ef96 (run)
- Notify docs: stale-green — success, but it tested
a6fb0cc and head is fb46907 -- that pass is evidence about a tree nobody runs any more
- Native Installer Release — newest run concluded cancelled on
7c59750 AFTER the workflow was retired (2026-08-29T14:52:58Z), so it failed as currently configured (run)
- Production channel admission — newest run concluded failure on
5845c12 (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)
- Notify docs: stale-green — success, but it tested
095082c and head is 5845c12 -- that pass is evidence about a tree nobody runs any more
- Release and PyPI Publish — newest run concluded failure on
d84e235 (run)
- Paper: stale-green — success, but it tested
dad7b04 and head is be7048f -- that pass is evidence about a tree nobody runs any more
- Validate claims: stale-green — success, but it tested
98588e8 and head is be7048f -- that pass is evidence about a tree nobody runs any more
- Source policy sync — newest run concluded failure on
0ec1734 (run)
- Qualification evidence store: stale-green — success, but it tested
e75cf05 and head is 0ec1734 -- that pass is evidence about a tree nobody runs any more
- Production DB backup freshness — newest run concluded failure on
b513a9c (run)
- Production DB logical backup — newest run concluded failure on
63351ee (run)
- Action pin sweep: stale-green — success, but it tested
c827d80 and head is b513a9c -- that pass is evidence about a tree nobody runs any more
- Default branch sweep: in-flight — in_progress for 0.0h on
b513a9c -- not yet evidence either way
- Workspace staleness sweep: stale-green — success, but it tested
63351ee and head is b513a9c -- that pass is evidence about a tree nobody runs any more
- CodeQL — newest run concluded failure on
e100109 (run)
- Published claims — newest run concluded failure on
4dd82a0 (run)
- GitHub link anchors: stale-green — success, but it tested
4dd82a0 and head is e100109 -- that pass is evidence about a tree nobody runs any more
- Production lifecycle projection: stale-green — success, but it tested
4dd82a0 and head is e100109 -- 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
- Release and PyPI Publish: stale-green — success, but it tested
2aa387f and head is e90102d -- that pass is evidence about a tree nobody runs any more
- OpenAdaptAI/openadapt-cloud
- Dependency Audit: stale-green — success, but it tested
60df757 and head is 74c6e65 -- 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)
- OpenAdaptAI/openadapt-evals
- Release and publish: stale-green — success, but it tested
a8ee294 and head is 5d0a01a -- 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 216 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/33753105076
6 of 41 repositories we own do not have a genuinely green default branch.
cancelled,timed_outandstartup_failureare not green: such a run proves nothing about the tree. The usual cause is concurrencycancel-in-progresswhen 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-capture (
main)2a3ef96(run)a6fb0ccand head isfb46907-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-desktop (
main)7c59750AFTER the workflow was retired (2026-08-29T14:52:58Z), so it failed as currently configured (run)5845c12(run)095082cand head is5845c12-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-flow (
main)d84e235(run)dad7b04and head isbe7048f-- that pass is evidence about a tree nobody runs any more98588e8and head isbe7048f-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-internal (
main)0ec1734(run)e75cf05and head is0ec1734-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-ops (
main)b513a9c(run)63351ee(run)c827d80and head isb513a9c-- that pass is evidence about a tree nobody runs any moreb513a9c-- not yet evidence either way63351eeand head isb513a9c-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-web (
main)e100109(run)4dd82a0(run)4dd82a0and head ise100109-- that pass is evidence about a tree nobody runs any more4dd82a0and head ise100109-- that pass is evidence about a tree nobody runs any moreGreen, with notes — none of these is a failure
retiredandnot-push-gatedentries 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-greenpassed on an older tree.in-flighthas been running for less than 6h.2aa387fand head ise90102d-- that pass is evidence about a tree nobody runs any more60df757and head is74c6e65-- that pass is evidence about a tree nobody runs any morea8ee294and head is5d0a01a-- that pass is evidence about a tree nobody runs any more01e87e5and head is6cfad96-- that pass is evidence about a tree nobody runs any more54311b1and head is21ec989-- that pass is evidence about a tree nobody runs any moreSwept 41 repositories in 216 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/33753105076