ENG-2736 - Remove Sandbox Unresponsive

[DamianB-BitFlipper]

The way that the prime cli handles "unresponsive" is not accurate. It is simply a timeout. Remove the concept of "unresponsive", and treat it as a timeout. If unresponsive sandboxes are an issue, the way to detect them would be with a liveliness checks and heartbeats.

---

Note

Medium Risk
Changes exception types and timeout behavior in the sandbox command execution path, which may affect downstream error handling/retries despite being a small, targeted change.

Overview
Removes the SandboxUnresponsiveError concept from prime-sandboxes. Gateway command timeouts now consistently raise CommandTimeoutError (unless the sandbox is known to be TERMINATED/ERROR/TIMEOUT, in which case _raise_not_running_error is used), and the SDK version is bumped to 0.2.13.

Also tweaks gateway command timeout handling to use effective_timeout + 2 seconds to avoid prematurely killing near-deadline commands, plus a handful of CLI formatting-only cleanups (string wrapping/whitespace) in RL and env-var/metadata utilities.

^{Written by Cursor Bugbot for commit 6d6e03b. This will update automatically on new commits. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3027b44635

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}