Remove automatic linting from build (#83136)

### What?
This PR removes the automatic ESLint linting that previously ran during `next build`. The documentation has been updated to reflect this change.

### Why?
As part of Next.js 16, we're removing the automatic build-time linting that was previously included in the build process. This gives developers more control over when linting runs by explicitly invoking their linter via npm scripts.

### How?
- Updated documentation to clarify that automatic build-time linting has been removed in Next.js 16
- Removed the `runLint` parameter and related linting code from the build process
- Removed the `verifyAndLint.ts` file which is no longer needed
- Simplified type checking code by removing lint-related functionality
- Removed ESLint telemetry during builds

Author: bgub

docs/01-app/01-getting-started/01-installation.mdx

@@ -346,7 +346,7 @@ npx @next/codemod@canary next-lint-to-eslint-cli .
 
 If you use ESLint, create an explicit config (recommended `eslint.config.mjs`). ESLint supports both [the legacy `.eslintrc.*` and the newer `eslint.config.mjs` formats](https://eslint.org/docs/latest/use/configure/configuration-files#configuring-eslint). See the [ESLint API reference](/docs/app/api-reference/config/eslint#with-core-web-vitals) for a recommended setup.
 
-> **Good to know**: If an ESLint config is present, `next build` will still run linting in Next.js 15, but this automatic build-time linting will be removed in Next.js 16. Control when linting runs by invoking your linter via npm scripts.
+> **Good to know**: Prior to Next.js 16, `next build` ran linting automatically. Now, this automatic build-time linting has been removed. Control when linting runs by invoking your linter via npm scripts.
 
 See the [ESLint Plugin](/docs/app/api-reference/config/next-config-js/eslint) page for more information.
 

docs/01-app/02-guides/memory-usage.mdx

@@ -94,18 +94,13 @@ export default nextConfig
 
 ## Disable static analysis
 
-Typechecking and linting may require a lot of memory, especially in large projects.
+Typechecking may require a lot of memory, especially in large projects.
 However, most projects have a dedicated CI runner that already handles these tasks.
-When the build produces out-of-memory issues during the "Linting and checking validity of types" step, you can disable these task during builds:
+When the build produces out-of-memory issues during the "Running TypeScript" step, you can disable this task during builds:
 
 ```js filename="next.config.mjs"
 /** @type {import('next').NextConfig} */
 const nextConfig = {
-  eslint: {
-    // Warning: This allows production builds to successfully complete even if
-    // your project has ESLint errors.
-    ignoreDuringBuilds: true,
-  },
   typescript: {
     // !! WARN !!
     // Dangerously allow production builds to successfully complete even if
@@ -119,9 +114,8 @@ export default nextConfig
 ```
 
 - [Ignoring TypeScript Errors](/docs/app/api-reference/config/typescript#disabling-typescript-errors-in-production)
-- [ESLint in Next.js config](/docs/pages/api-reference/config/next-config-js/eslint)
 
-Keep in mind that this may produce faulty deploys due to type errors or linting issues.
+Keep in mind that this may produce faulty deploys due to type errors.
 We strongly recommend only promoting builds to production after static analysis has completed.
 If you deploy to Vercel, you can check out the [guide for staging deployments](https://vercel.com/docs/deployments/managing-deployments#staging-and-promoting-a-production-deployment) to learn how to promote builds to production after custom tasks have succeeded.
 

docs/01-app/03-api-reference/05-config/03-eslint.mdx

@@ -230,36 +230,6 @@ module.exports = {
 }
 ```
 
-## Disabling linting during production builds
-
-If you do not want ESLint to run during `next build`, you can set the `eslint.ignoreDuringBuilds` option in `next.config.js` to `true`:
-
-```ts filename="next.config.ts" switcher
-import type { NextConfig } from 'next'
-
-const nextConfig: NextConfig = {
-  eslint: {
-    // Warning: This allows production builds to successfully complete even if
-    // your project has ESLint errors.
-    ignoreDuringBuilds: true,
-  },
-}
-
-export default nextConfig
-```
-
-```js filename="next.config.js" switcher
-const nextConfig = {
-  eslint: {
-    // Warning: This allows production builds to successfully complete even if
-    // your project has ESLint errors.
-    ignoreDuringBuilds: true,
-  },
-}
-
-export default nextConfig
-```
-
 ### Migrating existing config
 
 If you already have ESLint configured in your application, we recommend extending from this plugin directly instead of including `eslint-config-next` unless a few conditions are met.

examples/active-class-name/package.json

@@ -4,7 +4,7 @@
     "dev": "next dev",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint"
+    "lint": "eslint ."
   },
   "dependencies": {
     "next": "latest",

examples/cms-buttercms/package.json

@@ -4,7 +4,7 @@
     "dev": "next dev",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint"
+    "lint": "eslint ."
   },
   "dependencies": {
     "@popperjs/core": "^2.10.2",

examples/cms-sanity/package.json

@@ -6,7 +6,7 @@
     "prebuild": "npm run typegen",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint",
+    "lint": "eslint .",
     "presetup": "echo 'about to setup env variables, follow the guide here: https://github.com/vercel/next.js/tree/canary/examples/cms-sanity#using-the-sanity-cli'",
     "setup": "npx sanity@latest init --env .env.local",
     "postsetup": "echo 'create the read token by following the rest of the guide: https://github.com/vercel/next.js/tree/canary/examples/cms-sanity#creating-a-read-token'",

examples/cms-wordpress/package.json

@@ -4,7 +4,7 @@
     "dev": "graphql-codegen --config codegen.ts && node ./add-ts-nocheck.js && next dev",
     "build": "graphql-codegen --config codegen.ts && node ./add-ts-nocheck.js && next build",
     "start": "next start",
-    "lint": "next lint",
+    "lint": "eslint .",
     "codegen": "graphql-codegen --config codegen.ts && node ./add-ts-nocheck.js"
   },
   "dependencies": {

examples/panda-css/package.json

@@ -5,7 +5,7 @@
     "dev": "next dev",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint"
+    "lint": "eslint ."
   },
   "dependencies": {
     "next": "latest",

examples/prisma-postgres/package.json

@@ -4,7 +4,7 @@
     "dev": "next dev --turbopack",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint",
+    "lint": "eslint .",
     "postinstall": "prisma generate --no-engine"
   },
   "prisma": {

examples/with-apollo/package.json

@@ -4,7 +4,7 @@
     "dev": "next dev",
     "build": "next build",
     "start": "next start",
-    "lint": "next lint"
+    "lint": "eslint ."
   },
   "dependencies": {
     "@apollo/client": "^3.10.1",