jade-core-rule-dispatcher

To route migration rules, the dispatcher reads batch and manifest artifacts, resolves recipe mappings from recipe-registry.json, and invokes the appropriate recipe subprocess for each rule task. It records the fix result and updates the batch status to keep artifacts as the source of truth.

Sequential migration artifact tracking is handled by processing one rule task at a time from the batch loop, ensuring transformations stay deterministic. The dispatcher writes atomic JSON result records per task and updates the batch status after each recipe execution.

Fallback handling occurs during sequential transformation runs when the dispatcher resolves recipe mappings from recipe-registry.json. If a mapping is missing, it invokes a fallback handler instead of failing, ensuring the migration pipeline continues processing remaining rule tasks.

Yes, recipe-registry.json is required to resolve rule-to-recipe mappings before invoking recipe subprocesses. The dispatcher relies on this registry to select the correct recipe skill or fallback handler for each migration rule task in the batch.

No, the dispatcher does not embed any transform logic. It strictly routes rule tasks to the correct recipe skill, executes it safely via subprocess, and records the outcome, keeping recipe implementations separate from the dispatch mechanism.

Atomic JSON writes ensure per-task fix results are recorded safely without corruption during batch processing. The dispatcher writes these records to maintain artifact integrity, allowing the migration pipeline to recover and trace outcomes deterministically if a subprocess fails.