feat: AutoResume API takes an enabled bool instead of enum policy

[matthewlouisbrockman]

Simplified the API to match the SDK inputs, autoresume will just have an enabled bool rather than a policy. Still stores as a config with a policy; for now autoResume true maps to an any policy and can change that as add settings

---

Note

Medium Risk
This changes the public API contract for sandbox creation auto-resume configuration, which can break existing clients and alters validation behavior (previously invalid/missing policies were rejected; now missing enabled defaults to off). Runtime risk is otherwise limited to how paused sandboxes are resumed based on the stored policy mapping.

Overview
Sandbox autoResume configuration is simplified from a policy enum (any/off) to a single boolean enabled, with server-side creation logic mapping enabled=true to SandboxAutoResumeAny and false (or omitted) to SandboxAutoResumeOff. The OpenAPI spec, generated API clients/swagger, and integration/unit tests are updated to use the new shape, and request-time validation for unknown/empty policies is removed.

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

[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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3b92b0af9a

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[matthewlouisbrockman]

converting to draft to do this halfway; moving the API to a bool for SDK parity but still storing as an enum config to avoid requiring a orchestrator deployment