CI maintenance: 3 failing runs on PR #32 — fixes ready in PR #33, awaiting merge

[erudenko]

CI Maintenance Report — 2026-05-02

This issue was created by the CI maintenance agent after investigating recent failing GitHub Actions runs via the GitHub API (the gh CLI was not available in the execution environment).

---

Failing Runs Found

Run ID	Workflow	Branch / PR	Failing Job	Conclusion
24298790072	Test Plugins	fix/ci-workflow-trigger-broadening (PR #32)	test (20)	failure
24298790076	Test Stats Plugin	fix/ci-workflow-trigger-broadening (PR #32)	test (stats)	failure
24298782547	Test Stats Plugin	fix/ci-workflow-trigger-broadening (PR #32)	test (stats)	failure

All three failures are on PR #32's head commit (6f38db6), triggered on 2026-04-12.

---

Root Cause Analysis

PR #32 (fix/ci-workflow-trigger-broadening) correctly removed the hardcoded branches allowlist from test-plugins.yml and test-stats.yml, which caused CI to finally run on fix branches. However, it was stacked on top of fix/ci-type-errors-and-stale-test-date without the code-level fixes, so when CI ran, it immediately hit the underlying code failures:

Failure 1 — test (20) in run 24298790072 (Test Plugins)

• Cause: tsc --noEmit fails under noUnusedLocals — three stale imports left after refactors:
  • tools/claudeup-core/src/__tests__/integration/conventions-integration.test.ts: removeGitignoreEntries
  • tools/claudeup-core/src/__tests__/unit/doctor.test.ts: vi
  • tools/claudeup-core/src/services/conventions-manager.ts: existsSync

Failures 2 & 3 — test in runs 24298790076 / 24298782547 (Test Stats Plugin)

• Cause: plugins/stats/tests/db.test.ts and integration.test.ts used the hardcoded date "2026-03-26", which is now well outside the 7-day and 14-day rolling query windows used by getSessionSummary, getTopTools, and getDurationTrend. Those tests assert length > 0 / specific counts and return zero rows.

---

Fix Status — Already Implemented

The fixes for all three failures already exist in open PRs with fully green CI:

PR	Branch	CI Status	Covers
#33	fix/ci-consolidated	✅ All 7 checks pass	TS imports + rolling dates + browser-use 1.1.2 + trigger broadening
#24	fix/ci-24065489776-ts-and-dates	✅ All 7 checks pass	TS imports + rolling dates + browser-use 1.1.2
#34	fix/ci-all-fixes-final	✅ All 13 checks pass	TS imports + rolling dates + browser-use 1.1.2

PR #33 is the recommended merge target. It is a superset of PR #32 (trigger broadening) and PR #24 (all code fixes), with every check green.

---

Recommended Merge Path

1. Merge PR fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 (fix/ci-consolidated → fix/ci-type-errors-and-stale-test-date) — this resolves all three failing runs and all root causes.
2. After merging, close the following superseded PRs (no further action needed):
   • PR fix(ci): remove unused TS imports + fix stale stats test dates #22 (fix/ci-typescript-and-stats-dates) — partial fix, superseded
   • PR fix(ci): resolve merge conflict — unused TS imports + stale stats test dates #23 (fix/ci-typescript-and-stats-dates-resolved) — conflict-resolved partial, superseded
   • PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 in marketplace.json #28 (fix/ci-24276607217-browser-use-version) — browser-use only, superseded
   • PR fix(marketplace): bump browser-use version 1.1.1 → 1.1.2 to fix CI #31 (fix/ci-main-browser-use-version) — targets dist-only main, CI can never run there
   • PR fix(ci): remove hardcoded branch filters from workflow triggers #32 (fix/ci-workflow-trigger-broadening) — trigger fix only, superseded by fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33
   • 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) — duplicate of fix(ci): consolidated — TS imports, stale dates, browser-use version, unrestricted triggers #33 on a different branch

---

Note on main Branch

The main branch in this repo is a distribution-only orphan branch — it holds only the compiled/published artefacts and has no workflow YAML files. CI (test-plugins.yml, test-stats.yml) cannot and does not run against main. Source code and CI workflows live on fix/ci-type-errors-and-stale-test-date and its descendants. PR #31 (which targets main) will never get test CI coverage for this reason.

---

Generated by CI maintenance agent — no new fix branches were created because the fixes already exist in PR #33 with green CI.