test(e2e): add cloudflare/vinext to ecosystem-ci

- Add vinext to repo.json with forceFreshMigration (already uses vite-plus)
- Add e2e matrix entry: build, check, test on node 24, ubuntu-only
- Update add-ecosystem-ci skill to handle projects already using vite-plus

Author: fengmk2

.claude/skills/add-ecosystem-ci/SKILL.md

@@ -25,7 +25,11 @@ gh api repos/OWNER/REPO/commits/BRANCH --jq '.sha'
 
 Fetch the repository's root to check if the main package.json is in a subdirectory (like `web/`, `app/`, `frontend/`).
 
-### 2.2 Auto-detect Commands from GitHub Workflows
+### 2.2 Check if Project Already Uses Vite-Plus
+
+Check the project's root `package.json` for `vite-plus` in `dependencies` or `devDependencies`. If the project already uses vite-plus, set `forceFreshMigration: true` in `repo.json`. This is required because `patch-project.ts` runs `vp migrate` with locally built tgz overrides — without this flag, `vp migrate` detects "already using Vite+" and skips override injection, so the e2e test wouldn't actually test the locally built packages.
+
+### 2.3 Auto-detect Commands from GitHub Workflows
 
 Fetch the project's GitHub workflow files to detect available commands:
 
@@ -43,7 +47,7 @@ Look for common patterns in workflow files:
 - Commands like: `lint`, `build`, `test`, `type-check`, `typecheck`, `format`, `format:check`
 - Map detected commands to `vp` equivalents: `vp run lint`, `vp run build`, etc.
 
-### 2.3 Ask User to Confirm
+### 2.4 Ask User to Confirm
 
 Present the auto-detected configuration and ask user to confirm or modify:
 
@@ -62,7 +66,8 @@ Present the auto-detected configuration and ask user to confirm or modify:
        "repository": "https://github.com/owner/repo.git",
        "branch": "main",
        "hash": "full-commit-sha",
-       "directory": "web" // only if subdirectory is needed
+       "directory": "web", // only if subdirectory is needed
+       "forceFreshMigration": true // only if project already uses vite-plus
      }
    }
    ```
@@ -110,4 +115,5 @@ node ecosystem-ci/clone.ts project-name
 - The `directory` field is optional - only add it if the package.json is not in the project root
 - If `directory` is specified in repo.json, it must also be specified in the workflow matrix
 - `patch-project.ts` automatically handles running `vp migrate` in the correct directory
+- `forceFreshMigration` is required for projects that already have `vite-plus` in their package.json — it removes the existing dependency before migration so the locally built tgz overrides get injected
 - OS exclusions are added to the existing `exclude` section in the workflow matrix

.github/workflows/e2e-test.yml

@@ -257,6 +257,12 @@ jobs:
               vp check
               vp pack
               vp test
+          - name: vinext
+            node-version: 24
+            command: |
+              vp run build
+              vp run check
+              vp run test
         exclude:
           # frm-stack uses Docker (testcontainers) which doesn't work the same way on Windows
           - os: windows-latest
@@ -266,6 +272,10 @@ jobs:
           - os: windows-latest
             project:
               name: dify
+          # vinext uses workerd native deps that don't build on Windows
+          - os: windows-latest
+            project:
+              name: vinext
 
     steps:
       - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1

ecosystem-ci/repo.json

@@ -65,5 +65,11 @@
     "repository": "https://github.com/kazupon/vp-config.git",
     "branch": "main",
     "hash": "b58c48d71a17c25dec71a003535e6312791ce2aa"
+  },
+  "vinext": {
+    "repository": "https://github.com/cloudflare/vinext.git",
+    "branch": "main",
+    "hash": "f78dd2b39f5b02242417e0a684b1f2f55d3dbdff",
+    "forceFreshMigration": true
   }
 }