ci: maintenance audit — 3 active failures on PR #32, fix is ready in PR #33 (all green)

[erudenko]

CI Maintenance Audit — 2026-04-13

This issue was created by the CI/CD maintenance agent after auditing all recent workflow runs and open fix PRs. The gh CLI was unavailable so analysis was performed via GitHub MCP tools.

---

Active CI Failures

PR #32 (fix/ci-workflow-trigger-broadening) — 3 failing runs

Run ID	Workflow	Job	Conclusion
24298790072	Test Plugins	test (20)	failure
24298790072	Test Plugins	test (22)	cancelled
24298790076	Test Stats Plugin	test	failure
24298782547	Test Stats Plugin	test	failure

Root cause: PR #32 is stacked directly on fix/ci-type-errors-and-stale-test-date, which still carries 3 unused TypeScript imports (removeGitignoreEntries, vi, existsSync) and stale hardcoded dates in plugins/stats/tests/integration.test.ts. PR #32 only changed the workflow YAML triggers — it never fixed those code issues.

---

Fix Is Already Ready — No New Branch Needed

PR #33 (fix/ci-consolidated) is fully green (7/7 checks pass) and contains all required fixes:

Check	Result
GitGuardian Security Checks	✅ success
Validate marketplace.json format	✅ success
Validate shared dependencies	✅ success
test (20)	✅ success
test (22)	✅ success
test (stats)	✅ success
marketplace-sync	✅ success

PR #33 includes everything in PR #32 (workflow trigger broadening) plus all the code fixes (3 unused TS imports removed, rolling dates in both db.test.ts and integration.test.ts, browser-use version 1.1.1 → 1.1.2).

PR #34 (fix/ci-all-fixes-final) is also fully green (13/13 checks pass).

PR #24 (fix/ci-24065489776-ts-and-dates) is also fully green (7/7 checks pass).

---

Summary of All Open Fix PRs

PR	Branch	CI	Status
#34	fix/ci-all-fixes-final	✅ 13/13 green	Open — superseded by #33 (or merge separately)
#33	fix/ci-consolidated	✅ 7/7 green	Open — recommended merge
#32	fix/ci-workflow-trigger-broadening	❌ 3 failures	Open — superseded by #33
#31	fix/ci-main-browser-use-version	⚪ GitGuardian only	Open — targets main (dist-only orphan, no test workflows) — fix included in #33
#28	fix/ci-24276607217-browser-use-version	⚪ GitGuardian only	Open — superseded by #24/#33
#24	fix/ci-24065489776-ts-and-dates	✅ 7/7 green	Open — included in #33
#23	fix/ci-typescript-and-stats-dates-resolved	⚪ GitGuardian only	Open — superseded by #33
#22	fix/ci-typescript-and-stats-dates	⚪ GitGuardian only	Open — superseded by #33

---

Recommended Actions

1. Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (fix/ci-consolidated) into fix/ci-type-errors-and-stale-test-date. This resolves all active failures in a single, well-documented, fully-green PR.
2. Close PR fix(ci): remove hardcoded branch filters from workflow triggers #32 as superseded by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (same trigger fix, plus all code fixes).
3. Close PRs fix(ci): remove unused TS imports + fix stale stats test dates #22, fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 as superseded by fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24/fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33.
4. Close PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31 — it targets the main dist-only orphan branch where test workflows don't exist; the underlying fix (browser-use version) is already included in fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33.
5. After fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 merges, rebase or close PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 and fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — they will have conflicts or become empty diffs.

---

Why the failures are not transient

The failures on PR #32 are deterministic code-level failures (tsc --noEmit under noUnusedLocals: true), not network timeouts or flaky tests. Re-running them would produce the same result. The only fix is merging the code corrections already present in PR #33.