diff --git a/AGENTS.md b/AGENTS.md
index ddb33dcd9..fce6c1146 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -2,51 +2,45 @@
 
 ## Build Commands
 
--   **Type Check**: `npx tsc --noEmit`
--   **Build**: `npm run build`
--   **Dev**: `npm run dev`
--   **Lint**: `npm run lint`
--   **Checks**: `npm run check` runs every `dev/check-*.mjs` (links, filenames, images); `npm run build` runs them first, so any finding fails a deploy
--   **Check links**: `npm run check -- links --check-anchors --check-self-links` (CI comments on PRs that break links; see `dev/check-links.mjs`; the build runs it without flags, so only dead page links fail a deploy). When moving a page or renaming a heading, update every link to it; a redirect in `src/data/redirects.ts` does not satisfy the check. Link to this site with relative paths (`/admin/config/site-config`), never `https://sourcegraph.com/docs/…` or `https://docs.sourcegraph.com/…`. To also probe the external links you added: `npm run check -- links --check-anchors --check-self-links --check-external --diff <(git diff -U0 origin/main)`
--   **Prove changed links resolve on a deploy**: `node dev/verify-links-live.mjs --site <vercel-preview-url>` prints a Markdown table for the PR description
--   **Vercel build failures**: Vercel shows build logs only to its team members, so `.github/workflows/vercel-build-report.yml` attaches the log to the Vercel Slack app's "failed to deploy" post in `#alerts-vercel-doc-site` and comments a link to it on the PR (see `dev/report-vercel-build.mjs`). The log itself never goes on the PR, since the repository is public. It reads Vercel with the `VERCEL_TOKEN` repo secret, a token scoped to the `sourcegraph-docs` project that expires 2026-12-10; mint a new one with `POST /v3/user/tokens?teamId=<team>` and `projectId` in the body. Slack needs the `SLACK_BOT_TOKEN` repo secret and `SLACK_CHANNEL_ID` repo variable. The bot is the Slack app in `dev/slack-app-vercel-build-report.json`; to recreate it, paste that manifest at <https://api.slack.com/apps?new_app=1> (From a manifest), install it, copy its Bot User OAuth Token into the secret, and `/invite @Vercel build log` to the channel
-
-## AI Chat Integration
-
-This site uses **runLLM** for the AI chat widget. The integration is implemented via:
-
--   **Location**: `src/app/layout.tsx`
--   **Widget**: runLLM script loaded via Next.js `<Script>` component
--   **Configuration**:
-    -   Position: BOTTOM_RIGHT
-    -   Theme color: #FF5543 (Sourcegraph brand color)
-    -   Button text: "Ask AI"
-    -   Keyboard shortcut: Mod+j
-
-### runLLM Configuration
-
-To update the runLLM assistant ID or other settings, modify the Script component in `src/app/layout.tsx`:
-
-```tsx
-<Script
-	id="runllm-widget-script"
-	type="module"
-	src="https://widget.runllm.com"
-	crossOrigin=""
-	runllm-keyboard-shortcut="Mod+j"
-	runllm-name="Sourcegraph AI Assistant"
-	runllm-position="BOTTOM_RIGHT"
-	runllm-assistant-id="YOUR_ASSISTANT_ID" // Update this
-	runllm-theme-color="#FF5543"
-	runllm-floating-button-text="Ask AI"
-	async
-/>
+- **Type Check**: `npx tsc --noEmit`
+- **Build**: `npm run build`
+- **Dev**: `npm run dev`
+- **Lint**: `npm run lint`
+- **Checks**: `npm run check` runs every `dev/check-*.mjs` (links, filenames,
+  images); `npm run build` runs them first, so any finding fails a deploy
+- **Prove changed links resolve on a deploy**:
+  `node dev/verify-links-live.mjs --site <vercel-preview-url>` prints a
+  Markdown table for the PR description
+
+### Links
+
+- `npm run check -- links --check-anchors --check-self-links`. CI comments on
+  PRs that break links; see `dev/check-links.mjs`. The build runs it without
+  flags, so only dead page links fail a deploy.
+- When moving a page or renaming a heading, update every link to it; a
+  redirect in `src/data/redirects.ts` does not satisfy the check.
+- Link to this site with relative paths (`/admin/config/site-config`), never
+  `https://sourcegraph.com/docs/…` or `https://docs.sourcegraph.com/…`.
+- To also probe the external links you added:
+
+```sh
+npm run check -- links --check-anchors --check-self-links \
+  --check-external --diff <(git diff -U0 origin/main)
 ```
 
