.svelte files are format-checked by nothing, locally or in CI

.svelte files are format-checked by nothing — locally or in CI.

Measured

scripts/prettier-changed.mjs filters the changed-file set to .ts/.tsx, and no Svelte prettier plugin is configured. So the ESLint + Prettier (changed files) CI check passes over a .svelte file in any state.

Two compounding details found while verifying this:

• The repo's root prettier is v2 and cannot parse Svelte at all — it emits a parse error alongside All matched files use Prettier code style!, so the reassuring line appears even on a file it failed to read.
• All matched files use Prettier code style! is also exactly what zero matched files produces. Any check of this gate needs a deliberately-misformatted control file in the same invocation, or a pass means nothing.

Closing condition

A misformatted .svelte file fails the ESLint + Prettier (changed files) check. Demonstrate with a deliberately-misformatted .svelte control in the same invocation, so the pass is distinguishable from a zero-file pass.

Checked by: a PR whose only change is a deliberately-misformatted .svelte file turns the ESLint + Prettier (changed files) check red, and pnpm prettier names that file.