fix: resolve 7 TypeScript compilation errors blocking tsc --noEmit

[Shantanu112-bd]

Summary

Fixes all 7 TypeScript compilation errors that caused
npx tsc --noEmit to fail, blocking IDE integration
and CI type-checking pipelines.

Changes

agent.ts

• Fixed Server import → Horizon.Server (correct
  stellar-sdk v11+ pattern)
• Added Network type union to fix TS2367
  non-overlapping string comparison errors
• Added explicit types to balance variable inferences

examples/

• Typed all catch blocks as error: unknown with
  instanceof Error guard — eliminates implicit any

lib/buildTransaction.ts

• Fixed string equivalence type errors with proper
  type guards

Verification

npx tsc --noEmit → 0 errors
npm test        → 28 passed, 0 failed

Closes #49

---

Summary by cubic

Fixes seven TypeScript errors so npx tsc --noEmit passes and adds full network-aware Soroban/Horizon config across libs/tools. Bridge and contract/stake tools now support multi-chain/token flows with stricter schemas and better errors; all 28 tests pass.

• New Features

  • Added ContractConfig/StakeConfig and networkPassphrase in buildTransaction; AgentClient injects Soroban config via getSorobanConfig for all contract ops.
  • Upgraded bridgeTokenTool to accept destinationChain and symbol with dynamic token lookup; wrapped in try/catch with clearer failures; mainnet guard preserved.
  • Refined tool schemas using Zod discriminated unions; staking tool takes fromNetwork and builds per-network RPC/passphrase; stellarSendPaymentTool respects STELLAR_NETWORK; signTransaction accepts an explicit secret key.

• Bug Fixes

  • Switched to Horizon.Server from @stellar/stellar-sdk, typed balances with Horizon.ServerApi.BalanceLine, fixed TS2367 comparisons, and typed catch blocks as unknown; tests updated.
  • Removed hardcoded Testnet by propagating network inputs and using provided passphrases in fromXDR.

^{Written for commit 0db6861. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 3 files

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic Password	0db6861	tools/stellar.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[daiwikmh]

resolve merge conflicts