[Epic] Phase 16 — Engine and strategy expansion

[vrabbi]

Goal

Extend what the engine can reason about, driven by real migrations rather than completeness.

The Strategy enum and the discriminated ConversionRule union were built so each addition stays contained — a new strategy is a *Params type, an Op, a compile resolver, webhook validation, a CLI fixture, and a docs page. That discipline is what has kept 29 strategies coherent, and it should not be relaxed here.

Note that the highest-value engine change in the whole review — required-field satisfaction analysis — lives in Phase 12 (#12.4) rather than here, because it pairs with output validation.

Scope

Sub-issues are tracked as native GitHub sub-issues of this epic.

References

https://github.com/TeraSky-OSS/declarative-conversion-operator/blob/main/docs/proposals/next-phases.md

---

Generated by Claude Code