fix(mux): strip internal stub note from PTY OpenAPI descriptions (#9315)

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 119
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/runloop-ai/runloop-70af693bc68f1ed5f2678a59d9ad3bb8a9e9bf8356fac4c3080cbd1a117819f8.yml
-openapi_spec_hash: b29dfd448505a0a3a6686202f606b8f7
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/runloop-ai/runloop-a248dcb8ee40eb7c0446077413996aa6a67b543a1f2a47272378641fa8791e7f.yml
+openapi_spec_hash: 0636ec3e6ef760052c346ecaa8a4107d
 config_hash: 444e00951b440bf92e7548b2807584a4

src/resources/pty.ts

@@ -16,22 +16,18 @@ export class Pty extends APIResource {
    * effect. The response returns a PtyConnectView containing connect_url (a
    * server-relative path to the WebSocket data plane), idle_ttl_seconds (how long
    * this session is retained after the last client disconnects), and the resulting
-   * cols/rows. The interactive byte stream itself is intentionally not modeled in
-   * OpenAPI; see the controller-level documentation for the WebSocket close-code
-   * conventions. The single-attach contract is enforced when a client opens the
-   * WebSocket data plane, not on this bootstrap call: bootstrap always succeeds for
-   * a valid session_name, even if another client is currently attached. Rejection of
-   * a second concurrent attach happens at WebSocket upgrade time. If the active
-   * client disconnects, the session is preserved for the idle TTL so a later connect
-   * using the same session_name resumes the same shell. After the TTL expires, after
-   * an explicit close control action, or after the underlying Devbox lifecycle
-   * replaces the PTY process (such as through suspend/resume), a later request with
-   * the same session_name creates a fresh PTY session without the previous shell
-   * state.
-   *
-   * Documentation note: this operation is published from mux strictly as an OpenAPI
-   * contract stub for the PTY service control plane. It is not evidence that mux
-   * itself serves the interactive PTY transport.
+   * cols/rows. The interactive terminal byte stream is exchanged over the WebSocket
+   * data plane and is not modeled in this OpenAPI contract; clients should connect
+   * to connect_url and exchange raw binary frames for terminal I/O. The
+   * single-attach contract is enforced when a client opens the WebSocket data plane,
+   * not on this bootstrap call: bootstrap always succeeds for a valid session_name,
+   * even if another client is currently attached. Rejection of a second concurrent
+   * attach happens at WebSocket upgrade time. If the active client disconnects, the
+   * session is preserved for the idle TTL so a later connect using the same
+   * session_name resumes the same shell. After the TTL expires, after an explicit
+   * close control action, or after the underlying Devbox lifecycle replaces the PTY
+   * process (such as through suspend/resume), a later request with the same
+   * session_name creates a fresh PTY session without the previous shell state.
    */
   connect(
     sessionName: string,
@@ -68,10 +64,6 @@ export class Pty extends APIResource {
    * (best-effort; ignored if the shell has already exited) and drops the session
    * from the server's session cache. A subsequent connect with the same session_name
    * will create a fresh PTY session.
-   *
-   * Documentation note: this operation is published from mux strictly as an OpenAPI
-   * contract stub for the PTY service control plane. It is not evidence that mux
-   * itself serves the interactive PTY transport.
    */
   control(
     sessionName: string,