Coordinate Recover

Use coordinate_agents_recover_inspect, coordinate_agents_task_status, and coordinate_agents_task_resume for single-Task recovery. For a Task Graph, use coordinate_agents_task_graph_recover, coordinate_agents_task_graph_resume, coordinate_agents_task_graph_stop, and coordinate_agents_task_graph_cleanup. Recovery is facts-first and never an automatic retry. If MCP is unavailable, or the user explicitly requests debugging, let <skill-dir> be the absolute directory containing this loaded SKILL.md and use the bundled fallback:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" ...

The normal Plugin path starts with coordinate_agents_recover_inspect, followed by coordinate_agents_task_status or coordinate_agents_task_resume only when the recovery decision requires them. The following commands are fallback/debug syntax only:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task status --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" status --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" agent doctor --root "<repository>" --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-recover --root "<repository>" --id task-... --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-resume --root "<repository>" --id task-... --subtask <subtaskId> --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-stop --root "<repository>" --id task-... --json
node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task graph-cleanup --root "<repository>" --id task-... --json

Inspect the Task's lastError, the bounded runtime artifact, Agent Bus state, the sessionId Session status/inspect facts, and any matching commit or evidence. Explain the concrete error code and the smallest repair. Session inspection is read-only: do not restart, replay input, attach to a different PID, or resume the Task while collecting facts. Do not claim a missing capability as a successful result.

Only after the user explicitly asks to continue, invoke:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task resume --root "<repository>" --id task-... --json

task resume only clears the explicit recovery gate; it does not launch an Implementer. After the user confirms the repair, use task dispatch so the Task API performs executable validation, Bus handoff, launch, and state/error propagation as one operation.

For graph recovery, task graph-recover inspects durable Session, worktree, commit, and evidence records and records an interrupted FAILED subtask only when no healthy Session or verified completion exists. It never infers success from filenames or prose. task graph-resume is a separate explicit decision: it reuses a verified healthy Runtime-owned Session/worktree, or returns an exited/failed Session to READY for a later explicit graph dispatch. Failed prerequisites keep dependents BLOCKED until this valid recovery path runs. Use task graph-stop to mark active graph work STOPPED and close only Runtime-owned Sessions, followed by task graph-cleanup when needed. Both operations use bounded, ownership-checked cleanup and preserve user worktrees, branches, refs, commits, and evidence; repeated recovery/resume/stop/cleanup calls are idempotent.

TASK_NOT_FOUND, STALE_CLAIM, AGENT_EXIT_NONZERO, AGENT_TIMEOUT, and AUTH_REQUIRED remain facts to report; they do not authorize silent retries.