refactor: convert exported arrow consts to function declarations

[HerringtonDarkholme]

Summary

Converts every export const foo = (...) => {...} arrow function to an export function foo(...) {...} declaration across all packages (sdk, ui, hooks, and the wallet adapters).

119 conversions across 87 files.

What changed

• export const foo = (...) => {...} → export function foo(...) {...}
• Async, generic (<T,> → <T>), and explicit-return-type variants handled
• Expression-body arrows wrapped in return
• Typed React components (export const Foo: FC<Props> = ({...}) => {...}) → export function Foo({...}: Props) {...}, with the now-unused FC/FunctionComponent import removed (kept where non-exported helpers in the same file still reference it)

Left untouched

Non-exported arrow consts, forwardRef/memo components, object/value consts, and default exports.

Behavior preservation

Arrow functions and function declarations differ in this/arguments binding, constructor usage, and prototype/new.target. Verified none of these apply:

• this — not referenced in any of the 87 changed files (word-boundary search)
• arguments — not referenced in any of the 87 changed files
• None of the converted functions are used as constructors (new), and .prototype/new.target are not referenced

Hoisting differs (TDZ vs hoisted) but is harmless for module-level exports. The conversion is therefore behavior-preserving.

Verification

• 0 exported arrow consts remain
• SDK typecheck passes
• UI typecheck surfaces only 3 pre-existing errors (in untouched function bodies of ErrorStep.tsx / DepositAddressModalRenderer.tsx), not introduced by this refactor
• Prettier applied to all changed files

🤖 Generated with Claude Code

[vercel]

@HerringtonDarkholme is attempting to deploy a commit to the Uneven Labs Team on Vercel.

A member of the Team first needs to authorize it.