{
  "context": "Tests whether the agent correctly handles a Vite+ version upgrade by distinguishing between the global CLI upgrade surface and the project-local upgrade surface, explicitly updating the Vite+ core alias, removing the obsolete test wrapper, classifying direct Vitest usage, and performing the correct end-to-end validation sequence.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "vp upgrade for global CLI",
      "description": "The upgrade procedure includes `vp upgrade` to update the global `vp` binary on the machine — distinct from updating the project-local package",
      "max_score": 12
    },
    {
      "name": "Global before local",
      "description": "The global `vp upgrade` step appears before (or is documented as separate from) the project-local `vp update` steps — the two surfaces are not conflated into a single operation",
      "max_score": 8
    },
    {
      "name": "vp update vite-plus",
      "description": "The project-local update includes `vp update vite-plus` (updating the vite-plus package itself)",
      "max_score": 10
    },
    {
      "name": "Explicit core alias update",
      "description": "The procedure explicitly updates `@voidzero-dev/vite-plus-core` with `vp update @voidzero-dev/vite-plus-core` (or combined with other packages) — NOT relying on `vp update vite-plus` alone to re-resolve this alias",
      "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": "vp env current in validation",
      "description": "The end-to-end validation sequence includes `vp env current` as the first check",
      "max_score": 6
    },
    {
      "name": "Full validation sequence",
      "description": "The validation sequence includes all of: `vp install`, `vp check`, and `vp test` (in addition to `vp env current`)",
      "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 Vite+ packages",
      "description": "The upgrade steps do NOT use `npm install`, `pnpm update`, `yarn upgrade`, or other direct package-manager commands for the Vite+ packages — all updates go through `vp update`",
      "max_score": 3
    }
  ]
}