5 of 26 PUBLIC repositories we own do not have a genuinely green default branch.
This run saw no private repository. A repository-scoped GITHUB_TOKEN does not list them at all, so they are not skipped-and-reported here -- this job never learns they exist. Set an OA_SWEEP_TOKEN secret holding a token with actions:read on the private repositories to cover them.
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.
- Platform manifest and source boundary — newest run concluded failure on
da7b0f1 (run)
- Noncanonical docs guard: stale-green — success, but it tested
60fe15a and head is da7b0f1 -- that pass is evidence about a tree nobody runs any more
- Production qualification — newest run concluded cancelled on
d1f6615 AFTER the workflow was retired (2026-08-21T20:07:55Z), so it failed as currently configured (run)
- Notify docs: stale-green — success, but it tested
6109678 and head is d1f6615 -- that pass is evidence about a tree nobody runs any more
- Dependency Audit — newest run concluded failure on
f0f5d14 (run)
- Build managed FFmpeg runtime: not-push-gated — dispatch or schedule only, 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
6f43a97 and head is f0f5d14 -- that pass is evidence about a tree nobody runs any more
- evidence-freshness — newest run concluded failure on
aca85d4 (run)
- Production DB backup freshness — newest run concluded failure on
077f882 AFTER the workflow was retired (2026-08-20T15:41:44Z), so it failed as currently configured (run)
- Production DB logical backup — newest run concluded failure on
ea7e85a AFTER the workflow was retired (2026-08-20T15:41:44Z), so it failed as currently configured (run)
- Published version claims — newest run concluded failure on
077f882 (run)
- Default branch sweep: in-flight — in_progress for 0.0h on
077f882 -- not yet evidence either way
- Production lifecycle policy: stale-green — success, but it tested
ea7e85a and head is 077f882 -- that pass is evidence about a tree nobody runs any more
- Sync Documentation: stale-green — success, but it tested
0fca520 and head is 077f882 -- that pass is evidence about a tree nobody runs any more
- Workspace staleness sweep: stale-green — success, but it tested
ea7e85a and head is 077f882 -- 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-flow
- Paper: stale-green — success, but it tested
94e7036 and head is 80dc49b -- that pass is evidence about a tree nobody runs any more
- Validate claims: stale-green — success, but it tested
94e7036 and head is 80dc49b -- that pass is evidence about a tree nobody runs any more
- OpenAdaptAI/openadapt-grounding
- Release and PyPI Publish: not-push-gated — dispatch or schedule only, 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 — dispatch or schedule only, 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
743ffa9 and head is 54c9c0d -- that pass is evidence about a tree nobody runs any more
- Release and PyPI Publish: not-push-gated — dispatch or schedule only, so the failure run says nothing about the tree (retired 2026-08-20T11:10:42Z, after that run)
- OpenAdaptAI/openadapt-web
- Published version claims: stale-green — success, but it tested
cf45425 and head is 901f7d0 -- that pass is evidence about a tree nobody runs any more
Swept 26 repositories in 140 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/32945127051
5 of 26 PUBLIC 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 (
main)da7b0f1(run)60fe15aand head isda7b0f1-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-capture (
main)d1f6615AFTER the workflow was retired (2026-08-21T20:07:55Z), so it failed as currently configured (run)6109678and head isd1f6615-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-desktop (
main)f0f5d14(run)6f43a97and head isf0f5d14-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-evals (
main)aca85d4(run)OpenAdaptAI/openadapt-ops (
main)077f882AFTER the workflow was retired (2026-08-20T15:41:44Z), so it failed as currently configured (run)ea7e85aAFTER the workflow was retired (2026-08-20T15:41:44Z), so it failed as currently configured (run)077f882(run)077f882-- not yet evidence either wayea7e85aand head is077f882-- that pass is evidence about a tree nobody runs any more0fca520and head is077f882-- that pass is evidence about a tree nobody runs any moreea7e85aand head is077f882-- 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.94e7036and head is80dc49b-- that pass is evidence about a tree nobody runs any more94e7036and head is80dc49b-- that pass is evidence about a tree nobody runs any more743ffa9and head is54c9c0d-- that pass is evidence about a tree nobody runs any morecf45425and head is901f7d0-- that pass is evidence about a tree nobody runs any moreSwept 26 repositories in 140 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/32945127051