@giveitsmaller/contracts 0.84.0 → 0.86.0

package/openapi/api.yaml

@@ -103,7 +103,7 @@ info:
     of truth instead of hardcoding magic numbers. A runtime
     `GET /api/uploads/limits` endpoint for dynamic discovery
     (per-tier / per-environment overrides) is a deferred follow-up.
-  version: 2.219.0
+  version: 2.221.0
   contact:
     name: API Support
 
@@ -1098,13 +1098,12 @@ paths:
         bad ones before submit.
 
         Per ticket [I28 `KbVAnGCm`](https://trello.com/c/KbVAnGCm).
-        `availability: planned`. The upload-probe Lambda exists and runs
-        asynchronously when an upload is finalised; this endpoint returns
-        the cached result when one exists and `feature_not_available`
-        (422) when none does yet. It does not invoke the probe itself.
-        (A `planned` endpoint that answers 200 is inconsistent with the
-        availability taxonomy; the flip decision is tracked separately,
-        card `kAT0i5A6`.) Per Tension 1 (ADR-0001 §1.3).
+        `availability: beta` (card `kAT0i5A6`, on a production
+        observation, 2026-10-01). The upload-probe Lambda runs
+        asynchronously when an upload is finalised (measured on prod:
+        about 3 s for a 3 s clip); this endpoint returns the cached
+        result when one exists and a 422 when none does yet. It does not
+        invoke the probe itself.
 
         **SDK helper intent.** SDKs are expected to expose a
         `client.preflight_clips([file_ids])` helper that compiles to N
@@ -1128,7 +1127,7 @@ paths:
       x-identity-scoped: true  # ownership-scoped per ADR-0016 D3
       tags:
         - Upload
-      x-availability: planned
+      x-availability: beta
       parameters:
         - name: id
           in: path
@@ -1223,14 +1222,49 @@ paths:
                 $ref: '#/components/schemas/ErrorEnvelope'
         '422':
           description: |
-            No probe result is cached for this upload yet (the probe runs
-            asynchronously after the upload is finalised) — returned as
-            `FeatureNotAvailableResponse` with `error_type:
-            feature_not_available`. Per Tension 1 (ADR-0001 §1.3).
+            No probe result is cached for this upload. Discriminated on
+            `error_type` (ADR-0018), card
+            [`tRVvMOvy`](https://trello.com/c/tRVvMOvy):
+            - `probe_not_ready` → `UploadProbeNotReadyResponse`: the probe
+              has not landed YET. **Retry** (`Retry-After` when present).
+            - `probe_not_applicable` → `UploadProbeNotApplicableResponse`:
+              this upload's type is never probed (e.g. an image, whose
+              metadata is read inline at upload). **Terminal — do not
+              retry**; no result will ever exist.
+            - `feature_not_available` → `FeatureNotAvailableResponse`
+              with `violations[].availability: planned`:
+              **TRANSITIONAL.** What the server sends today for BOTH
+              causes above. It predates this endpoint's move to `beta`
+              and does NOT mean the endpoint is unavailable. Retry it
+              **with a ceiling** — it can be the terminal case. The
+              server switches to the two arms above only after an SDK
+              release that reads them is published; when this arm is
+              removed is an owner decision.
+          headers:
+            Retry-After:
+              required: false
+              description: |
+                Optional, on the `probe_not_ready` branch only: suggested
+                seconds before the next poll. Delta-seconds (RFC 9110).
+                Absent ⇒ poll on your own backoff (measured on prod
+                2026-10-01: about 3 s from upload to a result for a 3 s
+                clip).
+              schema:
+                type: integer
+                minimum: 0
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/FeatureNotAvailableResponse'
+                oneOf:
+                  - $ref: '#/components/schemas/UploadProbeNotReadyResponse'
+                  - $ref: '#/components/schemas/UploadProbeNotApplicableResponse'
+                  - $ref: '#/components/schemas/FeatureNotAvailableResponse'
+                discriminator:
+                  propertyName: error_type
+                  mapping:
+                    probe_not_ready: '#/components/schemas/UploadProbeNotReadyResponse'
+                    probe_not_applicable: '#/components/schemas/UploadProbeNotApplicableResponse'
+                    feature_not_available: '#/components/schemas/FeatureNotAvailableResponse'
         '429':
           description: |
             Rate limit exceeded. Probe is rate-limited independently
@@ -2031,7 +2065,7 @@ paths:
               Per-violation `required_tier` names the tier (if any)
               whose `per_tier_constraints` would accommodate the
               request (`null` = no tier resolves, e.g. enterprise
-              already at the 120 GB hard ceiling). Distinct from
+              already at its hard ceiling). Distinct from
               `TierRestrictionResponse` (403, request-level upload
               quota — see [ADR-0012](../docs/decisions/0012-processing-class-band-reject-envelope.md)
               for the band-vs-tier split). Per ADR-0001 §F6
