From e9ca151d44174230adad9af2d2ad893260a24917 Mon Sep 17 00:00:00 2001
From: Eric J <wormeyman@gmail.com>
Date: Wed, 29 Jul 2026 16:37:28 -0700
Subject: [PATCH 1/2] chore(types): close the .vue type-check gap - adopt
 vue-tsc in verify

`pnpm run check:vue` (`vue-tsc --noEmit`) now runs inside `verify`, between
`vp check` and `vp test`. It is the only thing in this repo that type-checks
`<script setup lang="ts">` bodies - 22 `.vue` files that until now were
checked by nothing at all.

The gap was real and is reproduced here rather than asserted: a planted
`TS2322` in `src/ui/FInfo.vue` left `vp check` printing "Found no warnings,
lint errors, or type errors in 301 files", while `vue-tsc` reported
`src/ui/FInfo.vue(3,7): error TS2322` and `pnpm run verify` exited 2 with
the test suite never running. That plant-and-check is the proof the guard
is not vacuous; if a future change makes `check:vue` pass on a planted
error, it has been neutered.

Against the real tree: 22 files, 0 errors, ~2.5s. No latent breakage was
hiding behind the gap, so this is a regression guard, not a bug hunt. It
runs on the existing `typescript` 6.0.3 - `vue-tsc`'s peer range is
`>=5.0.0`, so no TypeScript 7 work was involved.

Two CLAUDE.md claims this falsified, both now corrected in place:

- **"Bare `vue-tsc --noEmit` crashes, it needs its own tsconfig excluding
  `vite.config.ts`."** No longer true, so no extra tsconfig is added here.
  That was measured 2026-07-22, one day before the `vue() as Plugin` cast
  landed in 388f285. Confirmed causally by deleting the cast and re-running:
  without it, `vp check` fails `TS2321` and `tsc` AND `vue-tsc` both die on
  the same `Debug Failure` assertion; with it, all three pass. So the
  `TS2321` and the `Debug Failure` crash are one pathology with one fix,
  not two problems.
- **"`verify` is ~9.5s."** Measured 63s. That was already wrong by ~6x
  before this commit - the suite grew to 143 files through the Vulcanus and
  cliff work - so it is corrected rather than merely adjusted for the
  ~2.5s this adds.

**Why it was rejected on 2026-07-22 and why that expired.** The only stated
blocker was supply-chain freshness: 3.3.8 was under an hour old and
installing it made pnpm silently write a `minimumReleaseAgeExclude` bypass.
It was 7.3 days old here, so the gate passed on its own and
`pnpm-workspace.yaml` is untouched by this commit - checked, not assumed.
The old fallback advice to "pick 3.3.7 instead" is now obsolete and has
been removed.

Also documented while in the area, because it misleads in a dangerous
direction: `pnpm config get minimumReleaseAge` reports `undefined`, which
reads like "no policy". The 24-hour guard comes from pnpm 11's own defaults
table (`"minimum-release-age": 24 * 60`), read out of pnpm 11.17.0's
shipped code. And TypeScript 7 is now written up as a "don't" rather than a
vague deferral: 7.0 ships no programmatic API at all (planned for 7.1), the
official migration is a dual-install alias, and `vue-tsc` hard-crashes on a
bare `typescript@7` with `ERR_PACKAGE_PATH_NOT_EXPORTED`.

`vue-tsc` is ranged `^3.3.8` to match every sibling devDependency.

Gate: `pnpm run verify` exit 0 - 314 files formatted, 301 files clean,
`check:vue` clean, app 1249 passed / 3 skipped, worker 12, container 3.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GjMSePtN9aTgr8EtZp66k1
---
 CLAUDE.md      | 160 ++++++++++++++++++++++++++++++++++---------------
 package.json   |   6 +-
 pnpm-lock.yaml |  69 +++++++++++++++++++++
 3 files changed, 184 insertions(+), 51 deletions(-)

