jade-core-retry-router

Failed JADE migration rules are routed back into a retry queue by analyzing fix results, semantic diffs, and build logs to classify failures, preserve attempt counts, and requeue eligible rules with priority ordering.

When the retry budget is exhausted, the migration rule is escalated for human review by creating an escalation ledger record and generating an ACTION_REQUIRED.md file detailing the stalled rule attempts.

Failure classification for stalled migration attempts reads fix results, semantic diffs, and build logs to identify build errors, semantic mismatches, stalled retries, and missing artifacts before deciding to retry or escalate.

Yes, fix results, semantic diffs, and build logs are required inputs to classify verification gate breaks and batch failures, preserve monotonic attempt counts, and write routing outputs for the JADE pipeline.

Yes, retry routing applies to migration batch failures, verification gate breaks, and stalled rule attempts in the JADE pipeline, automatically requeuing eligible rules instead of aborting the workflow.

A single failed migration rule aborts the pipeline because without retry queue management and escalation handling, the system lacks failure classification and attempt tracking to isolate and requeue the broken rule.