fix(icon): bundle docs navigation icons to prevent client-nav flash

Docs nav icons render in @nuxt/icon CSS mode. On initial load their mask CSS
is inlined via SSR, but on client-side navigation the icon data isn't in the
client bundle, so it's fetched from the iconify API and the rule is injected
after paint — a visible flash.

The icons used only by the remote nuxt/nuxt docs nav (md frontmatter
`navigation.icon` + `.navigation.yml`) can't be collected automatically:
- the scanner skips the `.data` dot-dir (remote docs), and
- @nuxt/content restores its cache on CI (0 files parsed), so parse hooks and
  raw-file globbing both come up empty at build time.

Inline just those remote-only icons (validated against the installed
@iconify-json packages). Local content (deploy, blog, …) and app icons stay
covered by `scan`; widen its glob to include `.ts` and `**/.*.{yml,yaml}`
so app config and local `.navigation.yml` dotfiles are picked up too.

Verified: client bundle 215 -> 262 icons (143.57KB, under the 256KB limit),
including all folder-type/file-type docs nav icons; local icons (azure, blog
nav) confirmed still bundled via the scanner.

Author: benjamincanac

nuxt.config.ts

@@ -553,8 +553,36 @@ export default defineNuxtConfig({
       dir: resolve('./app/assets/icons')
     }],
     clientBundle: {
-      scan: true,
-      includeCustomCollections: true
+      // Scan app source + all local content for icons. The `**/.*.{yml,yaml}`
+      // pattern is needed for local `.navigation.yml` dotfiles (e.g. blog,
+      // enterprise), which `*.yml` skips under `dot:false`.
+      scan: {
+        globInclude: ['**/*.{vue,jsx,tsx,md,mdc,mdx,yml,yaml,ts}', '**/.*.{yml,yaml}']
+      },
+      includeCustomCollections: true,
+      // Icons used ONLY by the remote docs navigation (md frontmatter
+      // `navigation.icon` + `.navigation.yml`), collected across all three served
+      // versions (nuxt/nuxt `3.x`, `4.x`, `main`). The scanner can't reach these:
+      // remote docs are cloned under the `.data` dot-dir and restored from
+      // @nuxt/content's cache on CI (0 files parsed), so neither file scanning nor
+      // parse hooks see them at build. Without bundling they're fetched at runtime
+      // and flash in on client-side navigation. Local content (deploy, blog, …) is
+      // already covered by `scan` above, so it's intentionally NOT here.
+      // Regenerate when nuxt/nuxt docs add icons (see PR #2288 for the snippet).
+      icons: [
+        'logos:bun', 'lucide:alert-triangle', 'lucide:arrow-left-right', 'lucide:bell-dot',
+        'lucide:bug-off', 'lucide:cable', 'lucide:cog', 'lucide:cooking-pot',
+        'lucide:map', 'lucide:panels-top-left', 'lucide:play', 'lucide:ship',
+        'lucide:square-check', 'lucide:square-terminal', 'lucide:test-tube', 'lucide:toggle-right',
+        'simple-icons:codesandbox', 'simple-icons:git', 'simple-icons:google', 'simple-icons:googlechrome',
+        'simple-icons:mdnwebdocs', 'simple-icons:vite', 'simple-icons:w3c', 'simple-icons:webpack',
+        'vscode-icons:default-folder', 'vscode-icons:file-type-dotenv', 'vscode-icons:file-type-git', 'vscode-icons:file-type-light-config',
+        'vscode-icons:file-type-npm', 'vscode-icons:file-type-nuxt', 'vscode-icons:file-type-tsconfig', 'vscode-icons:file-type-vue',
+        'vscode-icons:folder-type-app', 'vscode-icons:folder-type-asset', 'vscode-icons:folder-type-component', 'vscode-icons:folder-type-log',
+        'vscode-icons:folder-type-middleware', 'vscode-icons:folder-type-node', 'vscode-icons:folder-type-nuxt', 'vscode-icons:folder-type-package',
+        'vscode-icons:folder-type-plugin', 'vscode-icons:folder-type-public', 'vscode-icons:folder-type-server', 'vscode-icons:folder-type-shared',
+        'vscode-icons:folder-type-src', 'vscode-icons:folder-type-temp', 'vscode-icons:folder-type-tools', 'vscode-icons:folder-type-view'
+      ]
     }
   },
   image: {