CommandKit Legacy Migration

Activation guidance

Use only when legacy plugin usage already exists.

Required filesystem expectations

• legacy and modern structures may coexist during phased migration
• target end state uses src/app/commands/** and src/app/events/**

Execution workflow

1. Detect legacy dependencies and plugin usage.
2. Inventory parity requirements.
3. Migrate incrementally by domain/feature slices.
4. Remove legacy() only after parity validation.

Guardrails