1.3 Boundaries and ecosystem
Ordered scope
Section titled “Ordered scope”| Order | Item | Acceptance |
|---|---|---|
| 1 | Package and runtime boundary audit | Dependency direction, lifecycle ownership, worker assets, SSR behavior and exports are documented and enforced |
| 2 | Real consumer fixtures | Vite, Webpack/Rspack, Next.js, headless Node and no-build ESM consumers pass install/build/runtime checks |
| 3 | Package-size budgets | Per-package and representative-app gzip budgets fail CI on regression |
| 4 | Framework bindings | React/Vue/Svelte bindings remain thin lifecycle/state adapters over the already exercised SDK boundary |
| 5 | Reference UI components | Accessible timeline, properties, media, player and subtitle primitives; not a full editor product |
| 6 | Measured hot-path optimization | SIMD/WASM work lands only behind unchanged semantics and with benchmark/golden evidence |
Framework bindings are intentionally after boundary and consumer validation. Otherwise each binding would fossilize unstable lifecycle decisions and multiply migration cost.