fix(client): use as const for tuple inference in useReadContract args

The safeBigInt IIFE returned bigint[] which isn't assignable to wagmi's
expected readonly tuple type. Adding as const narrows the array literal
to the correct tuple shape.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: Oba-One

client/components/jar/NFTGatedWithdrawalSection.tsx

@@ -159,7 +159,7 @@ export const NFTGatedWithdrawalSection: React.FC<
 		address: (activeNFT?.contractAddress as `0x${string}`) || undefined,
 		abi: ERC721_ABI,
 		functionName: "ownerOf",
-		args: activeNFT?.tokenId ? (() => { const id = safeBigInt(activeNFT.tokenId); return id !== undefined ? [id] : undefined; })() : undefined,
+		args: activeNFT?.tokenId ? (() => { const id = safeBigInt(activeNFT.tokenId); return id !== undefined ? [id] as const : undefined; })() : undefined,
 		query: {
 			enabled: !!(
 				activeNFT?.contractAddress &&
@@ -181,7 +181,7 @@ export const NFTGatedWithdrawalSection: React.FC<
 		functionName: "balanceOf",
 		args:
 			userAddress && activeNFT?.tokenId
-				? (() => { const id = safeBigInt(activeNFT.tokenId); return id !== undefined ? [userAddress, id] : undefined; })()
+				? (() => { const id = safeBigInt(activeNFT.tokenId); return id !== undefined ? [userAddress, id] as const : undefined; })()
 				: undefined,
 		query: {
 			enabled: !!(