Dual Edition Module Migration

When to apply

• A module must exist in both open-source and enterprise editions
• The user mentions src/opensource, enterprise/, Vite overlay, or edition-specific behavior
• A shared module needs to stay under src/opensource/..., but enterprise behavior must override it
• Old src/variant/... or src/opensource/variant/... facades need to be removed
• A migration must preserve the src/opensource import boundary

Core invariants

1. src/opensource is the shared source of truth

• Code under src/opensource/ is the default implementation
• src/opensource/ must not import commercial code
• If open-source needs a dependency, migrate that dependency too or degrade the feature
• If a file under src/opensource/ or enterprise/src/opensource/ imports a module outside the opensource tree, move that dependency into the current opensource closure instead of keeping a shim
• Do not pull private infrastructure such as keewoodClient or teamshareClient into src/opensource