@@ -2121,7 +2155,8 @@ paths:
                 before re-polling the upload probe and retrying the
                 workflow. **A guest (no credential) cannot poll the probe**
                 (`POST /api/uploads/{id}/probe` requires sign-in): it retries
-                the create itself. A `probe_pending` refusal does not count
+                the create itself. After `video.probe_wait_bound_seconds` from the upload
+                the create proceeds without a duration (guest unknown-duration rule). A `probe_pending` refusal does not count
                 against the guest per-minute create limit and reserves no
                 guest allowance credits (`schemas/anonymous-policy.yaml`
                 `video`). Delta-seconds (RFC 9110), mirroring the 429
@@ -3695,29 +3730,13 @@ paths:
         a **409** — cancel it first (`POST /api/workflows/{id}/cancel`) or wait
         for it to finish. Archiving does NOT change the workflow's status; it
         stays terminal and the response echoes it unchanged.
-      # ⚠️ NO PUBLIC HTTP ROUTE EXISTS FOR THIS. Downgraded to `planned`
-      # 2026-08-12 (yi4TDKVJ, raised by sdks + codex) on POSITIVE evidence, as
-      # standing policy 3 requires — not on an absent attestation, which policy
-      # 4 says is not enough:
-      #   * no `#[Route(...)]` matching archive/restore anywhere in
-      #     compression_api's `src/`;
-      #   * no `api/workflows/{id}/archive` or `/restore` path in `src/` or
-      #     `config/`;
-      #   * verified independently by sdks (named commit) and by codex reading
-      #     the list controller and its repository.
-      #
-      # ⚠️ CORRECTION TO THE RELAYED EVIDENCE, because it changes the ticket
-      # rather than the verdict: the claim reaching this repo was that a grep
-      # for `archiveWorkflow|/archive|archived` over `src` and `config`
-      # "returns NO OUTPUT". IT DOES NOT — `ArchiveWorkflowCommand`,
-      # `ArchiveWorkflowCommandHandler` and a `RestoreWorkflow` command all
-      # EXIST, and there is an ADMIN CRUD controller that archives. So this is
-      # **implemented in the application layer and not exposed on the public
-      # API**, which is a different thing from "nothing behind it". The verdict
-      # is unchanged — an unroutable capability is unreachable, so `planned` is
-      # correct — but anyone scoping the work should know a handler already
-      # exists.
-      x-availability: planned
+      # ROUTE ADDED: compression_api #804 (merge 85dd49fa, 2026-09-30) serves
+      # the public POST route, owner-scoped (ownership denial 404). It was
+      # `planned` since 2026-08-12 (yi4TDKVJ) because no route existed. Now
+      # `beta` on a staging customer-path round-trip, then `stable` on a PROD
+      # round-trip (e2e, 2026-09-30, api build 1.16.0,
+      # availability/prod-verification-log.yaml).
+      x-availability: stable
       operationId: archiveWorkflow
       security: [{bearerAuth: []}, {sessionAuth: []}]  # required (explicit 401 in response set)
       x-identity-scoped: true  # workflow-ownership-scoped per ADR-0016 D3
