Batch migrations

Discover solution directories and exported MSI packages recursively

Point solutionsRoot at an estate directory. A directory with a root-level .sln becomes one batch solution; each .msi becomes another. Explicit solution entries can override discovered entries with the same ID.

migration:
  mode: batch
  reportDirectory: ./reports
  batch:
    solutionsRoot: ../biztalk
    continueOnError: true
    concurrency: 1

li precheck --config migration.config.batch.yaml
li convert --config migration.config.batch.yaml --batch \
  --log-file ./logs/batch.log

• Concurrency is currently limited to one.
• Resume: keep batch state, reports, generated repositories, and conversion checkpoints if a run may need to resume. Add --resume only after a batch state file exists, not on the first run.
• One solution: add --solution orders to run one configured solution through the same pipeline with per-stage token notifications.
• Cost: a full batch automatically estimates Azure cost after packaging; --conversion-only omits that stage. Resume can reuse an existing cost summary without refreshing prices or assumptions; rerun li estimate-cost explicitly when those inputs change.
• No deployment: batch conversion does not deploy to Azure.