improvement(dev): chain the cache prune into dev scripts instead of a predev hook

Review read the root `bun run dev` path as bypassing the `predev` hook and so
never capping the newly-enabled cache. Turbo does fire `pre*` hooks — verified
live, the run prints the prune before `next dev` — but the concern is fair in
that the guarantee rested on package-manager lifecycle semantics that are
invisible at the call site.

Chaining it explicitly removes the question entirely: every `dev` variant now
runs `bun run dev:cache:cap && …`, which holds on any invocation path, is
visible in the command itself, and drops the three duplicated `predev:*` entries
for one shared script.

Verified on both paths — direct `bun run dev` and root `turbo run dev`, the
latter printing:

  sim:dev: $ bun run dev:cache:cap && next dev --port 3000
  sim:dev: $ bun run ../../scripts/prune-turbopack-cache.ts

Author: waleedlatif1

.agents/skills/dev-performance/SKILL.md

@@ -35,7 +35,9 @@ If your numbers are wildly off these, suspect your method before suspecting a re
 
 Never reason about one from the other, and never change either from a blog post or a default. Both are pinned explicitly so a version bump can't silently flip them.
 
-The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` runs on `predev` and drops it past a cap (default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override). Force it with `bun run dev:cache:prune`.
+The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` is chained into every `dev` script (`bun run dev:cache:cap && next dev`) and drops the cache past a cap — default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override. Force it with `bun run dev:cache:prune`.
+
+Chained explicitly rather than via a `predev` lifecycle hook: Turbo does fire `pre*` hooks (verified), but an explicit `&&` is visible in the command, survives any invocation path, and needs no per-variant `predev:*` duplicate.
 
 ## How to benchmark a dev-performance change
 

.claude/commands/dev-performance.md

@@ -34,7 +34,9 @@ If your numbers are wildly off these, suspect your method before suspecting a re
 
 Never reason about one from the other, and never change either from a blog post or a default. Both are pinned explicitly so a version bump can't silently flip them.
 
-The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` runs on `predev` and drops it past a cap (default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override). Force it with `bun run dev:cache:prune`.
+The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` is chained into every `dev` script (`bun run dev:cache:cap && next dev`) and drops the cache past a cap — default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override. Force it with `bun run dev:cache:prune`.
+
+Chained explicitly rather than via a `predev` lifecycle hook: Turbo does fire `pre*` hooks (verified), but an explicit `&&` is visible in the command, survives any invocation path, and needs no per-variant `predev:*` duplicate.
 
 ## How to benchmark a dev-performance change
 

.cursor/commands/dev-performance.md

@@ -30,7 +30,9 @@ If your numbers are wildly off these, suspect your method before suspecting a re
 
 Never reason about one from the other, and never change either from a blog post or a default. Both are pinned explicitly so a version bump can't silently flip them.
 
-The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` runs on `predev` and drops it past a cap (default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override). Force it with `bun run dev:cache:prune`.
+The dev cache is unbounded on disk — an abandoned one in this repo reached **78 GB across 1,848 SST files**. `scripts/prune-turbopack-cache.ts` is chained into every `dev` script (`bun run dev:cache:cap && next dev`) and drops the cache past a cap — default 20 GB, `SIM_TURBOPACK_CACHE_MAX_GB` to override. Force it with `bun run dev:cache:prune`.
+
+Chained explicitly rather than via a `predev` lifecycle hook: Turbo does fire `pre*` hooks (verified), but an explicit `&&` is visible in the command, survives any invocation path, and needs no per-variant `predev:*` duplicate.
 
 ## How to benchmark a dev-performance change
 

apps/sim/next.config.ts

@@ -240,7 +240,7 @@ const nextConfig: NextConfig = {
      * is not covered by the #6078 build A/B cited below.
      *
      * The cache is unbounded on disk (an abandoned one reached 78 GB here), so
-     * `scripts/prune-turbopack-cache.ts` runs on `predev` to cap it.
+     * `scripts/prune-turbopack-cache.ts` is chained into every `dev` script to cap it.
      */
     turbopackFileSystemCacheForDev: true,
     /**

apps/sim/package.json

@@ -8,12 +8,10 @@
     "node": ">=22.19.0"
   },
   "scripts": {
-    "predev": "bun run ../../scripts/prune-turbopack-cache.ts",
-    "dev": "next dev --port 3000",
-    "predev:minimal": "bun run ../../scripts/prune-turbopack-cache.ts",
-    "dev:minimal": "SIM_DEV_MINIMAL_REGISTRY=1 next dev --port 3000",
-    "predev:capped": "bun run ../../scripts/prune-turbopack-cache.ts",
-    "dev:capped": "NODE_OPTIONS='--max-old-space-size=4096' next dev --port 3000",
+    "dev": "bun run dev:cache:cap && next dev --port 3000",
+    "dev:minimal": "bun run dev:cache:cap && SIM_DEV_MINIMAL_REGISTRY=1 next dev --port 3000",
+    "dev:capped": "bun run dev:cache:cap && NODE_OPTIONS='--max-old-space-size=4096' next dev --port 3000",
+    "dev:cache:cap": "bun run ../../scripts/prune-turbopack-cache.ts",
     "dev:cache:prune": "bun run ../../scripts/prune-turbopack-cache.ts --force",
     "dev:clean": "rm -rf .next/dev/cache",
     "dev:webpack": "next dev --webpack",