[CI] Maintenance audit (2026-05-02): PR #34 is clean + green — 7 stale fix PRs need triage

[erudenko]

Summary

CI maintenance audit run on 2026-05-02. No new failures were introduced — all outstanding CI failures (from early April) have working fixes in open PRs. The problem is that those PRs have not been merged in 3 weeks.

---

Root causes fixed in the open PRs

Root cause	First failed run	Fix
3 unused TypeScript imports (TS6133) — removeGitignoreEntries, vi, existsSync	24065489776	Removed in PRs #22–24, #33, #34
Stale hardcoded dates (2026-03-26) in stats tests — outside 7/14-day rolling query windows	24029941408	Rolling TODAY/YESTERDAY/TWO_DAYS_AGO constants in PRs #22–24, #33, #34
browser-use version drift — plugin.json at 1.1.2, marketplace.json still at 1.1.1	24276607217	Bumped in PRs #24, #28, #31, #33, #34
Workflow triggers restricted to branches: [main] — CI never fired on any fix branch	All of the above	Branch filter removed entirely in PRs #32, #33, #34

---

Current state of all open fix PRs

PR	Branch	CI	Mergeable	Scope	Verdict
#34	fix/ci-all-fixes-final	✅ All green (Apr 12)	✅ clean	All 4 root causes; removes branch filter entirely	MERGE THIS
#33	fix/ci-consolidated	✅ All green (Apr 12)	❌ dirty (merge conflict in workflow files)	All 4 root causes	Close — superseded by #34
#32	fix/ci-workflow-trigger-broadening	❌ Failing (TS + dates)	n/a	Trigger broadening only — stacked on unfixed base	Close — superseded by #34
#28	fix/ci-24276607217-browser-use-version	CI never ran (branch not in trigger list)	n/a	browser-use version only	Close — superseded by #34
#24	fix/ci-24065489776-ts-and-dates	✅ All green (Apr 11)	Likely dirty (workflow conflict with base)	TS + dates + browser-use + partial trigger	Close — superseded by #34
#23	fix/ci-typescript-and-stats-dates-resolved	CI never ran	n/a	TS + dates only	Close — superseded by #34
#22	fix/ci-typescript-and-stats-dates	CI never ran	n/a	TS + dates only	Close — superseded by #34
#31	fix/ci-main-browser-use-version	Only GitGuardian ran	n/a	Targets main (dist orphan — no workflow files)	Close — wrong base branch

---

Why PR #33 is conflicted despite green CI

PR #33 is branched from PR #24's HEAD. PR #24 modifies the workflow files to add fix/ci-type-errors-and-stale-test-date to the branches: list (going from [main] → [main, fix/ci-type-errors-and-stale-test-date]). However, the base branch already applied that same change via commits 220e8b8 and 7e440fb on April 11. This creates a conflict when GitHub tries to compute the merge for PR #33.

PR #34, by contrast, is based directly on the current tip of fix/ci-type-errors-and-stale-test-date (7e440fb) and removes the branches: key entirely — a clean diff from the current base state.

---

Recommended action

1. Review and merge PR fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34 — it is the only comprehensive fix that is both clean and green.
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(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(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, fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 as superseded by fix(ci): complete all-fixes branch — rolling stats dates in integration.test.ts + browser-use 1.1.2 #34. Each PR's description already cross-references the others.

After #34 is merged into fix/ci-type-errors-and-stale-test-date, any future PR or push targeting that branch (or any branch, since the branches: filter will be gone) will trigger full CI automatically.

---

Automated CI maintenance audit — claude-code agent