docs(websocket): document boundary-aware listener matching

- Explain exact or slash-boundary path match with examples
- Note trailing slash stripping and root listener behavior

Author: NeaByteLab

docs/id/middleware/websocket.md

@@ -38,15 +38,17 @@ await router.serve(8000)
 Tentukan prefix path untuk upgrade WebSocket:
 
 ```typescript
-listener: '/ws' // Cocok /ws, /ws/chat, /ws/room/123, dll.
-listener: '/api/ws' // Cocok /api/ws, /api/ws/data, dll.
+listener: '/ws' // Cocok /ws, /ws/chat, /ws/room/123
+listener: '/api/ws' // Cocok /api/ws, /api/ws/data
 ```
 
+Pencocokan sadar-batas, jadi path harus sama persis dengan `listener` atau berlanjut dengan `/`. Dengan `listener: '/ws'`, request ke `/ws` atau `/ws/chat` di-upgrade, tapi `/wsfoo` tidak. Garis miring di akhir `listener` dipangkas, jadi `/ws/` berperilaku sama dengan `/ws`. Mengatur `listener: '/'` mencocokkan setiap path.
+
 **Penting:** Middleware hanya mengupgrade request yang:
 
 - Membawa header `Upgrade: websocket`
 - Memakai metode `GET`
-- Punya path yang dimulai dengan nilai `listener`
+- Cocok dengan path `listener` seperti dijelaskan di atas
 
 Tanpa `listener`, middleware meneruskan setiap request dan tidak pernah mengupgrade.
 
@@ -225,10 +227,10 @@ onConnect: (socket, event, ctx) => {
 
 Handshake yang ditolak diarahkan lewat error handler alih-alih melempar saat setup:
 
-- **Origin tidak diizinkan** mengembalikan **403** dengan pesan `WebSocket handshake rejected because the Origin is not allowed`.
-- **Upgrade tidak valid** mengembalikan **400** dengan pesan `WebSocket handshake is malformed because ...`.
+- **Origin tidak diizinkan** gagal dengan **403** dan pesan `WebSocket handshake rejected because the Origin is not allowed`.
+- **Upgrade tidak valid** gagal dengan **400** dan pesan `WebSocket handshake is malformed because ...`.
 
-Untuk membentuk response ini, daftarkan satu handler dengan [`router.catch()`](/id/error-handling/object-details), atau andalkan [perilaku default](/id/error-handling/default-behavior).
+Keduanya dialirkan ke [error handler terpusat](/id/error-handling/object-details), jadi bentuk response di sana atau andalkan [perilaku default](/id/error-handling/default-behavior).
 
 ## Integrasi Dengan CORS
 

docs/middleware/websocket.md

@@ -38,15 +38,17 @@ await router.serve(8000)
 Specify the path prefix for WebSocket upgrades:
 
 ```typescript
-listener: '/ws' // Matches /ws, /ws/chat, /ws/room/123, etc.
-listener: '/api/ws' // Matches /api/ws, /api/ws/data, etc.
+listener: '/ws' // Matches /ws, /ws/chat, /ws/room/123
+listener: '/api/ws' // Matches /api/ws, /api/ws/data
 ```
 
+Matching is boundary-aware, so the path must equal the `listener` exactly or continue with a `/`. With `listener: '/ws'`, a request to `/ws` or `/ws/chat` upgrades, but `/wsfoo` does not. A trailing slash on the `listener` is stripped, so `/ws/` behaves the same as `/ws`. Setting `listener: '/'` matches every path.
+
 **Important:** The middleware only upgrades requests that:
 
 - Carry the `Upgrade: websocket` header
 - Use the `GET` method
-- Have a path that starts with the `listener` value
+- Match the `listener` path as described above
 
 Without a `listener`, the middleware passes every request through and never upgrades.
 
@@ -225,10 +227,10 @@ onConnect: (socket, event, ctx) => {
 
 A rejected handshake routes through the error handler instead of throwing at setup:
 
-- **Disallowed origin** returns **403** with message `WebSocket handshake rejected because the Origin is not allowed`.
-- **Malformed upgrade** returns **400** with message `WebSocket handshake is malformed because ...`.
+- **Disallowed origin** fails with **403** and message `WebSocket handshake rejected because the Origin is not allowed`.
+- **Malformed upgrade** fails with **400** and message `WebSocket handshake is malformed because ...`.
 
-To shape these responses, register a single handler with [`router.catch()`](/error-handling/object-details), or rely on the [default behavior](/error-handling/default-behavior).
+Both route through the [central error handler](/error-handling/object-details), so shape the response there or rely on the [default behavior](/error-handling/default-behavior).
 
 ## Integration with CORS