ci: 3 failing runs on PR #32 — superseded by PR #33, recommend merging to unblock CI

[erudenko]

CI Failure Analysis — auto-generated by CI/CD maintenance agent

Failing runs identified

All three failing runs are on the head commit of PR #32 (fix/ci-workflow-trigger-broadening, sha 6f38db63):

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

Root cause

PR #32 removes the hardcoded branches allowlist from both test-plugins.yml and test-stats.yml — this was the right structural fix, but it was applied only to the workflow YAML without including the underlying code fixes. As a result, once CI could actually run on that branch (thanks to its own trigger fix), the pre-existing code failures were immediately exposed:

1. Stale hardcoded test dates — plugins/stats/tests/db.test.ts / integration.test.ts used "2026-03-26" which is outside the 7/14-day rolling query windows for getSessionSummary, getTopTools, getDurationTrend.
2. Unused TypeScript imports (TS6133) — removeGitignoreEntries, vi, existsSync left behind after refactors cause tsc --noEmit to fail under noUnusedLocals.
3. browser-use version drift — plugins/browser-use/plugin.json at 1.1.2 but .claude-plugin/marketplace.json still at 1.1.1.

Fix already exists — PR #33

PR #33 (fix/ci-consolidated, link) supersedes PR #32 entirely. It carries all three code fixes AND the workflow trigger broadening in a single branch. All 7 CI checks pass:

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

No new fix branch is needed. The recommended path forward is to merge PR #33.

Full open-PR landscape

PR	Branch	Base	CI	Recommendation
#22	fix/ci-typescript-and-stats-dates	fix/ci-type-errors-and-stale-test-date	Only GitGuardian (branch filter blocked CI)	Close — superseded by #24
#23	fix/ci-typescript-and-stats-dates-resolved	same	Only GitGuardian	Close — superseded by #24
#24	fix/ci-24065489776-ts-and-dates	same	✅ All 7 green	Merge first if desired (code-only fixes)
#28	fix/ci-24276607217-browser-use-version	fix/ci-24065489776-ts-and-dates	Only GitGuardian	Close — included in #24
#31	fix/ci-main-browser-use-version	main (dist-only)	Only GitGuardian	Close — no test CI on dist main; fix lives in #24/#33
#32	fix/ci-workflow-trigger-broadening	fix/ci-type-errors-and-stale-test-date	❌ 3 failures	Close — superseded by #33
#33	fix/ci-consolidated	fix/ci-type-errors-and-stale-test-date	✅ All 7 green	Merge — comprehensive fix
#34	fix/ci-all-fixes-final	fix/ci-type-errors-and-stale-test-date	✅ All 13 green	Merge or close (overlaps with #33)

Recommended action sequence

1. Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 — this resolves all three failing run root causes and broadens CI triggers so future branches are not invisible.
2. 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, fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31, fix(ci): remove hardcoded branch filters from workflow triggers #32 as superseded.
3. Close PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 if fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 lands first (its diff will be empty relative to merged state), or merge it if preferred.
4. PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24 — can be merged before fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 if a smaller incremental diff is preferred; fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33's diff will then shrink to just the two workflow YAML changes.

Why a new fix branch was NOT created

The failures on PR #32 are not transient and the fix is not straightforward to apply to that branch in isolation — PR #32's base (fix/ci-type-errors-and-stale-test-date) itself lacks the code fixes. Creating a new branch fix/ci-24298790076 would reproduce exactly what PR #33 already contains. Merging PR #33 is the correct resolution.

---

Generated by CI/CD maintenance agent on 2026-05-01