mirror of
https://github.com/civitai/civitai.git
synced 2026-09-20 22:08:18 +08:00
briant
e83150e84f
VS Code was watching and indexing every SvelteKit build artifact: `files.watcherExclude` covered `node_modules`, `.next` and `dist` but was never updated when the SvelteKit apps landed, so `.svelte-kit` (947 files) and `apps/*/build` (845) were unexcluded. A build writes ~1,800 files / 25MB into the workspace. `defender-exclusions.ps1` defaulted to `C:\Dev\Repos\work`, which is not where this repo lives. Add-MpPreference accepts a nonexistent path, so run with defaults it reported success and excluded nothing. It now resolves the repo from its own location and throws rather than silently no-op when the root is missing. Hook changes: drop the `svelte-kit sync` / `pnpm check` guard (sync alone is cheap - 121 generated files, not the ~690 the docs claim) and guard `build` instead, which is the expensive one and is not a check. Set to ask rather than block: diagnosing a build-only failure and producing a real artifact are both legitimate. check-svelte-ts.mjs removes the main reason to run a build at all. Svelte 5 strips the type annotation from `(n?: number)` but leaves the `?`, so rollup rejects it while typecheck, dev and every review agent pass. It now fails on write. Verified against all 148 committed .svelte files: catches the defect, zero false positives (the first version had five, all `?` in type position). Adds retool-fidelity-review, the export-vs-build pass. It was prose in the skill that got performed by hand, differently each time, and skipped twice - despite being the only review that can see a capability nobody wrote. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>