Sails Local Smoke

Goal

Validate the generated client path against a local node after gtest is already green.

The deploy artifact is the .opt.wasm file (optimized WASM), not the plain .wasm. The .opt.wasm is produced by wasm-opt during the Sails build and is significantly smaller. Uploading the unoptimized .wasm to a node will often fail with CodeTooLarge.
Prefer vara-wallet for deploying to a local node. It handles account management and program upload without requiring a Gear source checkout or Rust-specific tooling.
For Rust-native test harnesses that already use gclient, the GearApi + GclientEnv path remains valid as a secondary option.

Use local dev accounts or user-provided account addresses in SS58 form for standard Vara account flows; do not default to Ethereum 0x addresses for normal local-node work.
Record the real deployed program id from the deploy step and pass that into the typed client. If the flow uses vouchers, issue one first and use the returned voucher ID. Do not invent either identifier.
Keep seed phrases and private keys out of committed scripts, docs, and examples. Use local keyrings, environment input, or interactive setup instead.