docs(streaming): document WS close code 1006 as RFC-reserved client-side code (#200)

Add code 1006 to the close code tables in both the WebSocket streaming guide
and the WebSocket API reference, with a Callout explaining that it is never
transmitted over the wire — the client WebSocket library generates it locally
on abnormal TCP teardown (network loss, process kill). Developers commonly
mistake it for a server-sent code; the callout surfaces this before they waste
time debugging the server side.

Co-authored-by: root <root@api-dev.hs.chocopancake.com>
Co-authored-by: Paperclip <noreply@paperclip.ing>

Author: 3 people

content/en/api-reference/websocket.mdx

@@ -590,10 +590,15 @@ WebSocket frames may also carry the HTTP-style `invalid_api_key`, `tier_restrict
 | Code | Meaning | Resolution |
 |------|---------|------------|
 | `1000` | Normal close | Client or server initiated clean close |
+| `1006` | Abnormal closure (client-side) | Network drop or process kill — always reconnect |
 | `4001` | Authentication failure | Check your API key |
 | `4003` | No streaming access | Add WebSocket add-on ($99/mo) or upgrade to Enterprise |
 | `4029` | Stream limit exceeded | Close unused connections (default: 1 per key; newer connection wins) |
 
+<Callout type="warning">
+**Code 1006 is RFC 6455 reserved and is never transmitted over the wire.** Your WebSocket library generates it locally when the TCP connection is lost without a proper closing handshake (network failure, process kill, OS-level timeout). The server did not send it. Always reconnect on 1006.
+</Callout>
+
 ## Sequence Numbers
 
 Every server message includes a `seq` field — a per-connection integer that increments with each message. The `connected` message also includes `global_seq`, a server-wide event counter.

content/en/streaming/websocket.mdx

@@ -155,10 +155,15 @@ The server keeps a 2-minute replay buffer. Pass `resume=true&from_seq=N` on reco
 | Code | Meaning | Action |
 |------|---------|--------|
 | `1000` | Normal close | No action needed |
+| `1006` | Abnormal closure (client-side) | Network drop — always reconnect |
 | `4001` | Bad or missing API key | Fix your API key |
 | `4003` | No streaming access | Purchase WebSocket add-on |
 | `4029` | Too many connections | Close unused connections first |
 
+<Callout type="warning">
+**Code 1006 is RFC 6455 reserved and never sent by the server.** Your WebSocket library generates it locally when the TCP connection drops without a closing handshake (network failure, process kill). Always reconnect when you see it — the example below already does this correctly by only skipping reconnect on `1000`.
+</Callout>
+
 ## Full API Reference
 
 For complete documentation including all message schemas, error handling, and multi-language examples, see the [WebSocket API Reference](/en/api-reference/websocket).