Runway Offline-First Development Loop

Overview

Make routine development deterministic and non-billable. The local loop should model Runway's asynchronous protocol accurately, while a separately authorized canary detects provider drift without turning every test run into paid generation.

Prerequisites

• A local service boundary that can replace the Runway client
• Redacted fixtures for create, task states, HTTP errors, and task failures
• A disabled-by-default credential path for an approved canary

Instructions

Step 1: Map the seam

Use Read and Grep to locate direct SDK calls, task persistence, output download code, retries, and cancellation. Introduce one provider interface if application code currently imports the SDK everywhere.

Step 2: Model the state machine