Motivation

Published plugin packages currently sync required dependencies from internal workspaces, but the integrity command does not preserve whether a propagated dependency is optional. That makes it difficult to keep native, platform-specific packages optional when they are introduced by shared internal code.

Changes

• Teach dependency integrity to read internal workspace optionalDependencies.
• Propagate expected optional dependencies separately from required dependencies.
• Keep required dependencies authoritative when the same package appears as required in one workspace and optional in another.
• Reuse the same mismatch reporting/apply flow for both dependency sections.

QA Instructions

yarn cli integrity
git diff --check