Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

examples/websocket.mjs (1)

2-2: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Variable name ws reused for both the crossws plugin and the client-side WebSocket instance.

Line 2 imports the crossws plugin as ws; the embedded browser script (line 63) also declares const ws = new WebSocket(url). These live in separate execution contexts (server module vs. generated HTML string) so there's no actual bug, but the shared name can confuse readers skimming the example.

Also applies to: 63-63

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@examples/websocket.mjs` at line 2, The identifier `ws` is being reused for
two different concepts in `examples/websocket.mjs`, which makes the example
harder to read. Rename the imported crossws plugin binding from `ws` to a more
explicit name in the module scope, and keep the browser-side `const ws = new
WebSocket(url)` as-is or rename that one for clarity; update all references tied
to the import so the `plugin` usage remains consistent.

docs/1.guide/901.advanced/2.websocket.md (1)

122-137: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Route path inconsistency in HTTP-fallback example.

The main "Full example" registers the combined route at / (line 47), but this snippet uses /_ws (line 130). Since the whole point of the section is to demonstrate the same combined-route pattern, using a consistent path avoids reader confusion.

✏️ Suggested tweak

 app.get(
-  "/_ws",
+  "/",
   defineWebSocketHandler(
     { message: (peer, message) => peer.send(message.text()) },
     () => "Send a WebSocket upgrade request to connect.",
   ),
 );

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/1.guide/901.advanced/2.websocket.md` around lines 122 - 137, The
HTTP-fallback example uses a different route path than the earlier
combined-route example, which can confuse readers about the pattern being
demonstrated. Update the app.get call in this snippet to use the same route path
as the “Full example” so the defineWebSocketHandler usage stays consistent
across the section.