CI Audit — 2026-05-01
Automated CI maintenance scan. gh CLI is unavailable in this environment; analysis was performed via GitHub MCP tools (PR check runs + branch listing).
What is currently failing
PR #32 — fix/ci-workflow-trigger-broadening — FAILING ❌
Last run: 2026-04-12
| Job |
Result |
test (20) |
failure |
test (22) |
cancelled |
test (Test Stats Plugin) |
failure × 2 |
| Validate marketplace.json format |
success |
| Validate shared dependencies |
success |
Root cause of these failures: PR #32 only removed the hardcoded branches allowlist from the workflow YAML. It was stacked on fix/ci-type-errors-and-stale-test-date which still had broken TS imports and stale test dates. CI ran (the trigger fix worked), but the underlying tests still failed.
These failures are fully superseded — see below.
What is green and ready to merge
PR #33 — fix/ci-consolidated — ALL GREEN ✅
Last run: 2026-04-12 (7/7 checks pass)
| Job |
Result |
| GitGuardian Security Checks |
success |
| marketplace-sync |
success |
| test |
success |
| Validate shared dependencies |
success |
| test (22) |
success |
| test (20) |
success |
| Validate marketplace.json format |
success |
PR #33 includes all fixes:
- Unused TS imports removed —
removeGitignoreEntries, vi, existsSync flagged by noUnusedLocals
- Stale hardcoded dates replaced —
"2026-03-26" in db.test.ts and integration.test.ts replaced with runtime TODAY/YESTERDAY/TWO_DAYS_AGO constants
- browser-use version synced —
marketplace.json bumped from 1.1.1 → 1.1.2 to match plugin.json
- Workflow trigger broadening —
branches allowlist removed from test-plugins.yml and test-stats.yml so all feature/fix branches get CI coverage
PR #24 and PR #34 are also green and contain overlapping fixes; PR #33 is the most complete single-PR resolution.
Situation
These fix PRs have been open since April 11–12, 2026 (~3 weeks) with all CI green. None have been merged.
The source-code development branch is fix/ci-type-errors-and-stale-test-date (not main, which is a dist-only orphan at 4070f70).
Recommended action
Merge PR #33 into fix/ci-type-errors-and-stale-test-date. This will:
PRs #22, #23, #28, #31, #32, #34 can be closed as superseded after #33 merges.
CI Audit — 2026-05-01
Automated CI maintenance scan.
ghCLI is unavailable in this environment; analysis was performed via GitHub MCP tools (PR check runs + branch listing).What is currently failing
PR #32 —
fix/ci-workflow-trigger-broadening— FAILING ❌Last run: 2026-04-12
test (20)test (22)test(Test Stats Plugin)Root cause of these failures: PR #32 only removed the hardcoded
branchesallowlist from the workflow YAML. It was stacked onfix/ci-type-errors-and-stale-test-datewhich still had broken TS imports and stale test dates. CI ran (the trigger fix worked), but the underlying tests still failed.These failures are fully superseded — see below.
What is green and ready to merge
PR #33 —
fix/ci-consolidated— ALL GREEN ✅Last run: 2026-04-12 (7/7 checks pass)
PR #33 includes all fixes:
removeGitignoreEntries,vi,existsSyncflagged bynoUnusedLocals"2026-03-26"indb.test.tsandintegration.test.tsreplaced with runtimeTODAY/YESTERDAY/TWO_DAYS_AGOconstantsmarketplace.jsonbumped from1.1.1→1.1.2to matchplugin.jsonbranchesallowlist removed fromtest-plugins.ymlandtest-stats.ymlso all feature/fix branches get CI coveragePR #24 and PR #34 are also green and contain overlapping fixes; PR #33 is the most complete single-PR resolution.
Situation
These fix PRs have been open since April 11–12, 2026 (~3 weeks) with all CI green. None have been merged.
The source-code development branch is
fix/ci-type-errors-and-stale-test-date(notmain, which is a dist-only orphan at4070f70).Recommended action
Merge PR #33 into
fix/ci-type-errors-and-stale-test-date. This will:PRs #22, #23, #28, #31, #32, #34 can be closed as superseded after #33 merges.