{
  "context": "Tests whether the agent correctly handles a repository-local Vite+ version upgrade without a global CLI, using current vp migrate behavior, removing the obsolete test wrapper, classifying direct Vitest usage, and performing the correct end-to-end validation sequence.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "No global CLI dependency",
      "description": "The upgrade procedure does not install, inspect, or upgrade a global `vp`; every Vite+ operation resolves the repository-local CLI through `pnpm exec vp`",
      "max_score": 12
    },
    {
      "name": "Pinned package manager bootstrap",
      "description": "The procedure starts by honoring package.json#packageManager and installing the current lockfile with `pnpm install --frozen-lockfile` before invoking Vite+",
      "max_score": 8
    },
    {
      "name": "vp migrate for local stack",
      "description": "The project-local upgrade uses `pnpm exec vp migrate` from the project root so Vite+ updates the local `vite-plus` package and related toolchain pins together",
      "max_score": 10
    },
    {
      "name": "Core alias verified",
      "description": "The procedure verifies that `vp migrate` updated the `vite` -> `npm:@voidzero-dev/vite-plus-core@<matching-version>` alias in the manifest, catalog or override, and lockfile importer before calling the upgrade done",
      "max_score": 15
    },
    {
      "name": "Removed obsolete test wrapper",
      "description": "The procedure removes `@voidzero-dev/vite-plus-test` from dependencies, overrides/catalogs/resolutions, source references, and lockfile state instead of updating the removed wrapper",
      "max_score": 15
    },
    {
      "name": "vp outdated for verification",
      "description": "The procedure uses `vp outdated` to confirm that all Vite+ packages are now at the intended release (not `npm outdated`, `pnpm outdated`, or omitted entirely)",
      "max_score": 10
    },
    {
      "name": "Direct Vitest usage classified",
      "description": "The upgrade distinguishes node-mode-only projects from projects that directly use `vitest`, `@vitest/*`, coverage/UI packages, or browser providers, and only keeps direct upstream Vitest dependencies for the latter",
      "max_score": 8
    },
    {
      "name": "Local CLI version in validation",
      "description": "The end-to-end validation sequence verifies the repository-local CLI with `pnpm exec vp --version` and does not use the standalone-only `vp env` surface",
      "max_score": 6
    },
    {
      "name": "Full validation sequence",
      "description": "The validation sequence includes all of: `pnpm install --frozen-lockfile`, `pnpm exec vp check`, and `pnpm exec vp test`",
      "max_score": 9
    },
    {
      "name": "Build validation included",
      "description": "The validation sequence includes `vp build` or `vp pack` (as appropriate for the project type) to verify build artifacts after the upgrade",
      "max_score": 4
    },
    {
      "name": "No direct package manager for local Vite+ stack",
      "description": "The project-local upgrade does NOT use `npm install`, `pnpm update`, `yarn upgrade`, or other direct package-manager commands to select Vite+ package versions; the local Vite+ stack moves through `pnpm exec vp migrate`",
      "max_score": 3
    }
  ]
}