diff --git a/CLAUDE.md b/CLAUDE.md
index 51369e4c..2c019307 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -144,20 +144,41 @@ Adding a root dependency needs `pnpm add -w` (or `--workspace-root`); a bare
 `pnpm add <pkg>` at the root fails with `ERR_PNPM_ADDING_TO_ROOT`. Prefer
 targeted `pnpm add` over `pnpm up` for dependency bumps - see the type-checking
 note below for why `pnpm up`'s transitive re-resolution can break `vp check`.
+Always follow any `add` with a bare `pnpm install`: `add` relinks only its own
+workspace and leaves sibling workspaces' symlinks dangling. Only the full
+install prints `Scope: all 3 workspace projects`.
+
+**The 24-hour release-age guard is real but invisible to `pnpm config`.**
+`pnpm config get minimumReleaseAge` reports `undefined`, which reads like "no
+policy here" - it only reports what is _explicitly_ set, and nothing in this
+repo or `~/.npmrc` sets it. The value comes from pnpm 11's own defaults table,
+`"minimum-release-age": 24 * 60, // 1 day` (read out of pnpm 11.17.0's shipped
+code, 2026-07-29). So a package published less than a day ago will not install
+without pnpm writing a `minimumReleaseAgeExclude` bypass into
+`pnpm-workspace.yaml` - which is the thing to watch for in a diff. Don't
+conclude the guard is off because `config get` came back empty, and don't rely
+on it silently either: a pnpm 12 could change the default, so if it ever
+matters, set it explicitly.
 
 - `pnpm install` - install deps
 - `pnpm vp dev` - dev server
 - `pnpm vp test` - full test suite (Vitest-compatible; tests import from `"vite-plus/test"`)
 - `pnpm vp test test/controlScale.spec.ts` - a single test file
-- `pnpm vp check --fix` - format + lint + **type-check**, the single static-check
-  step (see the type-checking note below; there is still **no** `vue-tsc` check
-  of `.vue` bodies)
+- `pnpm vp check --fix` - format + lint + **type-check** of `.ts`, the main
+  static-check step (see the type-checking note below). It does **not** see
+  inside `.vue` bodies - that is `check:vue`'s job, and the two together are the
+  full net.
+- `pnpm run check:vue` - `vue-tsc --noEmit`, the type-check of `<script setup>`
+  bodies in the 22 `.vue` files (~2.1s). Nothing else checks them.
 - `pnpm vp build` - production build
-- `pnpm run verify` - `vp check` + `vp test` + `preview:test` in one gate.
-  **~65-90s on a dev machine, ~4 minutes on a CI runner** - the `~9.5s` this
-  line claimed for a long time was simply wrong, and the gap mattered: 63s is
-  exactly the duration at which people start skipping a manual gate, which is
-  half the argument for the CI workflow below.
+- `pnpm run verify` - `vp check` + `check:vue` + `vp test` + `preview:test` in
+  one gate. **~65-90s on a dev machine, ~4 minutes on a CI runner**, of which
+  the app test suite is ~57s and `check:vue` ~2.5s. The `~9.5s` this line
+  claimed for a long time was simply wrong - already wrong by a factor of six
+  before `check:vue` existed, because the suite grew to 143 files through the
+  Vulcanus and cliff work - and the gap mattered: ~63s is exactly the duration
+  at which people start skipping a manual gate, which is half the argument for
+  the CI workflow below. Don't budget 10 seconds for this.
 - `pnpm refs:sync` - pin `factorioLuaAPI/` + `~/GitHub/factorio-data` to the
   installed binary's version (`--check` reports drift only; `--fixtures` reports
   which oracle fixtures predate the binary). Deliberately **not** part of
@@ -519,17 +540,21 @@ so `pnpm preview:test` fails loudly on drift.
 behind `lint.options.typeAware` + `lint.options.typeCheck` in `vite.config.ts` -
 both are on. Do not add a `tsc`-based `typecheck` script:
 
