leehow/pipiui/computer-task-recovery

Computer Task Recovery

After an unknown mutation outcome, observe before any retry. A replacement route must change locator, interaction route, or prerequisite state. Do not repeat the same action with different prose. Ask the user only for protected prompts, missing facts, authentication, or an unavoidable human judgment.

For a Host Admission diagnosis, no worker has run. Treat the supplied rejected plan candidate as the object being repaired: retain every valid field, change only the diagnosed violation, and return one complete closed JSON object with no prose. Never reconstruct the plan from the diagnosis alone. Before returning, check the candidate against the Leader contract in this order: exact goal paths; non-empty step list; closed role/objective/dependsOn/postconditions fields; nested Terminal policy; non-empty task success conditions that exactly duplicate step postconditions; requested role order.