@@ -3809,29 +3828,13 @@ paths:
         `status` is the workflow's unchanged status (any `WorkflowStatus`
         value), not a fixed terminal subset. There is no 409: un-archiving is
         always safe.
-      # ⚠️ NO PUBLIC HTTP ROUTE EXISTS FOR THIS. Downgraded to `planned`
-      # 2026-08-12 (yi4TDKVJ, raised by sdks + codex) on POSITIVE evidence, as
-      # standing policy 3 requires — not on an absent attestation, which policy
-      # 4 says is not enough:
-      #   * no `#[Route(...)]` matching archive/restore anywhere in
-      #     compression_api's `src/`;
-      #   * no `api/workflows/{id}/archive` or `/restore` path in `src/` or
-      #     `config/`;
-      #   * verified independently by sdks (named commit) and by codex reading
-      #     the list controller and its repository.
-      #
-      # ⚠️ CORRECTION TO THE RELAYED EVIDENCE, because it changes the ticket
-      # rather than the verdict: the claim reaching this repo was that a grep
-      # for `archiveWorkflow|/archive|archived` over `src` and `config`
-      # "returns NO OUTPUT". IT DOES NOT — `ArchiveWorkflowCommand`,
-      # `ArchiveWorkflowCommandHandler` and a `RestoreWorkflow` command all
-      # EXIST, and there is an ADMIN CRUD controller that archives. So this is
-      # **implemented in the application layer and not exposed on the public
-      # API**, which is a different thing from "nothing behind it". The verdict
-      # is unchanged — an unroutable capability is unreachable, so `planned` is
-      # correct — but anyone scoping the work should know a handler already
-      # exists.
-      x-availability: planned
+      # ROUTE ADDED: compression_api #804 (merge 85dd49fa, 2026-09-30) serves
+      # the public POST route, owner-scoped (ownership denial 404). It was
+      # `planned` since 2026-08-12 (yi4TDKVJ) because no route existed. Now
+      # `beta` on a staging customer-path round-trip, then `stable` on a PROD
+      # round-trip (e2e, 2026-09-30, api build 1.16.0,
+      # availability/prod-verification-log.yaml).
+      x-availability: stable
       operationId: restoreWorkflow
       security: [{bearerAuth: []}, {sessionAuth: []}]  # required (explicit 401 in response set)
       x-identity-scoped: true  # workflow-ownership-scoped per ADR-0016 D3
@@ -6658,6 +6661,7 @@ paths:
                           effective: 128849018880
                           tier_default: 107374182400
                           overridden: true
+                          ceiling_basis: unproven
                         max_total_input_size_bytes:
                           effective: 120000000000
                           tier_default: 120000000000
@@ -8660,6 +8664,18 @@ components:
           description: |
             The tier's default cap for this limit, in the same unit as
             `effective` (already public via the tier model).
+        ceiling_basis:
+          # OPTIONAL in this expand step (xApHyTY3, from api 5pyX06rE); api
+          # emits it after this publishes.
+          $ref: '#/components/schemas/CeilingBasisValue'
+          description: |
+            Whether `effective` is a PROVEN value (owner decision 607(d) /
+            610(4)(d)). `unproven` (e.g. the Max and Enterprise
+            `max_upload_size_bytes`): the API still enforces it; present it
+            as "up to X (not yet verified)" (FORMAT.md obligation 10). ⛔
+            **ABSENT IS NOT `proven`** — it means the server made no claim,
+            so a consumer must not advertise the value as verified on its
+            strength.
         overridden:
           type: boolean
           description: |
@@ -10005,6 +10021,14 @@ components:
               description: |
                 Which guest limit was exceeded. OPEN: a consumer that does
                 not know a value shows the envelope's localised message.
