amadan
instances create prints 'unexpected response (status 202)' when a claim-mode console accepts it asynchronously open
platform-d8's deployment harness found this at G10, Run 8, on 2026-10-20.
With the console's host claim runtime on, POST /instances can answer 202 with {"operation_id", "phase", "host"}, where the claim operation is accepted but not finished (internal/console/claim_create.go:133, apiinstances.go:1643). The CLI's instanceCreate (apimode.go:3425) treats anything but 201 as an error, so it prints unexpected response (status 202) for a create that is actually under way.
The fix is to handle 202 like instanceSetChannel's proposed path: a typed result naming the host, the operation and its phase, and telling the operator how to watch it. Because that adds operator-visible text, it needs Paul's copy review. This only matters with CARLOSHOSTCLAIM on, which today means the dev trial, so it doesn't block. platform-1c will build it after the trial's G10 blocker.