Summary

crossws#200 makes the server plugin's resolve optional — it now defaults to calling the app's fetch handler and reading the hooks that defineWebSocketHandler() attaches as .crossws. That makes the resolve: (req) => (await app.fetch(req)).crossws boilerplate in our docs redundant (it was h3 wiring itself back into itself).

This PR updates the WebSocket guide + example to the zero-config form:

 serve(app, {
-  plugins: [ws({ resolve: async (req) => (await app.fetch(req)).crossws })],
+  plugins: [ws()],
 });

Docs-only — no src/ changes. serve() already passes fetch: app.fetch to srvx and defineWebSocketHandler already attaches .crossws, so nothing in the framework needs to change.

Changes

• docs/1.guide/901.advanced/2.websocket.md — use ws(), update prose, add a NOTE explaining resolve is now only for custom hook resolution, and drop the outdated "WIP" callout.
• examples/websocket.mjs — drop the resolve argument.

Follow-up (not in this PR)

• Bump the crossws peer/dev range once the release carrying crossws#200 is published (currently ^0.4.8).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified WebSocket setup instructions for H3 with CrossWS.
  • Updated examples to use a simpler plugin setup and noted when custom route resolution is needed.
• Bug Fixes
  • Removed outdated wording about WebSocket support status, making the guidance clearer and more accurate.