You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was generated by the CI maintenance agent after reviewing the 10 most-recent failed GitHub Actions runs. All failures are real (not transient), all fixes already exist in open PRs, and no new fix branches were required.
plugins/stats/tests/db.test.ts and integration.test.ts used the hardcoded date "2026-03-26" which is now >17 days old — outside the 7-day and 14-day rolling query windows used by getSessionSummary, getTopTools, and getDurationTrend.
3. browser-use version mismatch in marketplace.json
plugins/browser-use/plugin.json is at v1.1.2 but .claude-plugin/marketplace.json was left at v1.1.1, causing the marketplace-sync integration test to fail.
4. Hardcoded branch filters in workflow triggers
test-plugins.yml and test-stats.yml had branches: [main, fix/ci-type-errors-and-stale-test-date] allowlists, making CI invisible to all other branches.
After merging, the base branch fix/ci-type-errors-and-stale-test-date will also become green (its current HEAD failures are what the fix PRs address).
Why No New Fix Branch Was Created
All 10 failed runs are from intermediate/stale commits on branches where the HEAD is already green, or from a branch that is fully superseded by an open PR with green CI. Creating a new fix/ci-<run-id> branch would duplicate work that already exists. The bottleneck is review and merge, not code.
CI Failure Audit — 2026-04-13
This issue was generated by the CI maintenance agent after reviewing the 10 most-recent failed GitHub Actions runs. All failures are real (not transient), all fixes already exist in open PRs, and no new fix branches were required.
The 10 Failed Runs
fix/ci-all-fixes-final84411b6dfix/ci-all-fixes-final84411b6dfix/ci-all-fixes-finalc12a54cffix/ci-all-fixes-finalea72ec07fix/ci-all-fixes-finale3d5e8dcfix/ci-all-fixes-finalb6de79a2fix/ci-all-fixes-finalb6de79a2fix/ci-workflow-trigger-broadening6f38db63fix/ci-workflow-trigger-broadening6f38db63fix/ci-workflow-trigger-broadening6f38db63Root Causes (all 4 addressed in existing PRs)
1. Unused TypeScript imports (TS6133)
tsc --noEmitfails undernoUnusedLocalsfor three imports left behind after refactors:conventions-integration.test.ts:removeGitignoreEntriesdoctor.test.ts:viconventions-manager.ts:existsSync2. Stale hardcoded test dates
plugins/stats/tests/db.test.tsandintegration.test.tsused the hardcoded date"2026-03-26"which is now >17 days old — outside the 7-day and 14-day rolling query windows used bygetSessionSummary,getTopTools, andgetDurationTrend.3.
browser-useversion mismatch inmarketplace.jsonplugins/browser-use/plugin.jsonis atv1.1.2but.claude-plugin/marketplace.jsonwas left atv1.1.1, causing themarketplace-syncintegration test to fail.4. Hardcoded branch filters in workflow triggers
test-plugins.ymlandtest-stats.ymlhadbranches: [main, fix/ci-type-errors-and-stale-test-date]allowlists, making CI invisible to all other branches.Current State of Fix PRs
fix/ci-all-fixes-finalfix/ci-consolidatedfix/ci-24065489776-ts-and-datesfix/ci-workflow-trigger-broadeningfix/ci-main-browser-use-versionmaindist-orphan)fix/ci-24276607217-browser-use-versionfix/ci-typescript-and-stats-dates-resolvedfix/ci-typescript-and-stats-datesRecommended Actions
Test Stats PluginandTest Plugins.fix/ci-type-errors-and-stale-test-datewill also become green (its current HEAD failures are what the fix PRs address).Why No New Fix Branch Was Created
All 10 failed runs are from intermediate/stale commits on branches where the HEAD is already green, or from a branch that is fully superseded by an open PR with green CI. Creating a new
fix/ci-<run-id>branch would duplicate work that already exists. The bottleneck is review and merge, not code.Generated by CI maintenance agent on 2026-04-13