chore(codegen): resync cloud client from EF 354b4cf4 (#6608)

* codegen: resync cloud client from EF 354b4cf4

* chore(codegen): keep page_motion_blur in the generated render request

The CLI already sends page_motion_blur (#6087), and experiment-framework adds
it to the public spec in a pending change. Keep it here so the sync does not
break the CLI typecheck in the meantime.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: James <james.russo@heygen.com>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

packages/cli/src/cloud/_gen/types.ts

@@ -317,9 +317,18 @@ export interface HyperframesRenderDetail {
   failure_message?: string | null;
   /**
    * Why billing refused a finished render: 'hf_usage_exhausted',
-   * 'hf_subscription_required' or 'api_key_required'. Present only when status
-   * is 'failed' for that reason; nothing was charged, so the render can be sent
-   * again on a HeyGen API key.
+   * 'hf_subscription_required' or 'api_key_required', for which nothing was
+   * charged and the render can be sent again on a HeyGen API key; or
+   * 'usage_limit_reached', when a usage limit a workspace admin set (the API
+   * key's credit limit or the member's usage limit) was reached; sending the
+   * render again does not help until the limit is raised or resets, and
+   * `failure_message` is the limit's own message; or
+   * 'chunk_frames_exceed_timeout_at_max_chunks', when the render is too long to
+   * export at its size (even split into the most cloud parts allowed, it would
+   * still take longer than the time limit): sending it again fails the same way
+   * until it is shortened or rendered at a lower resolution or frame rate, and
+   * `failure_message` says so. Present only when status is 'failed' for one of
+   * these reasons.
    */
   failure_code?: string | null;
 }