+                `video_duration_seconds` is only ever sent for a MEASURED
+                duration: a guest video whose duration is unknown (the probe
+                could not measure one, or had not landed within
+                `video.probe_wait_bound_seconds` of the upload) is allowed, not
+                refused, as an ordinary guest create that reserves allowance
+                credits and counts against the per-minute create limit (owner
+                decision 648, `schemas/anonymous-policy.yaml`
+                `video.unknown_duration`).
               type: string
               x-enum-openness: open
               enum:
@@ -10121,6 +10145,44 @@ components:
               items:
                 $ref: '#/components/schemas/FeatureViolation'
 
+    UploadProbeNotReadyResponse:
+      description: |
+        422 from `POST /api/uploads/{id}/probe`: the upload's server-side
+        probe has not landed YET. Retryable — poll again after
+        `Retry-After` (when present) or your own backoff. Distinct from
+        `probe_pending` (`ProbePendingResponse`, workflow-create, carries
+        `job_ref`) so each code keeps one shape. Card
+        [`tRVvMOvy`](https://trello.com/c/tRVvMOvy).
+      allOf:
+        - $ref: '#/components/schemas/ErrorEnvelope'
+        - type: object
+          required:
+            - error_type
+          properties:
+            error_type:
+              type: string
+              enum:
+                - probe_not_ready
+              description: Discriminator for the probe endpoint's 422 oneOf. Always `probe_not_ready`.
+
+    UploadProbeNotApplicableResponse:
+      description: |
+        422 from `POST /api/uploads/{id}/probe`: this upload's type is
+        never probed (e.g. an image, whose metadata is read inline at
+        upload), so no result will ever exist. **Terminal — do not
+        retry.** Card [`tRVvMOvy`](https://trello.com/c/tRVvMOvy).
+      allOf:
+        - $ref: '#/components/schemas/ErrorEnvelope'
+        - type: object
+          required:
+            - error_type
+          properties:
+            error_type:
+              type: string
+              enum:
+                - probe_not_applicable
+              description: Discriminator for the probe endpoint's 422 oneOf. Always `probe_not_applicable`.
+
     ProbePendingResponse:
       description: |
         422 response on `POST /api/workflows` when the probe-pending
@@ -10336,7 +10398,7 @@ components:
             server SHOULD set `required_tier` to that tier — consumers
             can offer an upgrade nudge. `null` (or omitted) means
             **no tier resolves** the overflow (e.g. enterprise already
-            hits the 120 GB hard ceiling per
+            hits its hard ceiling per
             [ADR-0011](../docs/decisions/0011-per-tier-processing-class-constraints.md)
             D1–D4).
 
@@ -10388,7 +10450,7 @@ components:
         `required_tier` on each `ProcessingClassBandViolation` names
         the tier (if any) whose `per_tier_constraints` would
         accommodate the request; `null` means terminal (e.g. enterprise
-        already at the 120 GB hard ceiling).
+        already at its hard ceiling).
 
         Per
         [ADR-0012](../docs/decisions/0012-processing-class-band-reject-envelope.md)
@@ -10847,8 +10909,9 @@ components:
             Recommended chunk size in bytes for multipart upload
             chunks (16 MiB / 16,777,216 bytes — 1024-based). Raised
             from 5 MiB by CON-1 (ADR-0011): S3 caps a multipart
-            upload at 10,000 parts, and the Enterprise envelope is a
-            120 GB hard ceiling. At 16 MiB a 120 GiB object needs
+            upload at 10,000 parts, and the Enterprise envelope was
+            sized at 120 GB (the per-file ceiling is now 100 GiB, owner
+            649(2), which fits with margin). At 16 MiB a 120 GiB object needs
             7,680 parts (≤ 10,000, inside AWS's 16–64 MB recommended
             band); 5 MiB would need 24,576 and 10 MiB 12,288 — both
             exceed the S3 limit. **Wire-incompatible change** — SDKs
@@ -14886,6 +14949,29 @@ components:
             requested `target_size_bytes`. `false` is an honest best-effort outcome
             (target unreachable at min quality), NOT a failure. Present only for a
             target_size output. Mirrors `OperationMetrics.target_size_met`.
+        already_optimal:
+          type: boolean
+          description: |
+            OPTIONAL. `true` when this file IS the original input, returned
+            unchanged because compressing it would not have made it smaller
+            (owner decision 645(4): a success; the no-charge rule and its
+            current rollout — the API still charges until it ships, and only
+            short-form compress returns this today — are stated once, on
+            `OperationResultMetadata.already_optimal`). Same value as
+            `OperationResultMetadata.already_optimal` on `/status`, projected
+            here so a per-file result built from `/downloads` does not need a
+            second read (sdks `bYOCX61m`). Absent or `false`: an ordinary
+            output; treat the two the same. Mirrors
+            `OperationMetrics.already_optimal`.
+          example: true
+        already_optimal_kind:
+          type: string
+          enum: [not_smaller]
+          description: |
+            OPTIONAL, only with `already_optimal: true`. Same value and meaning
+            as `OperationResultMetadata.already_optimal_kind`; absent or unknown:
+            neutral "already optimised" copy.
+          example: not_smaller
         measured_quality:
           type: number
           format: double
@@ -16090,8 +16176,8 @@ components:
         Recursive condition node (the `Cond` field-token model, ADR-0024
         §2). Exactly ONE form per node — a boolean combinator (`all` /
         `any` / `not`) OR a single leaf test. A leaf tests one `field`
-        token with exactly one operator (`equals` / `in` / `isSet`),
-        except `opSelected` which is a standalone leaf asserting a
+        token with exactly one operator (`equals` / `in` / `isSet` /
+        `numericZero`), except `opSelected` which is a standalone leaf asserting a
         sibling operation of that type is present in the job. Consumers
         compute field tokens locally from the resolved request (no new
         wire field). Modelled as a `oneOf` of the valid forms (each
@@ -16154,6 +16240,33 @@ components:
               description: |
                 Leaf test — asserts `field` is present/set. Only the
                 positive form is used; negate via a wrapping `not` node.
+        - type: object
+          additionalProperties: false
+          required: [field, numericZero]
+          properties:
+            field:
+              type: string
+              description: Field token under test.
+            numericZero:
+              type: boolean
+              enum: [true]  # not `const` — ADR-0010 (generators mis-emit boolean const)
+              x-matches: '^0+(\.0+)?(px|%)$'
+              description: |
+                Leaf test — `field` is an offset whose number is zero,
+                whatever its spelling (`0px`, `00%`, `0.000px`). True iff
+                the String-coerced value fully matches `x-matches`; any
+                other value is false, including `-0`, `+0` and `.0`,
+                which the offset pattern `^\d+(\.\d+)?(px|%)$` refuses
+                anyway. An unresolved field behaves as it does for
+                `equals` / `in`. This regex is NORMATIVE. api's
+                `float == 0` test agrees with it on every offset a float
+                represents faithfully; it differs only where a cast
+                underflows (hundreds of fractional zeros before a non-zero
+                digit), which api reads as zero and this leaf does not.
+                Like every operator here, its semantics live in this
+                schema, not in `operation-capabilities.json`. Only the positive
+                form is used; negate via a wrapping `not` node. Card
+                `6jTnFnTh`: replaces lexical `in` lists of zero spellings.
         - type: object
           additionalProperties: false
           required: [opSelected]
@@ -17017,14 +17130,24 @@ components:
           "up to X (not yet verified)". Each becomes `proven`, or is
           lowered to the largest passing value, after its staging corner run.
       additionalProperties:
-        type: string
-        # CLOSED: a consumer decides how to present the limit from it.
-        x-enum-openness: closed
-        enum: [proven, unproven]
+        $ref: '#/components/schemas/CeilingBasisValue'
       example:
         max_input_size_bytes: unproven
         max_input_duration: unproven
 
+    CeilingBasisValue:
+      type: string
+      description: |
+        Whether ONE declared ceiling is proven (owner decision 607(d)). The
+        single vocabulary for `CeilingBasis` (per-ceiling map on a group or
+        class) and `AccountLimitEntry.ceiling_basis` (one account limit).
+        `proven`: a recorded run passed at 95% or more of the value.
+        `unproven`: still ENFORCED, not yet run at the value; present as
+        "up to X (not yet verified)" (FORMAT.md obligation 10).
+      # CLOSED: a consumer decides how to present the limit from it.
+      x-enum-openness: closed
+      enum: [proven, unproven]
+
     ResolutionBand:
       type: string
       description: |

package/operation-capabilities/operation-capabilities.json

@@ -513,12 +513,7 @@
                       {
                         "not": {
                           "field": "image_watermark.margin_x",
-                          "in": [
-                            "0px",
-                            "0%",
-                            "0.0px",
-                            "0.0%"
-                          ]
+                          "numericZero": true
                         }
                       }
                     ]
@@ -532,12 +527,7 @@
                       {
                         "not": {
                           "field": "image_watermark.margin_y",
-                          "in": [
-                            "0px",
-                            "0%",
-                            "0.0px",
-                            "0.0%"
-                          ]
+                          "numericZero": true
                         }
                       }
                     ]
