docs: add standalone debugger documentation

[ryanbas21]

Summary

• Add guide page (/docs/standalone-debugger) covering quick start, configuration, sessions, MCP mode, Node.js HTTP interceptor, and troubleshooting
• Add package reference page (/packages/devtools-standalone) with WebSocket protocol, MCP tools table, Effect services, and architecture diagram
• Update bridge package page with attachDebugger section and standalone connection docs
• Update getting-started page with standalone quick start section
• Update repository structure with standalone in package map and dependency graph
• Add standalone package card (tagged "New") to homepage grid
• Add standalone to architecture SVG diagram and package relationship descriptions

Test plan

• Run pnpm dev in apps/docs/ and verify new pages render at /docs/standalone-debugger and /packages/devtools-standalone
• Verify updated pages render correctly: /packages/devtools-bridge, /docs/getting-started, /contributing/repository-structure
• Verify homepage shows the new standalone package card with "New" tag
• Verify architecture diagram includes the standalone box and arrows
• Check all internal links resolve (standalone guide ↔ package reference, bridge → standalone)
• Run pnpm build to confirm elm-pages compiles without errors

🤖 Generated with Claude Code

[pullfrog]

Important

The SVG architecture diagram has an arrow coordinate bug—the devtools-types → devtools-standalone arrow starts at the bottom of the devtools-bridge box instead of the bottom of devtools-types. This will render as a bridge→standalone dependency, which is incorrect.

TL;DR — Adds two new doc pages (standalone debugger guide + package reference), updates the bridge page with attachDebugger API docs, and adds the standalone package to the architecture diagram, homepage grid, and repo structure page. Comprehensive docs rollout for the standalone Electron debugger.

Key changes

• New standalone debugger guide — quick start, configuration, session tracking, MCP mode, Node.js HTTP interceptor, troubleshooting
• New standalone package reference — installation, modes, WebSocket protocol, MCP tools table, Effect services list, architecture diagram
• Update bridge package docs — add attachDebugger section with options table, DebuggerHandle interface, and lifecycle explanation
• Update getting-started — add standalone quick start section with code example
• Update architecture diagram — add standalone box, arrow, and package description to the OIDC DevTools group
• Update homepage — add standalone package card with "New" tag to the grid
• Update repo structure — add standalone to package table and dependency graph

_{Summary ｜ 7 files ｜ 1 commit ｜ base: main ← docs/standalone-debugger}

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ 𝕏}

[pullfrog]

Addressed the review comment on the architecture diagram. The devtools-types → devtools-standalone arrow was starting at y=260 (bottom of bridge) instead of y=140 (bottom of types). Fixed by changing svgArrow 180 260 180 320 → svgArrow 120 140 120 320 in Architecture.elm:134, which also avoids overlap with the types→bridge arrow at x=180. Committed as 1b34d22, pushed, replied, and thread resolved.

Task list (3/3 completed)

• Read Architecture.elm to understand the arrow coordinate bug
• Fix the svgArrow coordinates for types→standalone
• Commit, push, reply, resolve, and report progress

  ^{｜ View workflow run ｜ via Pullfrog ｜ 𝕏}

[pullfrog]

No new issues. The prior review's sole finding (SVG arrow coordinate bug in the devtools-types → devtools-standalone arrow) was addressed by removing the incorrect arrow.

Reviewed the following changes:

• Expanded SVG viewBox and added the standalone box + core→standalone arrow; removed the buggy types→standalone arrow instead of repositioning it
• Added standalone package card ("New" tag) to the homepage grid

  ^{｜ View workflow run ｜ 𝕏}