-- **`tsc` is not the type-check path.** Bare `./node_modules/.bin/tsc --noEmit`
-  **crashes** (`Debug Failure. False expression: parameter should have errors
-when reporting errors`) - a TypeScript 6.0.3 compiler bug, not a type error,
-  triggered by `vite.config.ts` alone. `vp check` type-checks that same file
-  fine because it uses **tsgolint** (the TypeScript Go toolchain), a different
-  implementation. Beware: passing globs (`tsc --noEmit 'src/**/*.ts'`) silently
-  ignores `tsconfig.json` and reports a misleading "ok".
-- **`.vue` bodies are still unchecked.** Neither `vp check` nor `tsc` reports
-  type errors inside `<script setup lang="ts">` (measured, not assumed). So
-  `vp check` is a partial net over `.ts` only, not a full gate. This gap is
-  **not** caused by the TS7 deferral - see below.
+- **`tsc` is not the type-check path**, but not because it crashes any more.
+  It used to: bare `./node_modules/.bin/tsc --noEmit` threw `Debug Failure.
+False expression: parameter should have errors when reporting errors` - a
+  TypeScript 6.0.3 compiler bug, not a type error, triggered by
+  `vite.config.ts` alone. **The `vue() as Plugin` cast below fixed that too**,
+  and both now exit 0. Still don't add a `tsc`-based `typecheck` script: it
+  duplicates what `vp check` already does through tsgolint, and it is one
+  transitive-graph shift away from crashing again. Beware also that passing
+  globs (`tsc --noEmit 'src/**/*.ts'`) silently ignores `tsconfig.json` and
+  reports a misleading "ok".
+- **`vp check` does not see inside `.vue` bodies** - it reports no type errors
+  inside `<script setup lang="ts">` (measured, not assumed: a planted `TS2322`
+  in `src/ui/FInfo.vue` left it printing "Found no warnings, lint errors, or
+  type errors in 301 files"). That gap is now covered by `pnpm run check:vue`,
+  chained into `verify` - see below. `vp check` alone is still a partial net.
 - **`vite.config.ts` sits near TypeScript's comparison-depth limit.** A shift in
   the transitive dependency graph can tip it over, making `vp check` fail with
   `TS2321: Excessive stack depth comparing types ... and 'UserConfig'` - the
@@ -550,30 +575,68 @@ when reporting errors`) - a TypeScript 6.0.3 compiler bug, not a type error,
     (`plugins: [vue() as Plugin]`, `type Plugin` imported from `vite-plus`)
     collapses the comparison without suppressing type-checking of the rest of
     the config. See voidzero-dev/vite-plus#2010's comment thread.
-- The project stays on `typescript` 6.0.3 as the _editor/LSP_ compiler; the TS7
-  upgrade is deferred because `vue-tsc`/Volar can't yet type-check `.vue`
-  against it. Note the type-_check_ already effectively runs on TS7 via
-  tsgolint, so the deferral only ever applied to `vue-tsc`.
-
-### Closing the `.vue` gap with `vue-tsc` (evaluated 2026-07-22, NOT adopted)
-
-The `.vue` gap is **not** blocked by the TS7 deferral, and a past framing that
-implied otherwise was wrong. `vue-tsc`'s peer range is `typescript: ">=5.0.0"`,
-so it runs on the project's existing 6.0.3. Spiked and measured:
-
-- It **does** catch errors inside `<script setup lang="ts">` (planted `TS2322`
-  and `TS2345` were both reported).
-- Against the real codebase: **22 `.vue` files, 0 errors, 1.56s**. There is no
-  latent breakage hiding behind the gap - adding it would be a guard against
-  future regressions, not a bug hunt.
-- Bare `vue-tsc --noEmit` **crashes** with the same `Debug Failure` assertion as
-  `tsc`, because it wraps `tsc` 6.0.3 and hits `vite.config.ts`. It needs its
-  own tsconfig that excludes that file.
-
-**Not adopted, for a supply-chain reason worth remembering.** `vue-tsc@3.3.8`
-was published the same day it was evaluated (< 1 hour old). This workspace
-enforces a pnpm minimum-release-age policy, and installing that fresh release
-made pnpm silently write a bypass into `pnpm-workspace.yaml`:
+
+    **That one cast is load-bearing for three tools, not one.** Removing it
+    (measured 2026-07-29, by deleting it and re-running) reproduces all three
+    failures at once: `vp check` fails `TS2321`, and `tsc` **and** `vue-tsc`
+    both die on the `Debug Failure` assertion. So `TS2321` in `vp check` and
+    the `Debug Failure` crash are one pathology with one fix - don't treat a
+    reappearance of either as a separate problem.
+
+- The project stays on `typescript` 6.0.3 as the _editor/LSP_ compiler, and
+  **TypeScript 7 is not an upgrade this repo can take** - see below. Note the
+  type-_check_ already effectively runs on TS7 semantics via tsgolint, so
+  nothing is being given up by staying.
+
+### TypeScript 7: `pnpm outdated`'s `6.0.3 -> 7.0.2` row is misleading
+
+Taking that row literally breaks the toolchain, so it is worth knowing why
+before someone bumps it. Re-derived 2026-07-29:
+
+- **TS 7.0 exposes no programmatic API at all.** It is a CLI-only Go binary;
+  the API is planned for 7.1. Anything that consumes the compiler
+  programmatically - tsserver, `vue-tsc`, typescript-eslint - cannot run on it.
+- The official migration is therefore a **dual install**, not a bump:
+  `typescript` aliased to `npm:@typescript/typescript6` (the JS API line) plus
+  `@typescript/native` aliased to `npm:typescript@^7` (the Go `tsc`).
+- `vue-tsc` on a bare `typescript@7` does not degrade, it **hard-crashes**:
+  `ERR_PACKAGE_PATH_NOT_EXPORTED: './lib/tsc'` (vuejs/language-tools#6124).
+  `vue-tsc@3.3.8` added shim resolution so it works _behind the alias_ - which
+  is the one thing 3.3.8 adds over 3.3.7, and it only matters if the alias is
+  adopted.
+- **And there is nothing to gain.** This repo's `typescript` devDep is purely
+  the editor/LSP compiler; the type-check already runs TS7 semantics through
+  tsgolint. The dual install would add a second compiler and an alias to buy
+  nothing the repo consumes.
+
+Revisit when 7.1 ships a programmatic API. Until then this is a "don't", not a
+"blocked on someone else".
+
+### The `.vue` gap is CLOSED - `vue-tsc` adopted 2026-07-29
+
+`pnpm run check:vue` (`vue-tsc --noEmit`) runs in `verify`, between `vp check`
+and `vp test`. It is the only thing that type-checks `<script setup lang="ts">`
+bodies.
+
+- **The guard is not vacuous, and was proven so before landing.** A planted
+  `TS2322` in `src/ui/FInfo.vue` makes `vue-tsc` report
+  `src/ui/FInfo.vue(3,7): error TS2322` and `pnpm run verify` exit **2** with
+  the test suite never running - while `vp check` on the same tree still
+  printed "Found no warnings, lint errors, or type errors in 301 files". If a
+  future change makes `check:vue` pass on a planted error, it has been
+  neutered.
+- Against the real codebase: **22 `.vue` files, 0 errors, ~2.1s**. There was no
+  latent breakage behind the gap; this is a guard against regressions, not a
+  bug hunt. It ran on the existing `typescript` 6.0.3 - `vue-tsc`'s peer range
+  is `>=5.0.0`, so no TS7 work was needed.
+- **It needs no separate tsconfig**, and a note here previously said it did.
+  That was measured 2026-07-22, one day _before_ the `vue() as Plugin` cast
+  landed; the cast fixed `vue-tsc`'s crash along with `vp check`'s `TS2321`.
+  Bare `vue-tsc --noEmit` on the root `tsconfig.json` is now clean.
+
+**Why it was not adopted on 2026-07-22, and why that reason expired.** The only
+blocker was supply-chain freshness: `vue-tsc@3.3.8` was under an hour old, and
+installing it made pnpm silently write a bypass into `pnpm-workspace.yaml`:
 
 ```yaml
 minimumReleaseAgeExclude:
@@ -581,12 +644,11 @@ minimumReleaseAgeExclude:
   - vue-tsc@3.3.8
 ```
 
-**Watch for that block appearing in a diff - it means a freshness guard was
-waived.** Don't commit one without a deliberate decision. If `vue-tsc` is
-adopted later, pick a release old enough to clear the policy (3.3.7 shipped
-2026-07-08 and needs no exclusion); the only thing 3.3.8 adds here is a fix for
-users aliasing `typescript` to `@typescript/typescript6` under the official TS7
-migration, which does not apply while the project is on 6.0.3 directly.
+**Watch for that block appearing in any diff - it means a freshness guard was
+waived.** Don't commit one without a deliberate decision. It did not appear
+this time: 3.3.8 was 7.3 days old when adopted, so the gate passed on its own
+and `pnpm-workspace.yaml` was untouched. The old advice to "pick 3.3.7 instead"
+is obsolete - just take the latest once it has aged past the policy.
 
 ### Remaining build/test log noise (investigated, left alone)
 
diff --git a/package.json b/package.json
index cdeee2b1..b50cfa9e 100644
--- a/package.json
+++ b/package.json
@@ -10,9 +10,10 @@
     "test": "vp test",
     "perf": "FMW_PERF=1 vp test test/render-cost.perf.spec.ts && cat perf-result.txt",
     "check": "vp check --fix",
+    "check:vue": "vue-tsc --noEmit",
     "refs:sync": "bash scripts/sync-factorio-refs.sh",
     "verify:deploy": "node scripts/verify-deploy.ts",
-    "verify": "vp check && vp test && pnpm run preview:test",
+    "verify": "vp check && pnpm run check:vue && vp test && pnpm run preview:test",
     "localpreview": "pnpm run preview:dev",
     "preview:dev": "concurrently -k -n worker,app -c blue,green \"pnpm run preview:worker\" \"pnpm run preview:app\"",
     "preview:worker": "pnpm --filter @fmw/preview-worker exec wrangler dev --var ALLOWED_ORIGIN:http://localhost:5173",
@@ -35,7 +36,8 @@
     "concurrently": "^10.0.4",
     "happy-dom": "^20.11.1",
     "typescript": "^6.0.3",
-    "vite-plus": "^0.2.6"
+    "vite-plus": "^0.2.6",
+    "vue-tsc": "^3.3.8"
   },
   "devEngines": {
     "packageManager": {
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 3069bc8c..7812ed3d 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -244,6 +244,9 @@ importers:
       vite-plus:
         specifier: ^0.2.6
         version: 0.2.6(@types/node@26.1.1)(esbuild@0.28.1)(happy-dom@20.11.1)(typescript@6.0.3)(vite@8.1.2(@types/node@26.1.1)(esbuild@0.28.1))
+      vue-tsc:
+        specifier: ^3.3.8
+        version: 3.3.8(typescript@6.0.3)
 
   preview-service/container: {}
 
@@ -1301,6 +1304,15 @@ packages:
     cpu: [x64]
     os: [win32]
 
+  '@volar/language-core@2.4.28':
+    resolution: {integrity: sha512-w4qhIJ8ZSitgLAkVay6AbcnC7gP3glYM3fYwKV3srj8m494E3xtrCv6E+bWviiK/8hs6e6t1ij1s2Endql7vzQ==}
+
+  '@volar/source-map@2.4.28':
+    resolution: {integrity: sha512-yX2BDBqJkRXfKw8my8VarTyjv48QwxdJtvRgUpNE5erCsgEUdI2DsLbpa+rOQVAJYshY99szEcRDmyHbF10ggQ==}
+
+  '@volar/typescript@2.4.28':
+    resolution: {integrity: sha512-Ja6yvWrbis2QtN4ClAKreeUZPVYMARDYZl9LMEv1iQ1QdepB6wn0jTRxA9MftYmYa4DQ4k/DaSZpFPUfxl8giw==}
+
   '@vue/compiler-core@3.5.40':
     resolution: {integrity: sha512-39E8IgOhTbVDnoJFMKc2DvYnypcZwUqgUhQkccva/0m6FUwtIKSGV7n1hpVmYcFaoRAwf9pBcwnKlCEsN63ZEQ==}
 
@@ -1322,6 +1334,9 @@ packages:
   '@vue/devtools-shared@8.2.1':
     resolution: {integrity: sha512-Fkac7lUdGReh6pVOi3AYPRGe82LQqRmAfThW7RRligOAP0ZA/Z1z9XLHDM9dv34pV2HRc79DK8uKPeG2fLnA/g==}
 
+  '@vue/language-core@3.3.8':
+    resolution: {integrity: sha512-ieGT8jJdhhy0mGzStZhsg/qPw5bQZJg5yF+3+XU6saf4sM7yo9ZXy3h+nCwrm2+b4qS/SypkNdR2jAF3uei9tA==}
+
   '@vue/reactivity@3.5.40':
     resolution: {integrity: sha512-B7ot9UlUZOi1zbq61/LvE88ZLTV8IlajTdiZTAEiDQgrnIMIZoPr9kGw0Zw46ObW62O9+H/Be3kMbfb7kYPQZA==}
 
@@ -1476,6 +1491,9 @@ packages:
     resolution: {integrity: sha512-6/mh1E2u2YgEsCHdY0Yx5oW+61gZU+1vXaoiHHrpKeuRNNgFvS+/jrwHiQhB5apAf5oB7UB7E19ol2R2LKH8hQ==}
     engines: {node: ^14.17.0 || ^16.13.0 || >=18.0.0}
 
+  alien-signals@3.2.1:
+    resolution: {integrity: sha512-I8FjmltrfnDFoZedi5CG8DghVYNhzb/Ijluz7tCSJH0xpd0484Kowhbb1XDYOxfJpU1p5wnM2X54dA+IfGyD1g==}
+
   ansi-regex@5.0.1:
     resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
     engines: {node: '>=8'}
@@ -1809,6 +1827,9 @@ packages:
     resolution: {integrity: sha512-Y3wQdFg2Va6etvQ5I82yUhGdsKrcYox6p7FfL1LbK2J4V01F9TGlepTIhnK24t7koZibmg82KGglhA1XK5IsLQ==}
     engines: {node: '>=10'}
 
+  muggle-string@0.4.1:
+    resolution: {integrity: sha512-VNTrAak/KhO2i8dqqnqnAHOa3cYBwXEZe9h+D5h/1ZqFSTEFHdM65lR7RoIqq3tBBYavsOXV84NoHXZ0AkPyqQ==}
+
   nanoid@3.3.16:
     resolution: {integrity: sha512-bzlKTyNJ7+LdGIIwy8ijFpIqEQIvafahV7eYykJ8Cvh42EdJeODoJ6gUJXpQJvej1BddH8OqTXZNE/KfbWAu8Q==}
     engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
@@ -1865,6 +1886,9 @@ packages:
   pako@3.0.1:
     resolution: {integrity: sha512-GupotUUI0mlhugKjUs4bjOwLt3nrehy9Ys2dxC0GtgVef5cnKggkDMmf2bq2poCCuVXopWPmqsc9VDT2iJUy+w==}
 
+  path-browserify@1.0.1:
+    resolution: {integrity: sha512-b7uo2UCUOYZcnF/3ID0lulOJi/bafxa1xPe7ZPsammBSpjSWQkjNxlt635YGS2MiR9GjvuXCtz2emr3jbsz98g==}
+
   path-key@3.1.1:
     resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
     engines: {node: '>=8'}
@@ -2151,9 +2175,18 @@ packages:
       jsdom:
         optional: true
 
+  vscode-uri@3.1.0:
+    resolution: {integrity: sha512-/BpdSx+yCQGnCvecbyXdxHDkuk55/G3xwnC0GqY4gmQ3j+A+g8kzzgB4Nk/SINjqn6+waqw3EgbVF2QKExkRxQ==}
+
   vue-component-type-helpers@3.3.7:
     resolution: {integrity: sha512-Skkhw9agYSgsWqv7bxSOGJZa9SaiJbZVGdXuFWnrzKaQYHnw9qbjD630rw6RyMqDbp54nfLCLw5SZA55if7JLg==}
 
+  vue-tsc@3.3.8:
+    resolution: {integrity: sha512-xXmYlVQpcwJDWyGlqbHrGVOl1h3UOsASymRibrHc+iy9j/UNnOrOn4u+fntHz4D6Cs74RtapeqVV6CzJeg+UlA==}
+    hasBin: true
+    peerDependencies:
+      typescript: '>=5.0.0'
+
   vue@3.5.40:
     resolution: {integrity: sha512-+8PJ4SJXdn/cHGImF4CKdxlWHIN5Dkt7DoufRREM6h6uVCx2m7QxgcEQmmzyOK8A9mcafg7sFbJFYsdFVubTig==}
     peerDependencies:
@@ -2907,6 +2940,18 @@ snapshots:
   '@voidzero-dev/vite-plus-win32-x64-msvc@0.2.6':
     optional: true
 
+  '@volar/language-core@2.4.28':
+    dependencies:
+      '@volar/source-map': 2.4.28
+
+  '@volar/source-map@2.4.28': {}
+
+  '@volar/typescript@2.4.28':
+    dependencies:
+      '@volar/language-core': 2.4.28
+      path-browserify: 1.0.1
+      vscode-uri: 3.1.0
+
   '@vue/compiler-core@3.5.40':
     dependencies:
       '@babel/parser': 7.29.7
@@ -2950,6 +2995,16 @@ snapshots:
 
   '@vue/devtools-shared@8.2.1': {}
 
+  '@vue/language-core@3.3.8':
+    dependencies:
+      '@volar/language-core': 2.4.28
+      '@vue/compiler-dom': 3.5.40
+      '@vue/shared': 3.5.40
+      alien-signals: 3.2.1
+      muggle-string: 0.4.1
+      path-browserify: 1.0.1
+      picomatch: 4.0.5
+
   '@vue/reactivity@3.5.40':
     dependencies:
       '@vue/shared': 3.5.40
@@ -3053,6 +3108,8 @@ snapshots:
 
   abbrev@2.0.0: {}
 
+  alien-signals@3.2.1: {}
+
   ansi-regex@5.0.1: {}
 
   ansi-regex@6.2.2: {}
@@ -3359,6 +3416,8 @@ snapshots:
 
   mrmime@2.0.1: {}
 
+  muggle-string@0.4.1: {}
+
   nanoid@3.3.16: {}
 
   nopt@7.2.1:
@@ -3433,6 +3492,8 @@ snapshots:
 
   pako@3.0.1: {}
 
+  path-browserify@1.0.1: {}
+
   path-key@3.1.1: {}
 
   path-scurry@1.11.1:
@@ -3737,8 +3798,16 @@ snapshots:
     transitivePeerDependencies:
       - msw
 
+  vscode-uri@3.1.0: {}
+
   vue-component-type-helpers@3.3.7: {}
 
+  vue-tsc@3.3.8(typescript@6.0.3):
+    dependencies:
+      '@volar/typescript': 2.4.28
+      '@vue/language-core': 3.3.8
+      typescript: 6.0.3
+
   vue@3.5.40(typescript@6.0.3):
     dependencies:
       '@vue/compiler-dom': 3.5.40

From 9934a458d23e463b7331e48d7578c48c3d35c0b7 Mon Sep 17 00:00:00 2001
From: Eric J <wormeyman@gmail.com>
Date: Wed, 29 Jul 2026 22:41:23 -0700
Subject: [PATCH 2/2] docs: fold check:vue into the places that enumerate
 verify's phases

`verify` gained a fourth phase, so three places that spell the list out went
stale the moment it did. CLAUDE.md was updated in the parent commit; these were
not:

- `README.md` listed the gate as `vp check` + `vp test` + `preview:test` in two
  places (the script list and the deploy section) and had no `check:vue` entry
  at all, so the one command that type-checks `.vue` bodies was undiscoverable
  from the README.
- `.github/workflows/verify.yml`'s comment said "its three phases". The count is
  the whole point of that comment - it explains why the workflow calls
  `pnpm run verify` verbatim instead of re-listing phases as steps.

Comment-only in the YAML: no step is added and no phase is mirrored into CI,
which is deliberate - `verify` stays the single definition and CI picks up the
new phase with no workflow change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01F3a2HLJ4beKARi7SPmaM54
---
 .github/workflows/verify.yml |  2 +-
 README.md                    | 10 ++++++----
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/verify.yml b/.github/workflows/verify.yml
index 61f925af..53195cbc 100644
--- a/.github/workflows/verify.yml
+++ b/.github/workflows/verify.yml
@@ -3,7 +3,7 @@
 # days after the breaking merge) - see issue #54.
 #
 # This job deliberately runs `pnpm run verify` VERBATIM rather than re-listing
-# its three phases as separate steps. `verify` is the single definition of "the
+# its four phases as separate steps. `verify` is the single definition of "the
 # repo is consistent"; splitting it here would create a second definition that
 # can silently drift from package.json. Note it is `verify`, not `check` -
 # `check` is `vp check --fix` and CI must never rewrite files.
diff --git a/README.md b/README.md
index 282a0a50..0e1afb92 100644
--- a/README.md
+++ b/README.md
@@ -83,11 +83,13 @@ root fails with `EBADDEVENGINES`).
 
 - `pnpm install` - install dependencies
 - `pnpm vp dev` - dev server
-- `pnpm vp check --fix` - lint + format + type-check
+- `pnpm vp check --fix` - lint + format + type-check of `.ts`
+- `pnpm run check:vue` - `vue-tsc --noEmit`, the type-check of `<script setup>`
+  bodies in the `.vue` files. Nothing else checks them.
 - `pnpm vp test` - test suite (fixture-driven codec tests and UI tests)
 - `pnpm vp build` - production build
-- `pnpm run verify` - the whole gate: `vp check` + `vp test` + `preview:test`.
-  ~65-90s locally. Needs no Factorio install.
+- `pnpm run verify` - the whole gate: `vp check` + `check:vue` + `vp test` +
+  `preview:test`. ~65-90s locally. Needs no Factorio install.
 
 ### CI
 
@@ -136,7 +138,7 @@ test: `pnpm --filter @fmw/preview-container test:integration`.
 The app and preview service are already deployed (Cloudflare Pages +
 Workers/Containers on the `wormeyman` account; `pnpm run deploy` verifies,
 builds, and publishes the app). Both deploy paths are gated: `pnpm run deploy`
-runs `pnpm run verify` (`vp check` + `vp test` + `preview:test`) first and
+runs `pnpm run verify` (`vp check` + `check:vue` + `vp test` + `preview:test`) first and
 aborts before `wrangler` if anything fails. The one-time setup, for reference, needs a Cloudflare account
 and Workers Paid ($5/mo, required for Containers):