@@ -657,12 +647,7 @@
                       {
                         "not": {
                           "field": "text_watermark.margin_x",
-                          "in": [
-                            "0px",
-                            "0%",
-                            "0.0px",
-                            "0.0%"
-                          ]
+                          "numericZero": true
                         }
                       }
                     ]
@@ -676,12 +661,7 @@
                       {
                         "not": {
                           "field": "text_watermark.margin_y",
-                          "in": [
-                            "0px",
-                            "0%",
-                            "0.0px",
-                            "0.0%"
-                          ]
+                          "numericZero": true
                         }
                       }
                     ]
@@ -859,5 +839,5 @@
       "isAnimated": "maybe"
     }
   },
-  "schema_version": "2.219.0"
+  "schema_version": "2.221.0"
 }

package/operations/schemas/audio_overlay.yaml

@@ -110,11 +110,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         start_at:
           type: float
@@ -303,11 +303,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         start_at:
           type: float

package/operations/schemas/audio_watermark.yaml

@@ -75,11 +75,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         payload:
           type: string
@@ -181,11 +181,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         payload:
           type: string

package/operations/schemas/compress.yaml

@@ -1176,11 +1176,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         output_format:
           type: enum

package/operations/schemas/convert.yaml

@@ -349,11 +349,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         output_format:
           type: enum

