2.0 Stabilization

2.0.0 is a future stable release, not a container for unfinished 1.x promises. It may start only after deferred capability claims are either delivered or explicitly removed from the product contract.

Ordered program

Order	Work	Exit condition
0	Close or descope 1.x gaps	Physical-device, codec fallback, long-session, subtitle, analysis and WebGPU claims have an explicit delivered/deferred decision
1	Define Project v2 and migration	Immutable schema IDs, compatibility fixtures, deterministic v1→v2 migration and versioned loss reports exist before v2 authoring APIs
2	Define the Render IR v2 bridge	Project remains a persistent editing model and Render IR remains an execution model; their versioned compiler boundary has golden semantic tests
3	Clean package boundaries	Ownership, dependency direction, exports and deprecations are documented and pass package-consumer tests
4	Exercise framework/host bindings	Reference integrations validate that package boundaries and lifecycle APIs work outside repository tests
5	Freeze public APIs	API snapshots freeze only after schema, IR, package boundaries and bindings have been exercised
6	Full certification and stable release	Device matrix, golden data, soak, security, package reproducibility and migration replay pass for one bound source manifest

Non-negotiable design rules

• Project and Render IR are not merged into one object model. Project is durable/editable; Render IR is immutable, normalized and execution-oriented.
• Every schema revision gets a new immutable URI and version. Published schema identities are never edited in place.
• Migration precedes removal. Unsupported content fails closed and produces a machine-readable loss report.
• API freeze follows real consumer integrations; it does not precede them.
• latest moves to 2.0 only after the complete bound evidence set and an independent blocker review pass.