refactor(dev): drop dev:cache:prune in favour of the existing dev:clean

`dev:cache:prune` duplicated `dev:clean`, which already existed in `apps/sim` and
does strictly more (`rm -rf .next/dev/cache` covers the Turbopack cache plus the
fetch and image caches). Two commands for one job is worse than one, and the
docs pointed at the newer, narrower of the two.

Removes it from both apps and gives `apps/docs` the `dev:clean` that `apps/sim`
already had, so the recovery command is the same everywhere. `dev:cache:cap`
stays — it is the chained step, used by more than one dev variant, and naming it
keeps the relative script path out of each command.

Verified `dev:clean` is a real remedy: corrupt a cache block, run it, restart —
canvas serves 200 with no panic.

Also corrects an overstatement. A damaged cache does not *always* abort
Turbopack; whether it panics depends on whether the damaged region is read, so
it is not reliably reproducible. Both notes now say "can abort" and give the same
remedy either way.

Author: waleedlatif1

apps/docs/package.json

@@ -6,7 +6,7 @@
   "scripts": {
     "dev": "bun run dev:cache:cap && next dev --port 3001",
     "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",
     "build": "fumadocs-mdx && NODE_OPTIONS='--max-old-space-size=8192' next build",
     "start": "next start",
     "postinstall": "fumadocs-mdx",

apps/sim/next.config.ts

@@ -241,8 +241,9 @@ const nextConfig: NextConfig = {
      *
      * The cache is unbounded on disk (an abandoned one reached 78 GB here), so
      * `scripts/prune-turbopack-cache.ts` is chained into every `dev` script to cap it.
-     * A *corrupted* cache is a hard Turbopack panic, not a silent fallback —
-     * `bun run dev:cache:prune` and restart is the fix.
+     * A *corrupted* cache can abort Turbopack outright ("Cache corruption
+     * detected: checksum mismatch") rather than falling back — it depends whether
+     * the damaged region is read. `bun run dev:clean` and restart is the fix.
      *
      * If you re-measure any of this: `next dev` compiles routes on demand, so
      * startup time means nothing — time the first request to a route, restart the

apps/sim/package.json

@@ -12,7 +12,6 @@
     "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",
     "load:workflow": "bun run load:workflow:baseline",