Backend: Sandbox exists in Catalyst but not in Hadron (orphaned sandbox)

[rblalock]

Description

When listing sandboxes, some sandboxes appear in the list but file operations fail with a 404 from Hadron.

Reproduction

# Sandbox appears in list
$ agentuity --json cloud sandbox list
{
  "sandboxes": [
    {
      "sandboxId": "sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025",
      "name": "hello-ts-sandbox-1768319974",
      "status": "idle",
      "region": "use",
      ...
    }
  ]
}

# sandbox get works (hits Catalyst)
$ agentuity --json cloud sandbox get sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025
{
  "sandboxId": "sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025",
  "status": "idle",
  "region": "use",
  ...
}

# But file operations fail (hits Hadron)
$ agentuity --json cloud sandbox files sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025 -l
[ERROR] APIErrorResponse: error listing files in sandbox: error from hadron: 404 Not Found - {"success":false,"message":"not found: sandbox sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025 not found"}

Expected Behavior

Sandboxes listed in Catalyst should exist in Hadron, or orphaned entries should be cleaned up automatically.

Environment

• CLI version: 0.1.11
• Region: use (US East)

Analysis

The sandbox metadata exists in Catalyst's database but Hadron (the sandbox hypervisor) returns 404. This could be caused by:

1. Sandbox was terminated on Hadron but Catalyst wasn't notified
2. Sync failure between Catalyst and Hadron
3. Sandbox creation partially failed

Workaround

Delete the orphaned sandbox:

agentuity cloud sandbox delete sbx_ba39444798a1235b07140d740b93c3f5b9d0e641ed27929119741d922025 --confirm

[linear]

AGENT-1275