eforge-recover

# /eforge:recover Inspect the recovery analysis for a failed PRD and act on the verdict — re-queue, split into a successor PRD, or archive the original. ## Workflow Call `eforge_queue_list` to discover failed PRDs, read the recovery sidecar to surface the verdict and rationale, confirm the action with the user, and call `eforge_apply_recovery` to execute. Never auto-apply — always confirm. ## Steps ### Step 1: Identify the Failed PRD If the user supplied a `<prdId>` argument, use it directly and skip to Step 2. Otherwise, call `eforge_queue_list` (no parameters) and filter the response for items where `status === 'failed'`. Present the list to the user and ask which one to recover. If no failed PRDs are found, tell the user: > No failed PRDs found. Use `/eforge:status` to check the current build state. **Stop here** if no failed PRDs exist. ### Step 2: Read the Recovery Sidecar Call `eforge_read_recovery_sidecar` with `{ prdId }`. - If the tool returns a 404 or the response contains a `recoveryError` field, offer to run the recovery analysis: > No recovery analysis found for `{prdId}`. Would you like me to run the analysis now? (yes / no) If the user agrees, call `eforge_recover` with `{ setName, prdId }` — source `setName` from `summary.setName` in a prior sidecar if available, otherwise ask the user to supply it. Then loop back to Step 2. If the user declines, stop here. - If the sidecar is present, continue to Step 3. ### Step 3: Render the Verdict Di...