Entire existing guide deleted, not appended to

The PR description says it "adds a troubleshooting section," but the diff shows that the complete original 211-line document was deleted and replaced with only the 40-line hypervisorlaunchtype recovery snippet. This loses all of the following content that existed before this change:

• The YAML frontmatter (title, summary, read_when) required by Mintlify for navigation and page metadata
• The H1 page title (# WSL2 + Windows + remote Chrome CDP troubleshooting)
• "Choose the right browser mode first" (Options 1 & 2)
• "Working architecture" reference shape
• "Why this setup is confusing" overview
• "Critical rule for the Control UI"
• All five validation layers (Chrome serves CDP → WSL2 reachability → browser profile config → Control UI layer → end-to-end test)
• "Common misleading errors" quick-reference table
• "Fast triage checklist"
• "Practical takeaway"

The intended change — adding a hypervisorlaunchtype recovery section — should be appended to the existing guide, not used to replace it. Please restore the original content and add the new section underneath it (e.g. as a new ## Troubleshooting specific scenarios or directly appended before "Practical takeaway").

This is a comment left during a code review.
Path: docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md
Line: 3

Comment:
**Entire existing guide deleted, not appended to**

The PR description says it "adds a troubleshooting section," but the diff shows that the complete original 211-line document was deleted and replaced with only the 40-line `hypervisorlaunchtype` recovery snippet. This loses all of the following content that existed before this change:

- The YAML frontmatter (`title`, `summary`, `read_when`) required by Mintlify for navigation and page metadata
- The H1 page title (`# WSL2 + Windows + remote Chrome CDP troubleshooting`)
- "Choose the right browser mode first" (Options 1 & 2)
- "Working architecture" reference shape
- "Why this setup is confusing" overview
- "Critical rule for the Control UI"
- All five validation layers (Chrome serves CDP → WSL2 reachability → browser profile config → Control UI layer → end-to-end test)
- "Common misleading errors" quick-reference table
- "Fast triage checklist"
- "Practical takeaway"

The intended change — adding a `hypervisorlaunchtype` recovery section — should be appended to the existing guide, not used to replace it. Please restore the original content and add the new section underneath it (e.g. as a new `## Troubleshooting specific scenarios` or directly appended before "Practical takeaway").

How can I resolve this? If you propose a fix, please make it concise.

Update: I pushed a follow-up commit that addresses the bot review concerns on this PR.

What was fixed:

• Restored the full existing guide content (no full-file replacement).
• Kept Mintlify frontmatter + top-level title structure.
• Appended the new hypervisor-toggle recovery section instead of overwriting the page.
• Added shell-specific notes for PowerShell vs WSL (curl.exe alias caveat, Admin requirement for netsh, dynamic WSL host IP handling).

The new section is focused on the real-world hypervisorlaunchtype off/auto reboot failure mode and includes a strict validation sequence for both Windows and WSL2.

Addressed ✅

I pushed commit 7ee5e8a to this PR to resolve the review concerns:

• Restored full original guide content (no full-file replacement)
• Restored Mintlify frontmatter and H1
• Appended the hypervisor-toggle recovery section instead of overwriting
• Added shell-specific caveats (curl.exe in PowerShell, Admin requirement for netsh, dynamic WSL host IP notes)

If helpful, please re-review against latest head commit.

Missing Mintlify frontmatter and H1 title

The original file opened with a YAML frontmatter block and an H1 heading, both of which are required for this Mintlify-hosted docs site:

---
summary: "Troubleshoot WSL2 Gateway + Windows Chrome remote CDP in layers"
read_when:
  - Running OpenClaw Gateway in WSL2 while Chrome lives on Windows
  - Seeing overlapping browser/control-ui errors across WSL2 and Windows
  - Deciding between host-local Chrome MCP and raw remote CDP in split-host setups
title: "WSL2 + Windows + remote Chrome CDP troubleshooting"
---

# WSL2 + Windows + remote Chrome CDP troubleshooting

Without the frontmatter the page will lose its nav title, summary, and read_when fields. Without the H1 the document also starts with a ## heading, which renders incorrectly as a sub-section with no visible page title. Both should be restored.

This is a comment left during a code review.
Path: docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md
Line: 1-3

Comment:
**Missing Mintlify frontmatter and H1 title**

The original file opened with a YAML frontmatter block and an H1 heading, both of which are required for this Mintlify-hosted docs site:

```yaml
---
summary: "Troubleshoot WSL2 Gateway + Windows Chrome remote CDP in layers"
read_when:
  - Running OpenClaw Gateway in WSL2 while Chrome lives on Windows
  - Seeing overlapping browser/control-ui errors across WSL2 and Windows
  - Deciding between host-local Chrome MCP and raw remote CDP in split-host setups
title: "WSL2 + Windows + remote Chrome CDP troubleshooting"
---

# WSL2 + Windows + remote Chrome CDP troubleshooting
```

Without the frontmatter the page will lose its nav title, `summary`, and `read_when` fields. Without the H1 the document also starts with a `##` heading, which renders incorrectly as a sub-section with no visible page title. Both should be restored.

How can I resolve this? If you propose a fix, please make it concise.

Re-add front matter to WSL2 CDP troubleshooting page

This file now starts directly with a section header, so it no longer provides the summary/read_when metadata expected by the docs tooling; for example, scripts/docs-list.js reports this page as [missing front matter] instead of indexing it normally. That regression makes the page harder to discover and weakens downstream doc maintenance flows that rely on front matter fields.

Useful? React with 👍 / 👎.