6 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
68ab457 (run)
- Noncanonical docs guard: stale-green — success, but it tested
3771129 and head is 68ab457 -- that pass is evidence about a tree nobody runs any more
- evidence-freshness — newest run concluded failure on
8132e60 (run)
- Clean-machine quickstart lifecycle — newest run concluded failure on
67ebec2 AFTER the workflow was retired (2026-07-27T07:59:08Z), so it failed as currently configured (run)
- canvas-nodom-ladder — newest run concluded failure on
bc4a49c AFTER the workflow was retired (2026-07-27T07:59:08Z), so it failed as currently configured (run)
- Paper: stale-green — success, but it tested
bc4a49c and head is fafdf0e -- that pass is evidence about a tree nobody runs any more
- Validate claims: stale-green — success, but it tested
3011558 and head is fafdf0e -- that pass is evidence about a tree nobody runs any more
- Published version claims — newest run concluded failure on
3f5e7a8 (run)
- Default branch sweep: in-flight — in_progress for 0.0h on
c34cbaf -- not yet evidence either way
- Docs CI: stale-green — success, but it tested
b852bb7 and head is c34cbaf -- that pass is evidence about a tree nobody runs any more
- Published version claims — newest run concluded failure on
7e15927 (run)
- Deploy Worker — newest run concluded failure on
e99cdbe; the workflow file changed afterwards (2026-07-28T02:22:22Z), so re-run it to find out whether the fix took (run)
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-capture
- Notify docs: stale-green — success, but it tested
27ccd26 and head is a9d0877 -- that pass is evidence about a tree nobody runs any more
- OpenAdaptAI/openadapt-desktop
- Build managed FFmpeg runtime: not-push-gated — dispatch or schedule only, so the failure run says nothing about the tree (retired 2026-07-26T04:10:38Z, after that run)
- Notify docs: stale-green — success, but it tested
1685ea8 and head is f677d4c -- 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-07-28T02:22:09Z, 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-07-28T02:22:12Z, after that run)
- OpenAdaptAI/openadapt-viewer
- Release and PyPI Publish: not-push-gated — dispatch or schedule only, so the failure run says nothing about the tree (retired 2026-07-28T02:22:16Z, after that run)
Swept 26 repositories in 128 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/30531445169
6 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)68ab457(run)3771129and head is68ab457-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-evals (
main)8132e60(run)OpenAdaptAI/openadapt-flow (
main)67ebec2AFTER the workflow was retired (2026-07-27T07:59:08Z), so it failed as currently configured (run)bc4a49cAFTER the workflow was retired (2026-07-27T07:59:08Z), so it failed as currently configured (run)bc4a49cand head isfafdf0e-- that pass is evidence about a tree nobody runs any more3011558and head isfafdf0e-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-ops (
main)3f5e7a8(run)c34cbaf-- not yet evidence either wayb852bb7and head isc34cbaf-- that pass is evidence about a tree nobody runs any moreOpenAdaptAI/openadapt-web (
main)7e15927(run)OpenAdaptAI/openadapt-wright (
main)e99cdbe; the workflow file changed afterwards (2026-07-28T02:22:22Z), so re-run it to find out whether the fix took (run)Green, 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.27ccd26and head isa9d0877-- that pass is evidence about a tree nobody runs any more1685ea8and head isf677d4c-- that pass is evidence about a tree nobody runs any moreSwept 26 repositories in 128 API reads. https://github.com/OpenAdaptAI/openadapt-ops/actions/runs/30531445169