Step 3 of upload: confirm uploaded files

Confirms slots whose bytes you have PUT to S3 (up to 50 per call). For each id the server checks the file exists in S3, records its real size, and then:

• photos move to indexing and face indexing starts in the background (asynchronous; the photo becomes findable by selfie once indexing finishes);
• videos move straight to completed.

Results come back per photo in confirmed[] with HTTP 200 even when some items fail; check each status/reason. Failure reasons: not_found, not_owned, already_processed (status is then the current one), s3_object_missing (the PUT never landed), upload_exceeds_size_limit (over 100 MB for a photo or 1 GB for a video; the file is deleted), video_storage_limit_exceeded, video_storage_check_failed, size_exceeds_album_quality: ..., db_update_failed: ....

Optional dimensions: send the rendered width/height per photo when you resized before upload. They are stored and checked against the album quality (long edge over the cap by more than 2 px fails with size_exceeds_album_quality). Without them the server reads the dimensions from the stored JPEG or PNG and applies no quality check. original_size_bytes (the file size before you resized it) is what the plan's storage meter counts, never less than the stored size.