-The previous **Langbase** / `baseai` chatbot integration has been fully removed (packages, components, API routes, `baseai/` memory config, and the `pnpm sync` script).
-
-## Important Notes
-
--   **Assistant ID**: The `runllm-assistant-id` is currently set to "YOUR_ASSISTANT_ID" and needs to be updated with the actual Sourcegraph runLLM assistant ID
--   **Deployment**: After updating the assistant ID, add the deployment URL to the runLLM dashboard
--   **Styling**: The widget inherits the site's theme and uses the Sourcegraph brand color (#FF5543)
+### Vercel build failures
+
+- Vercel shows build logs only to its team members, so
+  `.github/workflows/vercel-build-report.yml` attaches the log to the Vercel
+  Slack app's "failed to deploy" post in `#alerts-vercel-doc-site` and comments
+  a link to it on the PR (see `dev/report-vercel-build.mjs`). The log itself
+  never goes on the PR, since the repository is public.
+- It reads Vercel with the `VERCEL_TOKEN` repo secret, a token scoped to the
+  `sourcegraph-docs` project that expires 2026-12-10; mint a new one with
+  `POST /v3/user/tokens?teamId=<team>` and `projectId` in the body.
+- Slack needs the `SLACK_BOT_TOKEN` repo secret and `SLACK_CHANNEL_ID` repo
+  variable. The bot is the Slack app in `dev/slack-app-vercel-build-report.json`;
+  to recreate it, paste that manifest at
+  <https://api.slack.com/apps?new_app=1> (From a manifest), install it, copy its
+  Bot User OAuth Token into the secret, and `/invite @Vercel build log` to the
+  channel.
diff --git a/README.md b/README.md
index 3f050ff44..fc36c3f5c 100644
--- a/README.md
+++ b/README.md
@@ -1,42 +1,53 @@
 # Sourcegraph Docs
 
 > [!IMPORTANT]
-> For support, please reach out to your account team or contact [support@sourcegraph.com](mailto:support@sourcegraph.com)
+> For support, please reach out to your account team or contact
+> [support@sourcegraph.com](mailto:support@sourcegraph.com)
 
-Welcome to the Sourcegraph documentation! We're excited to have you contribute to our docs. Our docs tech stack is powered by Next.js, TailwindCSS and deployed on Vercel. This guide will walk you through the process of contributing to our documentation.
+Welcome to the Sourcegraph documentation! We're excited to have you contribute
+to our docs. Our docs tech stack is powered by Next.js, TailwindCSS and deployed
+on Vercel. This guide will walk you through the process of contributing to our
+documentation.
 
 ## Get started
 
-To get started with this template, clone this repository to your local machine using the following command:
+To get started with this template, clone this repository to your local machine
+using the following command:
 
 ```sh
 git clone https://github.com/sourcegraph/docs.git docs
 ```
 
-Navigate to the project directory by typing the following command in your terminal:
+Navigate to the project directory by typing the following command in your
+terminal:
 
 ```sh
 cd docs
 ```
 
-Before the dependencies are installed make sure your local machine has the following versions of `node` and `pnpm` installed:
+Before the dependencies are installed make sure your local machine has the
+following versions of `node` and `pnpm` installed:
 
--   node: `v24.21.0`
--   pnpm: `10.25.0`
+- node: `v24.21.0`
+- pnpm: `10.25.0`
 
