fix: clean up PTY and lifecycle hook OpenAPI descriptions (#9502)

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-3ed5d8482ad69c2c52b9387f0c16e9a5053115b6e4c64ff59a32a0ab3498d7e2.yml
-openapi_spec_hash: b48f3fb201ee657d669d937ca92c55bf
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/runloop-ai/runloop-7235763cbdfd60834a897f356688d758b598a1dd723623330ea398dea2abea68.yml
+openapi_spec_hash: 01b9dbab4b732e4b83952debd108e404
 config_hash: 444e00951b440bf92e7548b2807584a4

src/resources/pty.ts

@@ -48,8 +48,8 @@ export class Pty extends APIResource {
 
   /**
    * Applies a PTY control operation to an existing session. The action field selects
-   * the operation; the other fields in PtyControlParameters are interpreted only
-   * when they are relevant to the chosen action.
+   * the operation; the other fields in PtyControlParams are interpreted only when
+   * they are relevant to the chosen action.
    *
    * resize: cols and rows are required and must each be in 1..=1000. A 0 or
    * out-of-range value returns 400. The new winsize is applied to the PTY master and

src/resources/shared.ts

@@ -350,14 +350,12 @@ export interface LifecycleConfiguration {
 
   /**
    * Lifecycle hooks for Devbox suspend. suspend_commands run sequentially as the
-   * configured Devbox user through the rage/vmagent suspend path before the Devbox
-   * suspends; failures are logged but do not block suspending. The
-   * suspend_deadline_ms budget defaults to 30000 ms, may not exceed 60000 ms, and
-   * covers broker drain plus suspend_commands. If the deadline is exceeded, suspend
-   * work is abandoned, the timeout is logged, and the Devbox still proceeds to
-   * suspend by shutting down vmagent and killing the VM. Resume hooks and resume
-   * deadline settings are persistence/internal only and hidden from the public API
-   * reference. launch_commands still run on every startup, including after resume.
+   * configured Devbox user before the Devbox suspends; failures are logged but do
+   * not block suspending. The suspend_deadline_ms budget defaults to 30000 ms, may
+   * not exceed 60000 ms, and covers broker drain plus suspend_commands. If the
+   * deadline is exceeded, suspend work is abandoned, the timeout is logged, and the
+   * Devbox still proceeds to suspend. launch_commands still run on every startup,
+   * including after resume.
    */
   lifecycle_hooks?: LifecycleHooks | null;
 
@@ -369,14 +367,12 @@ export interface LifecycleConfiguration {
 
 /**
  * Lifecycle hooks for Devbox suspend. suspend_commands run sequentially as the
- * configured Devbox user through the rage/vmagent suspend path before the Devbox
- * suspends; failures are logged but do not block suspending. The
- * suspend_deadline_ms budget defaults to 30000 ms, may not exceed 60000 ms, and
- * covers broker drain plus suspend_commands. If the deadline is exceeded, suspend
- * work is abandoned, the timeout is logged, and the Devbox still proceeds to
- * suspend by shutting down vmagent and killing the VM. Resume hooks and resume
- * deadline settings are persistence/internal only and hidden from the public API
- * reference. launch_commands still run on every startup, including after resume.
+ * configured Devbox user before the Devbox suspends; failures are logged but do
+ * not block suspending. The suspend_deadline_ms budget defaults to 30000 ms, may
+ * not exceed 60000 ms, and covers broker drain plus suspend_commands. If the
+ * deadline is exceeded, suspend work is abandoned, the timeout is logged, and the
+ * Devbox still proceeds to suspend. launch_commands still run on every startup,
+ * including after resume.
  */
 export interface LifecycleHooks {
   /**