docs: describe export default and export = forwards and type-only test imports

cli/audit.mdx

@@ -854,7 +854,7 @@ The object has these keys:
 
 Treat `reach` as an open set: a later version can add a class. Read an unknown value as "needs attention". The section is advisory and never changes the verdict or the exit code. The human brief prints the counts and the first three rows.
 
-Some limits apply. A change inside a non-exported helper is not attributed to the exports that call it. An automock without a factory (`vi.mock('./x')`) counts as reach. Code that only a setup file imports, and pages that only end-to-end tests visit, get `none-file`.
+Some limits apply. A change inside a non-exported helper is not attributed to the exports that call it. An automock without a factory (`vi.mock('./x')`) counts as reach. Code that only a setup file imports, and pages that only end-to-end tests visit, get `none-file`. A test that imports a file only with `import type` does not load the file, so that file also gets `none-file`.
 
 ### Agent walkthrough loop
 

cli/dead-code.mdx

@@ -198,7 +198,7 @@ The `reason` values are:
 - `re-export-alias`: a barrel re-exports the export under another name, and the consumer imports that name.
 - `namespace-use`: the consumer imports the whole namespace (`import * as ns`) and does not name the export.
 - `dynamic-import`: the consumer loads the module with `import()` and does not name the export.
-- `pass-through`: the consumer only forwards the export and does not use it. The consumer is a barrel (`export * from`, `export { foo } from`), or a file that imports the export and only exports it again (`import { foo } from './x'; export { foo }`, `import bar from './x'; export { bar }`, or a renamed re-export such as `import { foo as baz } from './x'; export { baz }`). A file that forwards with `export default bar` or `export = bar` stays a consumer, because the dependency graph does not follow that form to the files behind it.
+- `pass-through`: the consumer only forwards the export and does not use it. The consumer is a barrel (`export * from`, `export { foo } from`), or a file that imports the export and only exports it again (`import { foo } from './x'; export { foo }`, `import bar from './x'; export { bar }`, `import bar from './x'; export default bar`, `import bar from './x'; export = bar`, or a renamed re-export such as `import { foo as baz } from './x'; export { baz }`). The importers of the forwarding file show in the trace.
 
 A pass-through consumer is `found`, and it is never a gap. A change of the export needs no edit there. Fallow checks the files that import through it on their own. A file that also uses the binding in another place stays a normal consumer. A `.vue`, `.svelte`, `.astro`, or `.mdx` file that imports the export also stays a normal consumer, because a template can use the binding.
 

public-content-manifest.json

@@ -7,7 +7,7 @@
     "visibility": "public-only"
   },
   "content": {
-    "sha256": "1a8dacd50494702de55ad0604a761f722c93a5e8840a4931475047bbe8967c98",
+    "sha256": "72b6c63a487d120069a227f4991568dbea2f54c3d01e1cb948d10db450658467",
     "files": [
       {
         "path": "adoption.mdx",
@@ -91,8 +91,8 @@
       },
       {
         "path": "cli/audit.mdx",
-        "bytes": 72227,
-        "sha256": "45439941ad0c3b56a06bb7bf0d1d0cd125cb330da059451ec52f0b2dda179706"
+        "bytes": 72338,
+        "sha256": "fea5c54f4aca21c11c91e6aa5929551171aec8bff14a638afe98791e0afd0807"
       },
       {
         "path": "cli/baselines.mdx",
@@ -111,8 +111,8 @@
       },
       {
         "path": "cli/dead-code.mdx",
-        "bytes": 40564,
-        "sha256": "7ec51a0dc82a2b04003475165b83bce01a94944fc14f20b8e22f8d8f5063c191"
+        "bytes": 40542,
+        "sha256": "504e4446be73deff7d761a533dd9d160034e5ed2d58c0500b2698aca624a43d6"
       },
       {
         "path": "cli/decision-surface.mdx",