Exposes direct cork/uncork on the underlying AsyncSocket for both WebSocket and HttpResponse, bypassing the safe callback-based cork() API for advanced use cases requiring manual cork state management.

Changes

• AsyncSocketCorkHelper<bool SSL> — thin helper struct inheriting uWS::AsyncSocket<SSL> to expose the protected cork() and uncork() methods; guarded with #ifndef UWS_JS_ASYNC_SOCKET_CORK_HELPER_DEFINED to prevent ODR violations when both wrapper headers are compiled in the same TU
• WebSocketWrapper — adds uWS_WebSocket_corkUnsafe / uWS_WebSocket_uncorkUnsafe, registered as _corkUnsafe / _uncorkUnsafe
• HttpResponseWrapper — adds res_corkUnsafe / res_uncorkUnsafe, registered in the if constexpr (SSL != 2) block (same scope as cork; excludes QUIC/CACHE); uses SSL != 0 to map int PROTOCOL → bool SSL for the cast
• docs/index.d.ts — adds typed declarations for both interfaces with warnings about mandatory pairing

Usage

// Manual cork/uncork without callback overhead
ws._corkUnsafe();
ws.send(data1);
ws.send(data2);
ws._uncorkUnsafe();

res._corkUnsafe();
res.writeStatus('200 OK').writeHeader('Content-Type', 'text/plain').end('hello');
res._uncorkUnsafe();

⚠️ _corkUnsafe must always be paired with _uncorkUnsafe. Failing to uncork leaves the socket in a permanently corked state and prevents data from being flushed.

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.