docs(go2): add local Wi-Fi teleop troubleshooting guide

[kezaer]

Summary

• Add a public Go2 local Wi-Fi teleop troubleshooting guide covering discovery, Wi-Fi resets, dashboard/video/keyboard/phone teleop checks, and macOS-specific notes.
• Link the guide from the Go2 getting-started page and list teleop-phone-go2 in the Go2 blueprint table.
• Add the guide to docs navigation and update stale agents/... nav entries to coding-agents/... so Mint validation uses existing files.

Why

Operators need a safe recovery path for local Wi-Fi teleop before pressing any movement controls. The guide separates robot reachability, operator-machine addressing, browser UI routing, and image-stream checks.

Safety

• The guide emphasizes no-motion checks before live teleop.
• It explicitly warns that --listen-host 0.0.0.0 should be used only on a trusted local network when another device needs to reach the UI.

Validation

• python3 -m json.tool docs/docs.json >/dev/null
• npm --prefix docs run validate

Note: Mint validation succeeds while printing the existing favicon warning: Error generating favicons: Invalid image buffer.

[greptile-apps]

Greptile Summary

This PR adds a comprehensive Go2 local Wi-Fi teleop troubleshooting guide and integrates it into the docs navigation and the Go2 getting-started page. It also corrects stale agents/… nav entries in docs.json to coding-agents/… to match the actual directory layout.

• New guide (local_wifi_teleop_troubleshooting.md) covers robot discovery, Wi-Fi resets, dashboard/video/keyboard/phone teleop checks, macOS notes, a symptom-reference table, and guidance on when to open a bug report.
• Index updates add a teleop-phone-go2 row to the blueprint table and two cross-links to the new guide in the Pre-flight and Deep Dive sections.
• docs.json nav fixes rename six agents/… page paths to coding-agents/… (matching the real directory) and register the new troubleshooting page under Platforms → Quadruped.

Confidence Score: 5/5

Documentation-only change with no runtime code; safe to merge.

All three files are Markdown or JSON configuration. The nav-path renames in docs.json align with the actual coding-agents/ directory on disk. Internal doc links in the new guide point to pages already registered in docs.json, and GitHub source links use absolute blob URLs. The PR author confirmed Mint validation passes.

No files require special attention.

Important Files Changed

Filename	Overview
docs/platforms/quadruped/go2/local_wifi_teleop_troubleshooting.md	New 271-line troubleshooting guide; all internal doc links resolve to registered pages in docs.json and all GitHub source links use absolute blob URLs.
docs/platforms/quadruped/go2/index.md	Adds teleop-phone-go2 blueprint row and two cross-links to the new guide; consistent with existing link style in the file.
docs/docs.json	Corrects six stale agents/… nav paths to coding-agents/… (matching the real directory) and registers the new troubleshooting page; all referenced files exist on disk.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Go2 Getting Started\nindex.md] -->|Cross-link added| B[Local Wi-Fi Teleop\nTroubleshooting Guide]
    B --> C{Problem area}
    C --> D[Discovery & Reconnects\ndimos go2tool discover]
    C --> E[Dashboard\nport 7779]
    C --> F[Video Feed\ndimos lcmspy]
    C --> G[Keyboard Control\nport 3030 WebSocket]
    C --> H[Phone Teleop\nHTTPS port 8444]
    C --> I[macOS Notes]
    B --> J[Symptom Reference Table]
    B --> K[When To Open A Bug]
    L[docs.json] -->|Nav registered| B
    L -->|Path corrected| M[coding-agents/*\nwas agents/*]

Loading

_{Reviews (4): Last reviewed commit: "Remove doctor dependency from Go2 troubl..." | Re-trigger Greptile}

[kezaer]

Addressed the dependency issue in c6017ef. The guide no longer references dimos go2tool doctor, so this docs PR can merge independently of #2378. The quick-recovery flow now uses the existing manual listener check with lsof, and the separate later section keeps the same no-motion port verification path.

Re-ran:

• python3 -m json.tool docs/docs.json >/dev/null
• npm --prefix docs run validate

Mint validation still exits successfully with the existing favicon warning.