ci: accumulated fix PRs need triage — 8 open, 3 passing, 5 superseded

[erudenko]

CI Maintenance Audit — 2026-05-01

This issue was auto-generated by a CI maintenance agent that scanned for recently failed GitHub Actions runs. gh run list is not available in this environment, so the analysis is based on PR-level check-run data via the GitHub API.

---

Historical Failures Found

The following run IDs appear in open PR descriptions as the root cause for all current fix branches:

Run ID	Workflow	Failure
24065489776	Test Plugins	tsc --noEmit — 3 unused TS imports (TS6133)
24063290384	Test Plugins	Shared-deps out of sync + type check
24298790072	Test Plugins	Type check (inherited from broken base)
24298790076	Test Stats Plugin	Stale hardcoded date in time-windowed queries
24298782547	Test Stats Plugin	Stale hardcoded date in time-windowed queries
24298781727	Test Plugins	Type check (inherited)
24276607217	Test Plugins	browser-use version mismatch: plugin.json 1.1.2 vs marketplace.json 1.1.1
24276583408	Test Stats Plugin	Stale date
24276582786	Test Plugins	Type check
24040412326	Test Stats Plugin	Stale date

Root causes (all now fixed in green branches):

1. Three unused TypeScript imports left behind after refactors (TS6133 under noUnusedLocals)
2. Hardcoded date "2026-03-26" in plugins/stats/tests/ fell outside the rolling 7/14-day query windows
3. browser-use bumped to 1.1.2 in plugin.json but marketplace.json left at 1.1.1
4. Workflow triggers had a hardcoded branches allowlist that made CI invisible on every branch except main and one specific fix branch

---

Current State of Open Fix PRs

PR	Branch	CI	Status
#22	fix/ci-typescript-and-stats-dates	GitGuardian only	⚠️ Superseded — branch filter bug prevented test CI from ever running
#23	fix/ci-typescript-and-stats-dates-resolved	GitGuardian only	⚠️ Superseded — same as above
#24	fix/ci-24065489776-ts-and-dates	✅ 7/7 passing	Comprehensive fix: TS imports + stale dates + browser-use + trigger broadening
#28	fix/ci-24276607217-browser-use-version	GitGuardian only	⚠️ Superseded — branch filter bug; superseded by #24
#31	fix/ci-main-browser-use-version	GitGuardian only	⚠️ Targets dist-only main — test workflows don't exist there
#32	fix/ci-workflow-trigger-broadening	❌ test(20) fail, test(stats) fail×2	Stacked on broken base; superseded by #33
#33	fix/ci-consolidated	✅ 7/7 passing	Superset of #24: all code fixes + workflow trigger broadening
#34	fix/ci-all-fixes-final	✅ 13/13 passing	Alternative comprehensive fix

---

Recommended Actions

Close (superseded)

• fix(ci): remove unused TS imports + fix stale stats test dates #22 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24
• fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24
• fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 — superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24
• fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31 — wrong base branch (dist-only main); can't run test CI
• fix(ci): remove hardcoded branch filters from workflow triggers #32 — superseded by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33

Merge path

PRs #24, #33, and #34 are all CI-green and contain the same core fixes. They are stacked on fix/ci-type-errors-and-stale-test-date, which is the source-code branch that test CI runs against (since main is a dist-only orphan).

The simplest resolution: merge PR #33 (fix/ci-consolidated) into fix/ci-type-errors-and-stale-test-date. It is the most comprehensive — it includes all four fixes and the workflow trigger broadening — and was last updated today (2026-05-01).

After #33 is merged, PRs #24 and #34 can be closed as superseded.

---

Why this wasn't auto-fixed

The merge order requires owner judgement: the base branch (fix/ci-type-errors-and-stale-test-date) is itself not main, the PRs overlap heavily, and force-merging the wrong one could create conflicts in the others. This issue documents the state so the repository owner can take the final merge action.