Runway SDK and Model Contract Migration

Overview

A Runway upgrade can change client types, model availability, allowed fields, output behavior, cost, latency, and quality at once. Preserve operation and task compatibility while migrating from retired identifiers through explicit per-model contracts and controlled comparisons.

Prerequisites

• Current dependency lock, model/request inventory, and task-state schema
• Target SDK changelog, API reference, models, and pricing evidence
• Representative fixtures, canary budget, and rollback owner

Instructions

Step 1: Inventory the current surface

Use Read and Grep to find SDK imports, raw endpoints, version headers, model identifiers, ratio and duration literals, wait helpers, error classes, task persistence, output handling, and docs.

Step 2: Define the target contract