docs: update chromium references for deprecation in v1.10 (#1984)

Cherry-pick of #1983 (stable docs) with v1.10-specific adjustments.
The auto-backport failed due to CLI reference conflicts with #1982.

- Deprecation callout documents transparent redirect behavior:
  `quarto install chromium` installs chrome-headless-shell and
  auto-removes legacy chromium
- Sample quarto check output uses v1.10.2 with
  "Chromium (deprecated)" label
- Binder description updated to Chrome Headless Shell
- Preview workflow excludes CLAUDE.md from changed-files detection
- CLI reference files unchanged (already correct from #1982)

Companion to quarto-dev/quarto-cli#14334

Author: cderv

.claude/rules/quarto-web-workflow.md

@@ -0,0 +1,10 @@
+# quarto-web Workflow
+
+## Stable → Prerelease
+
+1. PRs target `main` (stable/released docs)
+2. On merge, `port-to-prerelease.yml` (korthout/backport-action) auto-creates a cherry-pick PR to `prerelease`
+3. Prerelease-specific changes (e.g., v1.10 features) are layered in a follow-up PR after the backport merges
+
+Always PR to `main` first for shared content. Never PR directly to `prerelease` for changes that apply to both stable and prerelease.
+

.github/workflows/preview.yml

@@ -155,6 +155,8 @@ jobs:
             docs/reference/**/*.json
             docs/cli/*.json
             docs/**/images/*.png
+          files_ignore: |
+            **/CLAUDE.md
           json: true
           escape_json: false
 

bug-reports.qmd

@@ -100,44 +100,46 @@ For instance, the markdown code you would provide might look like this:
 
 ````md
 ```bash
-Quarto 1.5.42
+Quarto 1.10.2
 [✓] Checking versions of quarto binary dependencies...
-      Pandoc version 3.2.0: OK
+      Pandoc version 3.4.0: OK
       Dart Sass version 1.70.0: OK
-      Deno version 1.41.0: OK
+      Deno version 1.46.3: OK
       Typst version 0.11.0: OK
 [✓] Checking versions of quarto dependencies......OK
 [✓] Checking Quarto installation......OK
-      Version: 1.5.42
+      Version: 1.10.2
       Path: /Applications/quarto/bin
 
 [✓] Checking tools....................OK
-      TinyTeX: v2024.03.13
-      Chromium: (not installed)
+      TinyTeX: v2026.04
+      Chromium (deprecated): (not installed)
+      Chrome Headless Shell: (not installed)
+      VeraPDF: (not installed)
 
 [✓] Checking LaTeX....................OK
       Using: TinyTex
       Path: /Users/username/Library/TinyTeX/bin/universal-darwin
-      Version: 2024
+      Version: 2026
 
 [✓] Checking basic markdown render....OK
 
 [✓] Checking Python 3 installation....OK
       Version: 3.12.1
       Path: /.venv/bin/python3
       Jupyter: 5.7.2
-      Kernels: julia-1.10, python3
+      Kernels: python3
 
 [✓] Checking Jupyter engine render....OK
 
 [✓] Checking R installation...........OK
-      Version: 4.3.3
-      Path: /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources
+      Version: 4.4.2
+      Path: /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources
       LibPaths:
-        - /Users/username/Library/R/arm64/4.3/library
-        - /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
-      knitr: 1.45
-      rmarkdown: 2.26
+        - /Users/username/Library/R/arm64/4.4/library
+        - /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/library
+      knitr: 1.49
+      rmarkdown: 2.29
 
 [✓] Checking Knitr engine render......OK
 ```

docs/authoring/diagrams.qmd

@@ -246,8 +246,16 @@ quarto install chrome-headless-shell
 
 [Chrome Headless Shell](https://developer.chrome.com/blog/chrome-headless-shell) is a lightweight, headless-only browser from Google's [Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing) infrastructure. It has fewer system dependencies than full Chromium, making it a good fit for Docker containers and WSL environments.
 
-::: callout-note
-## Legacy Chromium
+::: callout-warning
+## Chromium (Deprecated)
+
+The `quarto install chromium` command is deprecated. It transparently redirects to `chrome-headless-shell` — running `quarto install chromium` installs Chrome Headless Shell and automatically removes any legacy Chromium installation. CI pipelines using `quarto install chromium --no-prompt` continue to work without changes.
+
+To install Chrome Headless Shell directly:
+
+``` {.bash filename="Terminal"}
+quarto install chrome-headless-shell
+```
 
-The older `quarto install chromium` command (which installs Chromium via Puppeteer) is still available but no longer recommended. If you use it, note that the Puppeteer-bundled Chromium may not work in Docker or WSL — see [Puppeteer troubleshooting](https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-puppeteer-in-docker) for details.
+This also automatically removes any legacy Puppeteer Chromium. The `chromium` tool will be removed from the registry in a future release.
 :::

docs/cli/includes/CLAUDE.md

@@ -0,0 +1,10 @@
+# CLI Reference: Auto-Generated Files
+
+Files in this directory are auto-generated. Do not edit manually.
+
+## Regeneration
+
+1. `quarto dev-call cli-info > docs/cli/cli-info.json`
+2. `Rscript --vanilla _tools/reference-cli-generate-md.R`
+
+Descriptions come from quarto-cli source. To change them permanently, update the CLI command definitions in quarto-cli.

docs/output-formats/pdf-engine.qmd

@@ -44,9 +44,11 @@ which will provide a list of available tools, the installed versions, and the la
 ``` bash
 [✓] Inspecting tools
 
-Tool         Status            Installed     Latest
-chromium     Not installed     ---           869685
-tinytex      Up to date        v2022.10      v2022.10
+Tool                      Status            Installed     Latest
+chrome-headless-shell     Not installed     ---           147.0.7727.56
+chromium                  Not installed     ---           869685
+tinytex                   Up to date        v2026.04      v2026.04
+verapdf                   Not installed     ---           1.28.2
 ```
 
 To update to the latest version, use the command:

docs/projects/binder.qmd

@@ -116,7 +116,7 @@ The following files may be generated by the `quarto use binder` command. Note th
 
 `postBuild`
 
-:   The post build script runs code after restoring the environment. This script is generated with commands required to ensure the proper version of Quarto is present in the environment, install any required tools like TinyTex or Chromium, and to configure VSCode and the Quarto extension for VSCode when applicable.
+:   The post build script runs code after restoring the environment. This script is generated with commands required to ensure the proper version of Quarto is present in the environment, install any required tools like TinyTeX or Chrome Headless Shell, and to configure VSCode and the Quarto extension for VSCode when applicable.
 
 `apt.txt`
 

docs/troubleshooting/index.qmd

@@ -13,46 +13,46 @@ but this page might help you get up and running quickly.
 You can check the version of Quarto and its dependencies by running `quarto check`. Here's an example of the output it generates:
 
 ```
-Quarto 1.6.30
-[✓] Checking environment information...
-      Quarto cache location: /Users/cscheid/Library/Caches/quarto
+Quarto 1.10.2
 [✓] Checking versions of quarto binary dependencies...
       Pandoc version 3.4.0: OK
       Dart Sass version 1.70.0: OK
       Deno version 1.46.3: OK
       Typst version 0.11.0: OK
 [✓] Checking versions of quarto dependencies......OK
 [✓] Checking Quarto installation......OK
-      Version: 1.6.30
-      Path: /Users/cscheid/repos/github/cscheid/quarto-regress/releases/v1.6.30/binQuarto 1.5.42
+      Version: 1.10.2
+      Path: /Applications/quarto/bin
 
 [✓] Checking tools....................OK
-      TinyTeX: v2024.03.13
-      Chromium: (not installed)
+      TinyTeX: v2026.04
+      Chromium (deprecated): (not installed)
+      Chrome Headless Shell: (not installed)
+      VeraPDF: (not installed)
 
 [✓] Checking LaTeX....................OK
       Using: TinyTex
       Path: /Users/username/Library/TinyTeX/bin/universal-darwin
-      Version: 2024
+      Version: 2026
 
 [✓] Checking basic markdown render....OK
 
 [✓] Checking Python 3 installation....OK
       Version: 3.12.1
       Path: /.venv/bin/python3
       Jupyter: 5.7.2
-      Kernels: julia-1.10, python3
+      Kernels: python3
 
 [✓] Checking Jupyter engine render....OK
 
 [✓] Checking R installation...........OK
-      Version: 4.3.3
-      Path: /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources
+      Version: 4.4.2
+      Path: /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources
       LibPaths:
-        - /Users/username/Library/R/arm64/4.3/library
-        - /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
-      knitr: 1.45
-      rmarkdown: 2.26
+        - /Users/username/Library/R/arm64/4.4/library
+        - /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/library
+      knitr: 1.49
+      rmarkdown: 2.29
 
 [✓] Checking Knitr engine render......OK
 ```