From 4ae71b2a15acb440bd4606d7911527ae1c0c8f34 Mon Sep 17 00:00:00 2001 From: gsxdsm Date: Tue, 7 Jul 2026 08:37:04 -0700 Subject: [PATCH] test(engine): pin FN-4944 already-on-main fast-path noop log in post-finalize test --- ...ost-finalize-verification-noop-status-write.test.ts | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/packages/engine/src/__tests__/reliability-interactions/post-finalize-verification-noop-status-write.test.ts b/packages/engine/src/__tests__/reliability-interactions/post-finalize-verification-noop-status-write.test.ts index 1608dfa451..1ed5948c1f 100644 --- a/packages/engine/src/__tests__/reliability-interactions/post-finalize-verification-noop-status-write.test.ts +++ b/packages/engine/src/__tests__/reliability-interactions/post-finalize-verification-noop-status-write.test.ts @@ -162,8 +162,16 @@ describe("post-finalize verification noop status-write guard", () => { expect.objectContaining({ source: expect.objectContaining({ sourceType: "recovery" }) }), ); + // FNXC:MergerUnification 2026-07-07-08:35: + // FN-4944's post-finalize guard added an earlier "already-on-main fast-path" + // no-op that fires whenever a done + merge-confirmed task hits a verification + // error, BEFORE the bounce-cap logic. This scenario (done task, VerificationError) + // now resolves through that fast-path, whose log message differs from the older + // cap-reached "already-done task" wording. Pin the fast-path message text here; + // the no-op count (1) and the task:post-finalize-verification-no-op audit are + // unchanged across both paths. const noopLogs = logs.filter((entry) => - entry.includes("[verification] post-finalize VerificationError on already-done task — no action"), + entry.includes("[verification] post-finalize verification failed for already-on-main fast-path; no action"), ); expect(noopLogs).toHaveLength(1);