From dd28ac6223b3b58c4b3d26c1de972de30dea7f17 Mon Sep 17 00:00:00 2001 From: Eyejoker Date: Tue, 31 Mar 2026 09:03:20 +0900 Subject: [PATCH] fix: fallback to proceed on unrecognized arbiter verdict MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Previously unknown verdicts caused arbiter_escalated (task terminated). Now falls back to proceed so the loop continues — a parse failure should not kill the task. --- src/paired-execution-context.ts | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/paired-execution-context.ts b/src/paired-execution-context.ts index 27448f4..3c5357b 100644 --- a/src/paired-execution-context.ts +++ b/src/paired-execution-context.ts @@ -738,13 +738,18 @@ export function completePairedExecutionContext(args: { logger.info({ taskId }, 'Arbiter escalated to user — task completed'); break; default: - // Unknown verdict — treat as escalate + // Unknown verdict — fallback to proceed so the loop continues. + // Stopping the task on a parse failure is worse than letting it run. updatePairedTask(taskId, { - status: 'completed', + status: 'active', + round_trip_count: Math.max(0, ARBITER_DEADLOCK_THRESHOLD - 1), arbiter_verdict: 'unknown', - completion_reason: 'arbiter_escalated', updated_at: now, }); + logger.warn( + { taskId, summary: args.summary?.slice(0, 200) }, + 'Arbiter verdict unrecognized — falling back to proceed', + ); break; } }