Skip to main content

Dependency ownership

Fased keeps the Agent and crypto path stable while optional runtimes move out of the default install. The checked source is config/dependency-ownership.json. Run the report:
pnpm release:check fails when a production dependency has no owner, has more than one owner, or remains in the ownership file after removal from package.json.

Delivery groups

Core protection

Package work must preserve these fresh-install checks:
Moving a dependency does not mean removing its feature. The feature gains an explicit install boundary and lifecycle state. The component catalog reports not-installed, configured, ready, or error instead of showing a setup field as proof that its runtime exists.

Extraction order

  1. Advanced channel SDKs that serve one channel family.
  2. Browser libraries and the system browser boundary.
  3. Media and speech runtimes.
  4. Native local-memory dependencies.
  5. Provider-specific SDKs.
Each extraction needs a packed-core smoke, an add-on smoke, and a docs update. Do not combine those moves into one release-sized change.