ide-diagnostics-boardlisted

Generate a visual diagnostics dashboard for the workspace and open it in the browser. ## Prerequisites 1. Check if the `getToolCapabilities` MCP tool is available to you. - **Available**: call it, check `extensionConnected` → use **IDE Path** below. - **Not available** (no MCP tool by that name): use **CLI Path** below. ## Arguments `$ARGUMENTS` sets the severity filter: - `error` — errors only - `warning` — warnings and errors - `all` (default) — all severities --- ## IDE Path Use this path when bridge MCP tools are available. ### Phase 1 — Collect diagnostics 1. Determine the severity filter from `$ARGUMENTS` (default: `all`). 2. Call `getDiagnostics` with no URI filter (full workspace scan). Pass the severity param if supported. 3. If no diagnostics found, report "No diagnostics found — workspace is clean." and stop. ### Phase 2 — Summarize 4. Group diagnostics by severity: errors / warnings / info / hints. 5. Group by file: sort files by error count descending. 6. Compute totals: total diagnostic count, count per severity, number of files affected. ### Phase 3 — Generate and open HTML 7. Construct the HTML document (see HTML Template section below). 8. Call `openInBrowser` with the HTML string and filename `diagnostics-<timestamp>.html`. 9. Report: "Opened diagnostics board — N errors, M warnings across K files. Saved to: <path>" --- ## CLI Path Use this path when bridge MCP tools are NOT available (e.g., remote-control sessions). ### Phase 1 — Detect a