From 4110f8001b25bac9343a3dba7398e677913d2b46 Mon Sep 17 00:00:00 2001 From: Dotta Date: Thu, 10 Sep 2026 17:09:11 -0500 Subject: [PATCH] test(runner): accept startup detection of damaged resume input Keep the archive, retained-input, same-task and successful-recovery assertions while accepting either startup or attach as the point that detects the deliberately corrupted fixture. Co-Authored-By: Paperclip --- .../services/native-runtime/native-session-resume.test.ts | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/server/src/services/native-runtime/native-session-resume.test.ts b/server/src/services/native-runtime/native-session-resume.test.ts index ba66f3c25f..31bf40ba95 100644 --- a/server/src/services/native-runtime/native-session-resume.test.ts +++ b/server/src/services/native-runtime/native-session-resume.test.ts @@ -1017,8 +1017,11 @@ const recoveryFakeCodex = resolve( normalizedSessionId, }); expect(continuity).toMatchObject({ - reason: expect.stringContaining( - "run.attach requires a settled Codex provider session", + // The deliberately corrupt input may be rejected during provider + // startup or by run.attach after startup has reported the failure. + // Both paths must archive the same damaged epoch and recover below. + reason: expect.stringMatching( + /run\.attach requires a settled Codex provider session|semantic tool input content digest does not match its transmitted input/, ), previousDriverSessionId: checkpoint.sessionId, });