ci: fix PR backlog — 8 open PRs, 50+ stale branches, none merged (action required)

[erudenko]

CI Maintenance Agent Report — 2026-05-06

This issue is filed by the CI maintenance agent after auditing all recent failed runs and open fix PRs. No new failures were found — every root cause has been addressed in existing PRs. The problem is that none of those PRs have been merged, causing a growing pile of stale branches and competing fix PRs.

---

Confirmed Failures (historical, April 2026)

Run ID	Workflow	Branch	Failure
24065489776	Test Plugins	fix/ci-type-errors-and-stale-test-date	tsc --noEmit — 3 unused TS imports (TS6133)
24063290384	Test Plugins	fix/ci-type-errors-and-stale-test-date	shared-deps out of sync + type check
24029941408	Test Stats Plugin	fix/ci-type-errors-and-stale-test-date	stale hardcoded date 2026-03-26 in time-windowed queries
24029941414	Test Stats Plugin	fix/ci-type-errors-and-stale-test-date	same stale date failure
24276607217	Test Plugins	fix/ci-24065489776-ts-and-dates	marketplace-sync: browser-use version mismatch (1.1.1 vs 1.1.2)
24298790072	Test Plugins	fix/ci-workflow-trigger-broadening	inherited TS errors from base branch
24298790076	Test Stats Plugin	fix/ci-workflow-trigger-broadening	inherited stale date from base branch

All of these are from April 12 or earlier. No new failures exist on currently active branches.

---

Root Causes (all now fixed in existing PRs)

1. Unused TypeScript imports (TS6133) — removeGitignoreEntries, vi, existsSync left behind by refactors in tools/claudeup-core. Fixed in PR fix(ci): remove 3 unused TS imports + fix stale stats dates + re-enable CI triggers #24.
2. Stale hardcoded test dates — plugins/stats/tests/db.test.ts and integration.test.ts used "2026-03-26", which fell outside rolling 7/14-day query windows. Fixed with dynamic TODAY/YESTERDAY/TWO_DAYS_AGO constants in 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.
3. browser-use version drift — plugins/browser-use/plugin.json at 1.1.2 but marketplace.json still at 1.1.1. Fixed in PRs 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/fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34.
4. CI workflow trigger restrictions — both test-plugins.yml and test-stats.yml had a branches allowlist that made most fix branches invisible to CI. Fixed in PRs fix(ci): remove hardcoded branch filters from workflow triggers #32/fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33.

---

Open PRs Status

PR	Branch	CI	Contains	Status
#22	fix/ci-typescript-and-stats-dates	GitGuardian only	TS fixes + stale dates	Superseded by #24
#23	fix/ci-typescript-and-stats-dates-resolved	GitGuardian only	Same + conflict resolution	Superseded by #24
#24	fix/ci-24065489776-ts-and-dates	✅ ALL GREEN	TS fixes + dates + browser-use + triggers	Ready to merge
#28	fix/ci-24276607217-browser-use-version	GitGuardian only	browser-use bump (stacked on #24)	Superseded by #24
#31	fix/ci-main-browser-use-version	N/A (targets dist-only main)	browser-use bump	Wrong base branch — close
#32	fix/ci-workflow-trigger-broadening	❌ OLD FAILURES	Trigger broadening only	Superseded by #33
#33	fix/ci-consolidated	✅ ALL GREEN	All fixes + trigger broadening	Ready to merge (supersedes #32)
#34	fix/ci-all-fixes-final	✅ ALL GREEN	All fixes from #33 + final integration.test.ts dates	Ready to merge (most complete)

---

Recommended Action

Simplest path (one merge):

Merge PR #33 (fix/ci-consolidated → fix/ci-type-errors-and-stale-test-date)

PR #33 is all-green, self-contained, and consolidates everything: TS import removal, dynamic test dates, browser-use version bump, and CI trigger broadening. After merging #33, close PRs #22, #23, #24, #28, #32 as superseded, and close #31 as targeting the wrong branch.

If you want the extra date fix in #34:

Merge PR #33 first, then merge PR #34 (it adds the dynamic date fix to integration.test.ts which #33 already covers via its base). Alternatively, just merge PR #34 directly if it's fully rebased — its CI is also all-green and it contains a superset of #33's fixes.

---

Branch Cleanup

There are currently 50+ fix/ci-* branches that are stale and no longer needed. After merging the chosen fix PR, consider deleting all fix/ci-* branches except the source branch (fix/ci-type-errors-and-stale-test-date).

---

Note on Repository Structure

main is a dist-only orphan branch that receives automated distribution commits. It has no CI workflow files. All source code and CI live on fix/ci-type-errors-and-stale-test-date. This is an unusual setup — consider promoting the source branch to main or creating a stable develop/source branch to make the repository structure clearer for future contributors and agents.

[erudenko]

Correction (CI maintenance agent, 2026-05-06):

The body of this issue recommends merging PR #33, but that recommendation is out of date. As of 2026-05-06:

• PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (fix/ci-consolidated) — mergeable_state: dirty ❌ has a merge conflict; cannot be merged as-is
• PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 (fix/ci-all-fixes-final) — mergeable_state: clean ✅ no conflicts; all 13 CI checks pass

Correct action: merge PR #34, then close PRs #22, #23, #28, #31, #32, #33 as superseded.

See issue #133 for the authoritative current-state analysis.

---

Generated by Claude Code