package/operations/schemas/custom_luma.yaml

@@ -81,11 +81,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         duration:
           type: float

package/operations/schemas/split.yaml

@@ -530,11 +530,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         mode:
           type: enum

package/operations/schemas/thumbnail.yaml

@@ -130,9 +130,9 @@ operation:
             max_input_size_bytes: 5000000000       # 5 GB (Pro)
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
       # Same 16MP output-area wall as image (width*height <= max_output_pixels).
       # Extras (worker-enforced, prose-only): output dimensions are forced EVEN
       # (force_divisible_by=2 — the worker rounds an odd request down) and the

package/operations/schemas/transform.yaml

@@ -160,11 +160,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         rotate:
           type: enum

package/operations/schemas/video_text_watermark.yaml

@@ -123,11 +123,11 @@ operation:
             max_output_size_bytes: 5000000000
           per_tier_constraints:
             max:
-              max_input_size_bytes: 50000000000    # 50 GB (Max self-serve band)
-              max_output_size_bytes: 50000000000
+              max_input_size_bytes: 53687091200    # 50 GiB = api's Max upload cap (decision 677)
+              max_output_size_bytes: 53687091200
             enterprise:
-              max_input_size_bytes: 120000000000   # 120 GB (Enterprise enforced ceiling)
-              max_output_size_bytes: 120000000000
+              max_input_size_bytes: 107374182400   # 100 GiB = api's Enterprise upload cap (owner 649(2))
+              max_output_size_bytes: 107374182400
       options:
         text:
           type: string