-**Note**: If you have `mise` available you can install the above versions for only this repository by running the following command from your terminal in the root folder:
+**Note**: If you have `mise` available you can install the above versions for
+only this repository by running the following command from your terminal in the
+root folder:
 
 ```sh
 mise install
 ```
 
-Now that the base requirements of the project have been satisfied, we can install the required dependencies to run the development server!
+Now that the base requirements of the project have been satisfied, we can
+install the required dependencies to run the development server!
 
 ```sh
 pnpm install
 ```
 
-Spell checking is not part of the project dependencies. To run it locally: `npx cspell@10 --no-progress --dot '**/*'`
+Spell checking is not part of the project dependencies. To run it locally:
+`npx cspell@10 --no-progress --dot '**/*'`
 
 Next, run the development server:
 
@@ -44,13 +55,16 @@ Next, run the development server:
 pnpm run dev
 ```
 
-Finally, open [`http://localhost:3000`](http://localhost:3000) in your browser to view the website.
+Finally, open [`http://localhost:3000`](http://localhost:3000) in your browser
+to view the website.
 
 ## Writing and contributing to Sourcegraph Docs
 
 ### (Easy) Using GitHub to edit existing files
 
-You can easily update existing docs pages using [GitHub's file editor](https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files). All you need to do is:
+You can easily update existing docs pages using
+[GitHub's file editor](https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files).
+All you need to do is:
 
 1. Find the corresponding `.mdx` file in the [folder structure](#folder-structure).
 2. Click the pencil icon to open the file editor.
@@ -59,12 +73,17 @@ You can easily update existing docs pages using [GitHub's file editor](https://d
 5. Provide a Commit message and an Extended description.
 6. Click on the green "Propose changes" button to create a PR.
 7. Add a PR reviewer to the Reviewers panel by clicking on the gear icon.
-8. Tag `@maedahbatool` in the `#docs` Slack channel and link to your PR to get a quick review.
-    > NOTE: "Edit from GitHub" is generally recommended for text-based edits. For more structural-based contributions like adding React components and code blocks, it's always better to go with a local setup. This way, you can preview changes before you commit.
+8. Tag `@maedahbatool` in the `#docs` Slack channel and link to your PR to get
+   a quick review.
+    > NOTE: "Edit from GitHub" is generally recommended for text-based edits.
+    > For more structural-based contributions like adding React components and
+    > code blocks, it's always better to go with a local setup. This way, you
+    > can preview changes before you commit.
 
 ### (Advanced) Local dev environment
 
-To add new or update existing docs content. Create a new branch and checkout by via:
+To add new or update existing docs content. Create a new branch and checkout by
+via:
 
 ```sh
 git switch -c BRANCH_NAME_HERE
@@ -72,20 +91,24 @@ git switch -c BRANCH_NAME_HERE
 
 ### Folder structure
 
-The folder structure is exactly the same here. All the docs reside within the `/docs` folder. Here you'll find separate folders for every docs section like `cody`, `code-search`, `cli`, etc.
+The folder structure is exactly the same here. All the docs reside within the
+`/docs` folder. Here you'll find separate folders for every docs section like
+`cody`, `code-search`, `cli`, etc.
 
--   Navigate to the relevant relevant section for your contribution
--   If you're adding a new page, create a new MDX file (e.g., `my-new-page.mdx`) in the appropriate folder
+- Navigate to the relevant section for your contribution
+- If you're adding a new page, create a new MDX file (e.g., `my-new-page.mdx`)
+  in the appropriate folder
 
 ### Frontmatter
 
-Each MDX file can include frontmatter at the top of the file to configure page metadata. Here are the supported fields:
+Each MDX file can include frontmatter at the top of the file to configure page
+metadata. Here are the supported fields:
 
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `title` | string | No | The page title |
-| `date` | date | No | Last modified date (used in sitemap) |
-| `seoPriority` | number | No | SEO priority for sitemap (0.0 to 1.0, default: 0.5) |
+| Field         | Type   | Required | Description                           |
+| ------------- | ------ | -------- | ------------------------------------- |
+| `title`       | string | No       | The page title                        |
+| `date`        | date   | No       | Last modified date (used in sitemap)  |
+| `seoPriority` | number | No       | Sitemap priority 0.0–1.0, default 0.5 |
 
 Example:
 
@@ -99,10 +122,11 @@ seoPriority: 0.8
 
 ### Using MDX
 
-We use MDX for our documentation, which allows you to seamlessly integrate JSX (React components) within Markdown. Write your content using standard markdown syntax. For example,
-
-```
+We use MDX for our documentation, which allows you to seamlessly integrate JSX
+(React components) within Markdown. Write your content using standard markdown
+syntax. For example,
 
+```md
 # This is heading 1
 
 This is an introductory paragraph.
@@ -122,11 +146,15 @@ This is how you add a [demo-link](https://sourcegraph.com/)
 
 ### Including React Components
 
-The only difference with this new stack is its ability to use React components. We have a set of reusable React components located in the `src/components` directory. These components are designed to enhance the user experience and maintain consistency across our documentation.
+The only difference with this new stack is its ability to use React components.
+We have a set of reusable React components located in the `src/components`
+directory. These components are designed to enhance the user experience and
+maintain consistency across our documentation.
 
-For example the cards layout appears by using the `<Callout>` component that can add `note`, `info`, or `warning` notices in docs.
+For example the cards layout appears by using the `<Callout>` component that
+can add `note`, `info`, or `warning` notices in docs.
 
-![](https://storage.googleapis.com/sourcegraph-assets/Docs/CleanShot%202023-12-12%20at%2012.00.29%402x.png)
+![Callout components rendered in the docs](https://storage.googleapis.com/sourcegraph-assets/Docs/CleanShot%202023-12-12%20at%2012.00.29%402x.png)
 
 You can use this component within your content as follows:
 
@@ -134,54 +162,72 @@ You can use this component within your content as follows:
 <Callout type="note">This feature is currently in Beta for all users.</Callout>
 ```
 
-This snippet creates a single `<QuickLink>` titled as "Get Cody". You can add as many cards you want while filling out all the relevant details.
+This snippet creates a single `<QuickLink>` titled as "Get Cody". You can add
+as many cards you want while filling out all the relevant details.
 
 Here are the list of all the supported components we have:
 
--   `<QuickLinks>`
--   `<ProductLinks>`
--   `<LinkCards>`
--   `<Callout>`
+- `<QuickLinks>`
+- `<ProductLinks>`
+- `<LinkCards>`
+- `<Callout>`
 
-For a better docs experience, we'll continue adding more components in the future.
+For a better docs experience, we'll continue adding more components in the
+future.
 
 ### Adding a link
 
-To add a `link` to any docs page, use the following routing syntax: `[Link text](path-to-link)`.
+To add a `link` to any docs page, use the following routing syntax:
+`[Link text](path-to-link)`.
 
--   Do not include `/docs` in the link paths. The base URL will be `sourcegraph.com/docs`
--   There should be **no file extension** in the path name
+- Do not include `/docs` in the link paths. The base URL will be
+  `sourcegraph.com/docs`
+- There should be **no file extension** in the path name
 
-For example, if you want to link to the Cody Quickstart somewhere in the Code Search docs, you should use:
+For example, if you want to link to the Cody Quickstart somewhere in the Code
+Search docs, you should use:
 
 ```markdown
--   This is a link to [Cody Quickstart](/cody/quickstart) in Code Search docs
--   This is a way to hash-link to [Cody for VSCode installation](/cody/clients/install-vscode#verifying-the-installation) in Code Search docs
+- Link to the [Cody Quickstart](/cody/quickstart)
+- Hash-link to a heading:
+  [Verify the install](/cody/clients/install-vscode#verifying-the-installation)
 ```
 
 ### Adding media assets (images, videos and gifs)
 
-You can upload images, videos and gifs to Sourcegraph docs. For a more detailed instructions visit [this page](https://www.notion.so/sourcegraph/How-to-host-blog-assets-using-GCP-file-storage-a2cae02bd0c74166a12eaff5062c41ad).
+You can upload images, videos and gifs to Sourcegraph docs. For a more detailed
+instructions visit
+[this page](https://www.notion.so/sourcegraph/How-to-host-blog-assets-using-GCP-file-storage-a2cae02bd0c74166a12eaff5062c41ad).
 
-> Note: Make sure to use [ImageOptim.app](https://imageoptim.com/mac) to reduce the size of the images before uploading, since large images degrade page loading speed.
+> Note: Make sure to use [ImageOptim.app](https://imageoptim.com/mac) to reduce
+> the size of the images before uploading, since large images degrade page
+> loading speed.
 
 ## Previewing Changes
 
 ### Locally
 
-As you make changes to the documentation, the development server will automatically update. Review your changes by navigating to `http://localhost:3000` in your browser.
+As you make changes to the documentation, the development server will
+automatically update. Review your changes by navigating to
+`http://localhost:3000` in your browser.
 
 ### Previewing Vercel Deployments
 
-When you open a PR Vercel deploys and provides you with a preview deployment link. To view your deployment, click the **Visit Preview** link from Vercel's deployment panel in your PRs and you get a preview of your docs
+When you open a PR Vercel deploys and provides you with a preview deployment
+link. To view your deployment, click the **Visit Preview** link from Vercel's
+deployment panel in your PRs and you get a preview of your docs
 
-![CleanShot 2024-11-05 at 10 11 29@2x](https://github.com/user-attachments/assets/b0911e2e-95a7-4f56-b2ff-b659d13077d8)
+![Vercel deployment panel on a PR](https://github.com/user-attachments/assets/b0911e2e-95a7-4f56-b2ff-b659d13077d8)
 
 ## Submitting your Contribution
 
 Once you're satisfied with your changes, follow these steps:
 
--   Commit your changes
--   Create a pull request to the [Sourcegraph documentation repository](https://github.com/sourcegraph/docs), and tag the appropriate reviewers.
+- Commit your changes
+- Create a pull request to the
+  [Sourcegraph documentation repository](https://github.com/sourcegraph/docs),
+  and tag the appropriate reviewers.
 
-Thank you for contributing to Sourcegraph documentation! Your efforts help us provide top-notch learning experiences for our users. If you have any questions or need assistance, feel free to reach out.
+Thank you for contributing to Sourcegraph documentation! Your efforts help us
+provide top-notch learning experiences for our users. If you have any questions
+or need assistance, feel free to reach out.
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index f8c2c31ab..990381a3f 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -1914,8 +1914,8 @@ packages:
     resolution: {integrity: sha512-BLrgEcRTwX2o6gGxGOCNyMvGSp35YofuYzw9h1IMTRmKqttAZZVU67bdb9Pr2vUHA8+j3i2tJfjO6C6+4myGTA==}
     engines: {node: 18 || 20 || >=22}
 
-  baseline-browser-mapping@2.11.21:
-    resolution: {integrity: sha512-uh8vpY/1/YyFkunIDFH/12p7/7VdPKA1hejMVEbdkEaWnUz0Hesvx5EbiU6XxjyHZIOju+ZMbQJkRh+es3/spQ==}
+  baseline-browser-mapping@2.11.22:
+    resolution: {integrity: sha512-pWc4w51fBFd7mav43/zKRC+RI6f4yfzQoVlfvE8dECePyfkn1bzLp01Fj0QACcyCZyFhiEMyD2qScfKRWgWibA==}
     engines: {node: '>=6.0.0'}
     hasBin: true
 
@@ -1983,9 +1983,6 @@ packages:
     resolution: {integrity: sha512-DLIsRzJVBQu72meAKPkWQOLcujdXT32hwdfnkI1frSiSRMK1MofjKHf+MEx0SB6fjEFXL8fBDv1dKymBlOp4Qw==}
     engines: {node: '>=0.10.0'}
 
-  caniuse-lite@1.0.30001769:
-    resolution: {integrity: sha512-BCfFL1sHijQlBGWBMuJyhZUhzo7wer5sVj9hqekB/7xn0Ypy+pER/edCYQm4exbXj4WiySGp40P8UuTh6w1srg==}
-
   caniuse-lite@1.0.30001810:
     resolution: {integrity: sha512-TITQPUkaz+aVk5GL6NhOdwk1aEaNTSDPsGFWrTuhKGtjTF70jL/Oht2W4c6rXUe5fu7Ie19VIahAXHIIiWWNeg==}
 
@@ -6384,7 +6381,7 @@ snapshots:
   autoprefixer@10.4.24(postcss@8.5.28):
     dependencies:
       browserslist: 4.28.9
-      caniuse-lite: 1.0.30001769
+      caniuse-lite: 1.0.30001810
       fraction.js: 5.3.4
       picocolors: 1.1.1
       postcss: 8.5.28
@@ -6404,7 +6401,7 @@ snapshots:
 
   balanced-match@4.0.4: {}
 
-  baseline-browser-mapping@2.11.21: {}
+  baseline-browser-mapping@2.11.22: {}
 
   big.js@5.2.2: {}
 
@@ -6429,7 +6426,7 @@ snapshots:
 
   browserslist@4.28.9:
     dependencies:
-      baseline-browser-mapping: 2.11.21
+      baseline-browser-mapping: 2.11.22
       caniuse-lite: 1.0.30001810
       electron-to-chromium: 1.5.425
       node-releases: 2.0.55
@@ -6474,8 +6471,6 @@ snapshots:
 
   camelcase@2.1.1: {}
 
-  caniuse-lite@1.0.30001769: {}
-
   caniuse-lite@1.0.30001810: {}
 
   ccount@2.0.1: {}
@@ -8580,7 +8575,7 @@ snapshots:
       '@next/env': 14.2.35
       '@swc/helpers': 0.5.5
       busboy: 1.6.0
-      caniuse-lite: 1.0.30001769
+      caniuse-lite: 1.0.30001810
       graceful-fs: 4.2.11
       postcss: 8.4.31
       react: 18.3.1
diff --git a/src/app/api/og/[...path]/route.tsx b/src/app/api/og/[...path]/route.tsx
index da9dbd2ee..701cd9c2d 100644
--- a/src/app/api/og/[...path]/route.tsx
+++ b/src/app/api/og/[...path]/route.tsx
@@ -42,7 +42,8 @@ export async function GET(
 			}}
 		>
 			{/* Sourcegraph logo */}
-			<img src={logoDataUrl} width={246} height={35} />
+			{/* eslint-disable-next-line @next/next/no-img-element, jsx-a11y/alt-text -- Satori requires a native image, and alt text is not rendered. */}
+			<img src={logoDataUrl} width={246} height={35} alt="" />
 
 			{/* Title */}
 			<div
diff --git a/src/components/Logo.tsx b/src/components/Logo.tsx
index 82eec1921..2acb056e7 100644
--- a/src/components/Logo.tsx
+++ b/src/components/Logo.tsx
@@ -3,11 +3,13 @@ export function Logo(props: React.ComponentPropsWithoutRef<'svg'>) {
 
 	return (
 		<>
+			{/* eslint-disable-next-line @next/next/no-img-element -- SVG logos do not need image optimization. */}
 			<img
 				className="hidden h-[23px] w-[190px] dark:block"
 				src={`${basePath}/logo-theme-dark.svg`}
 				alt="Sourcegraph Docs"
 			/>
+			{/* eslint-disable-next-line @next/next/no-img-element -- SVG logos do not need image optimization. */}
 			<img
 				className="block h-[23px] w-[190px] dark:hidden"
 				src={`${basePath}/logo-theme-light.svg`}
diff --git a/src/components/mdx/LinkCards.tsx b/src/components/mdx/LinkCards.tsx
index 8e43e1b3f..493c494a4 100644
--- a/src/components/mdx/LinkCards.tsx
+++ b/src/components/mdx/LinkCards.tsx
@@ -31,6 +31,7 @@ export function LinkCard({
 		<div className="not-prose group relative rounded-xl border border-light-border-2 dark:border-dark-border">
 			<div className="absolute -inset-px rounded-xl border-2 border-transparent opacity-0 transition-opacity [background:linear-gradient(var(--quick-links-hover-bg,theme(colors.light-bg)),var(--quick-links-hover-bg,theme(colors.light-bg-1)))_padding-box,linear-gradient(144deg,#F34E3F,#A96AF3)_border-box] group-hover:opacity-100 dark:[--quick-links-hover-bg:theme(colors.dark-bg)]" />
 			<div className="relative flex items-center gap-4 overflow-hidden rounded-xl p-4 sm:gap-6">
+				{/* eslint-disable-next-line @next/next/no-img-element -- Small MDX icons do not need image optimization. */}
 				<img className="not-prose h-8 w-8" alt={imgAlt} src={imgSrc} />
 				<div className="flex flex-col items-start gap-1">
 					<h3 className="slate-900 font-display text-xl dark:text-white">
diff --git a/src/components/mdx/ProductCards.tsx b/src/components/mdx/ProductCards.tsx
index ac298fb5e..38f0f7d03 100644
--- a/src/components/mdx/ProductCards.tsx
+++ b/src/components/mdx/ProductCards.tsx
@@ -28,6 +28,7 @@ export function ProductCard({
 		<div className="group relative rounded-xl border border-light-border-2 dark:border-dark-border">
 			<div className="absolute -inset-px rounded-xl border-2 border-transparent opacity-0 transition-opacity [background:linear-gradient(var(--quick-links-hover-bg,theme(colors.light-bg)),var(--quick-links-hover-bg,theme(colors.light-bg-1)))_padding-box,linear-gradient(144deg,#F34E3F,#A96AF3)_border-box] group-hover:opacity-100 dark:[--quick-links-hover-bg:theme(colors.dark-bg)]" />
 			<div className="relative flex flex-col items-start gap-y-4 overflow-hidden rounded-xl p-6">
+				{/* eslint-disable-next-line @next/next/no-img-element -- Small MDX icons do not need image optimization. */}
 				<img className="not-prose h-8 w-8" alt={imgAlt} src={imgSrc} />
 				<div>
 					<h2 className="font-display text-base text-slate-900 dark:text-white">
diff --git a/src/components/mdx/ZoomableImage.tsx b/src/components/mdx/ZoomableImage.tsx
index eeb8aaa9c..ef395215c 100644
--- a/src/components/mdx/ZoomableImage.tsx
+++ b/src/components/mdx/ZoomableImage.tsx
@@ -28,6 +28,7 @@ export function ZoomableImage({className, alt, ...props}: ZoomableImageProps) {
 
 	return (
 		<>
+			{/* eslint-disable-next-line @next/next/no-img-element -- MDX image dimensions are unknown. */}
 			<img
 				className={`cursor-zoom-in rounded-xl ${className ?? ''}`}
 				alt={alt}
@@ -63,6 +64,7 @@ export function ZoomableImage({className, alt, ...props}: ZoomableImageProps) {
 							<line x1="6" y1="6" x2="18" y2="18" />
 						</svg>
 					</button>
+					{/* eslint-disable-next-line @next/next/no-img-element -- MDX image dimensions are unknown. */}
 					<img
 						className="max-h-[90vh] max-w-[90vw] cursor-zoom-out rounded-lg object-contain"
 						alt={alt}