docs/client-configurations.md tells 13 clients to use a "config provided above" that the page does not contain #3008

Description of the bug

docs/client-configurations.md tells readers of 13 client sections (Amp, Cline, Codex, Copilot/VS Code, Cursor, Gemini CLI, Gemini Code Assist, JetBrains AI Assistant and Junie, Kiro, Qoder, Warp, Windsurf) to "use the config provided above" or "the standard config from above". Since the docs were split out of README.md in #2600, the standard config lives in README.md ("Getting started"), and this page has no such block above those sections. The Amp section, first on the page, has nothing above it at all. The JSON blocks that do appear earlier belong to other clients' collapsed sections: Antigravity's adds --browser-url=http://127.0.0.1:9222, which only attaches to an already-running debuggable Chrome; Bob's matches the standard config; and for Qoder, Warp and Windsurf the nearest block above is OpenCode's, which uses OpenCode's own config schema.

Actual behavior

On main, the references are at lines 9 (Amp), 102 (Cline), 108 (Codex), 194 (Copilot/VS Code), 219 (Cursor), 281 (Gemini CLI), 288 (Gemini Code Assist), 304 and 305 (JetBrains AI Assistant, Junie), 312 and 314 (Kiro), 379 and 381 (Qoder), 416 (Warp) and 423 (Windsurf). The page's only JSON blocks are at lines 22-35 (Antigravity, with --browser-url=http://127.0.0.1:9222), 50-59 (Bob) and 362-372 (OpenCode, "mcp": {"chrome-devtools": {"type": "local", "command": [...]}}). Every client section is a collapsed <details> element on GitHub, so a reader of the rendered page sees no configuration above the instruction. The page never links to the README's "Getting started" block.

Reproduction

1. Open docs/client-configurations.md on main and search for "above".
2. For each match, look for a configuration block earlier on the page that a reader could use.
3. Compare with README.md lines 72-80, which hold the standard config ("command": "npx", "args": ["-y", "chrome-devtools-mcp@latest"]).

Expectation

Each instruction to "use the config provided above" or "the standard config from above" should lead a reader of this page to the standard configuration it means, as it did when this text was part of README.md before #2600 (git show 5463101^:README.md places the same sentences below the standard config block).

MCP configuration

--headless --isolated --no-usage-statistics --no-performance-crux unless the reproduction states otherwise (update checks disabled with CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS=1).

Chrome DevTools MCP version

1.10.1 (npm) and main 5ddb0a3 (local build)

Chrome version

154.0.8037.98 (stable)

Node version

v22.23.2

Operating system

macOS 27.0

Environment details

• Release documentation: docs/client-configurations.md at tag chrome-devtools-mcp-v1.10.1, which has the same references.
• main documentation: docs/client-configurations.md at 5ddb0a3. Of its 16 lines containing "above", 15 are the references below; line 96 correctly refers to the Claude Code CLI method.
• No runtime was needed; the defect is in the Markdown file.

Evidence

• Expected source: README.md:72-80 (the standard config) and the pre-split wording in README.md before docs: split the docs in separate files #2600, where "above" referred to that block.
• Failure source: docs/client-configurations.md lines listed under Actual behavior, on main; the same wording at tag chrome-devtools-mcp-v1.10.1.
• Evidence provenance: static
• Local verification: static-proof
• Reproduction completeness: complete

Runtime reproduction was not needed or run; the evidence is the file content, re-read on main and at the tag. The full open and closed issue and PR corpus was screened as of 2026-10-06; no issue or PR mentions these references. Open PR #2922 and other open docs PRs do not touch this file.

Fix check

Failing now: the 13 sections' "config provided above" or "standard config from above" references point to no standard config on docs/client-configurations.md, and the first one (Amp) has nothing above it. Restored: each such reference on the page leads a reader to the standard npx -y chrome-devtools-mcp@latest configuration, on the page itself or by an explicit link. Control: sections that give their own complete client-specific block (Antigravity, Bob, OpenCode) keep their blocks.