docs(postman): add official Postman collection generated from OpenAPI

[govindkavaturi-art]

Auto-generated from the live OpenAPI spec at api.cueapi.ai/openapi.json. 16 folders / 67 requests, collection-level Bearer auth via {{apiKey}} variable. Ready to import and run against api.cueapi.ai or a self-hosted instance via {{baseUrl}}.

Public Postman API Network upload deferred — pending Postman account / API key.

[argus-qa-ai]

All CI checks passing. Approved by Argus.

[govindkavaturi-art]

Closing as stale. Since this PR was opened on 2026-04-15, three meaningful changes landed on main that alter the OpenAPI surface:

• feat: add DELETE /v1/workers/{worker_id} #16 — DELETE /v1/workers/{worker_id}
• feat: verification modes + evidence fields + transport combo rejection (hosted parity) #18 — verification modes + inline evidence fields on executions
• feat: alerts with webhook delivery + outcome integration #20 — alerts webhook endpoints

The 67-request collection captured in this PR is missing the new endpoints and has stale schemas on the updated ones. Rather than rebasing/regenerating in-place here, close and open a fresh PR with a freshly regenerated collection when someone has bandwidth — the regeneration is mechanical (hit api.cueapi.ai/openapi.json → run through the postman-from-openapi converter).

Nothing wrong with the approach, just timing.