The on-demand PDF generation routes were failing on Vercel because the runtime environment could not locate the browser binary packed by @sparticuz/chromium. Since the package's internal path resolution wasn't detectable by @vercel/nft, we've updated next.config.ts to explicitly include the package in the output file tracing. This ensures the necessary binary is correctly bundled and available at runtime.