Route Defender signer through the talos recorder, bump @talos/client

Defender's relayer manages nonce + gas + retries server-side, so the
nonce-queue wrap is both broken (the SDK's signTransaction is a
permanent stub) and unnecessary. Switch to the new
wrapSignerWithDefenderRecorderV6 from @talos/client which forwards
sendTransaction unchanged but inserts one nonce_queue_transactions
row post-broadcast — the tx hash + run linkage still appear on
talos's Transactions page.

Bumps @talos/client to talos 060f99e for the new export.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: sparrowDom

pnpm-lock.yaml

@@ -4,6 +4,7 @@ import * as hhHelpers from "@nomicfoundation/hardhat-network-helpers";
 import {
   createDb,
   createPool,
+  wrapSignerWithDefenderRecorderV6,
   wrapSignerWithNonceQueueV6,
 } from "@talos/client";
 
@@ -157,7 +158,16 @@ export async function getSigner(address?: string): Promise<Signer> {
           "Either uncheck the Defender option on this action or configure the env vars.",
       );
     }
-    return maybeWrap(await getDefenderSigner());
+    // Defender's relayer manages nonce + gas + retries server-side, so
+    // the nonce-queue wrap is both broken (Defender can't sign offline)
+    // and unnecessary. The recorder wrapper instead inserts a single row
+    // into nonce_queue_transactions post-broadcast so the tx hash still
+    // shows up on talos's Transactions page linked to its run.
+    const signer = await getDefenderSigner();
+    const db = getNonceDb();
+    return db
+      ? wrapSignerWithDefenderRecorderV6(signer, { db })
+      : signer;
   }
 
   if (hasAwsKmsCredentials()) {