Attach a direct-upload source-code revision (multipart)

POST 
/api/v1/assessments/:assessment_id/revisions/upload

Attach a fix_attempt revision from a directly uploaded archive.

Multipart counterpart to POST /assessments/{id}/revisions. The bytes are extracted inline (no draft pre-upload + archive_id round-trip), persisted under the revision's content-addressed object storage key, and the assessment's current_revision_id is flipped to the new head.

Head-SHA short-circuit: when the freshly-extracted inner-tar SHA matches the current head, returns the existing head row unchanged — no new revision row, no object storage PUT. Identical-to-historical (not head) still creates a new row by design (rollback semantics).

Same gates as /revisions: the fix verification flag release, source:upload_zip + assessments:update scopes, manager-or-above role,. Rate-limit tier file_upload.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.