⭐ Migration Approach

The Maven reactor is converted one file at a time — each file individually inspected against the Maven source and given its own decision (carry over as-is, convert, omit, or rewrite), never bulk-copied or run through an automated converter. Work proceeds bottom-up by dependency direction: build-logic conventions first, then leaf modules, then core domain, then extensions, then aggregation, then publishing.

See the migration pipeline diagram for current phase status, and todo.md for the full decision log.