openapi: align asset download/export 202 status enum with runtime + sibling schemas

CodeRabbit caught a vocabulary mismatch: the two new 202 response schemas
declared `[pending, running, completed, failed]` while the rest of the same
spec uses `[created, running, completed, failed]` for the identical task
lifecycle (download/export progress WebSocket events, /api/tasks, TaskEntry,
TaskResponse — 4 sites total). Cloud's runtime emits `created` on initial
creation (AssetDownloadResponseStatusCreated; task.Status sourced from the
DB enum whose initial value is Created). `pending` would have introduced a
fifth, contradictory vocabulary for the same lifecycle and pushed the spec
further from the implementation it is meant to align with.

Followup tracked separately: extract a shared TaskStatus enum so all five
sites move in lockstep instead of needing per-site edits.
This commit is contained in:
Matt Miller 2026-05-22 14:24:20 -07:00
parent 25ddeedabd
commit bd39960793

View File

@ -2358,8 +2358,8 @@ paths:
description: ID of the download task; use to poll status.
status:
type: string
enum: [pending, running, completed, failed]
description: Current task status (typically `pending` on initial creation).
enum: [created, running, completed, failed]
description: Current task status (typically `created` on initial creation).
message:
type: string
description: Human-readable task message.
@ -2418,8 +2418,8 @@ paths:
description: ID of the export task; use to poll status.
status:
type: string
enum: [pending, running, completed, failed]
description: Current task status (typically `pending` on initial creation).
enum: [created, running, completed, failed]
description: Current task status (typically `created` on initial creation).
message:
type: string
description: Human-readable task message.