docs: correct the claim that Turbopack ignores outputFileTracingIncludes

Two documents said Next skips trace collection under Turbopack and
concluded the option therefore never runs. The first half is true and the
conclusion does not follow: `collectBuildTraces` is skipped, but Turbopack
emits the `.nft.json` files and applies the include globs itself.

Measured against a Turbopack build of this app rather than argued from
`next/dist`: `next-server.js.nft.json`, which the `'/**'` key does not
cover, lists three `@swc/helpers` entries and none under `esm/`; a route's
`.nft.json`, which it does cover, lists over a thousand including 324
under `esm/` and the package's `LICENSE`, a file no tracer would follow.
The glob is load-bearing, not dead code, and the gate guarding its pinned
version guards something real.

That reading also produced a false explanation for the missing migration
`.sql` files on Vercel. They are absent because nothing imports them and
nothing lists them, not because the mechanism is unavailable — the
schema-check the installer now does stands on its own arguments, which
were always the better ones. And the reason `output: 'standalone'` broke
the Vercel build is recorded as unestablished rather than explained by a
mechanism that does not hold.

The positive fact is written down beside the glob it explains, because
reading `next/dist` alone leads to the wrong conclusion twice.

Author: jouwdan

docs/development.md

@@ -155,10 +155,11 @@ tree**, right after `next build` finishes. `next.config.mjs` sets
 `output: 'standalone'` everywhere the board has to serve itself — which is
 everywhere except Vercel, where Vercel packages the build into its own
 functions and never runs `forum-web start`. Asking for standalone there
-breaks the build outright: standalone makes Vercel's builder read
-`.next/next-server.js.nft.json`, and Next skips the tracing that writes it
-whenever the bundler is Turbopack, which is the default for `next build` in
-Next 16. Next's own standalone output deliberately
+breaks the build outright: standalone makes Vercel's builder look for
+`.next/next-server.js.nft.json`, and on that deployment it was not there.
+Why it was missing was never established — a Turbopack build does write
+that file, as the tracing note below records — so treat the mechanism as
+open and the failure as observed. Next's own standalone output deliberately
 excludes both directories — they have to be copied in alongside the traced
 `server.js` for it to serve `/_next/static/*` and anything under `public/`
 (Next's bundled docs, under `node_modules/next/dist/docs`, say so under
@@ -214,6 +215,18 @@ worst place to learn it. The check reads both configs that carry the literal
 carrying one at all. The second, unversioned glob beside it covers the hoisted
 layout npm installs, where no `.pnpm` directory exists for the first to match.
 
+**`outputFileTracingIncludes` is applied by Turbopack itself**, which is worth
+stating because the option is handled in `next/dist` only by
+`collectBuildTraces`, and `next build` skips that function entirely when the
+bundler is Turbopack — reading only that far suggests the glob above is dead
+code, and it is not. Turbopack emits the `.nft.json` files and applies the
+include globs on its own side. Measured on a Turbopack build of this app:
+`next-server.js.nft.json`, which the `'/**'` key does not cover, lists three
+`@swc/helpers` entries and none under `esm/`; a route's `.nft.json`, which it
+does cover, lists over a thousand including 324 under `esm/` and the package's
+`LICENSE` — a file no tracer would follow. Delete the glob on the theory that
+nothing reads it and self-hosted boards go back to failing at request time.
+
 **This assumes a hoisted `node_modules`** — npm, yarn classic, or pnpm with
 `node-linker=hoisted` (`create-meith`'s own scaffold uses npm). The
 materialized app's source imports every `@meith/*` package it needs by bare

docs/vercel.md

@@ -361,12 +361,11 @@ then come back for the four things specific to this route:
   contend for the same migration lock, and the function timeout bounds how
   long a migration is allowed to take. The step reads the table names out
   of the schema definitions, which are ordinary imported code, because the
-  migration `.sql` files are not in the function at all: nothing imports
-  them, so nothing traces them in, and `outputFileTracingIncludes` cannot
-  put them back while `next build` defaults to Turbopack, for which Next
-  skips trace collection entirely. If that step does report missing tables,
-  run `community migrate` against the same database and reload — do not
-  reach for `MIGRATIONS_DIR`, which cannot help when the files are absent.
+  migration `.sql` files are not in the function: nothing imports them, so
+  nothing traces them in, and nothing lists them in
+  `outputFileTracingIncludes` either. If that step does report missing
+  tables, run `community migrate` against the same database and reload —
+  `MIGRATIONS_DIR` cannot help when the files are absent.
 - **The installer takes the same session-level advisory lock migrations
   do**, so it needs `DIRECT_DATABASE_URL` for the same reason. Run against
   a pooler, it can report itself permanently in flight.