[Feature] Generate TypeScript client bindings for Tholos

[collinsezedike]

Summary

Generate a typed TypeScript client for Tholos using the Stellar CLI's stellar contract bindings typescript, and publish/commit it so JS/TS integrators stop hand-writing raw Contract/TransactionBuilder/nativeToScVal boilerplate. INTEGRATION.md currently only documents the Rust contract-to-contract path (via contractimport!); there's no equivalent for application developers calling in from a browser or Node. demos/freelance-escrow's src/lib/tholos.ts is a concrete example of exactly the boilerplate a generated client would eliminate: manual transaction building, simulate, sign, submit, and poll-for-result, all hand-rolled.

Scope

• Run stellar contract bindings typescript against the deployed (or wasm) contract, producing a typed package under, e.g., packages/tholos-sdk or a similar location, one method per contract function.
• Decide and document how it's consumed: committed in-repo package, published to npm, or both.
• Add a short section to INTEGRATION.md documenting this as the JS/TS integration path, alongside the existing Rust contract-to-contract pattern.
• Out of scope: migrating demos/freelance-escrow to use it instead of its current hand-rolled client (separate follow-up issue, since the demo works fine as-is and shouldn't block the SDK on unrelated churn).

Proposed approach

Regenerate bindings whenever the contract's public interface changes (a CI check similar to the existing "verify workspace membership" one could catch drift, but that's an implementation detail to work out during the issue, not a decision to make up front).

[yunus-dev-codecrafter]

Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!

[Ranny17]

I’m applying to this because this issue sits squarely in the kind of work I do day-to-day building and shipping developer-facing tooling for web3 integrations, not just theorizing about it. I understand firsthand the friction integrators feel when they’re hand-rolling boilerplate like manual transaction building, signing, and polling exactly the pain point this issue calls out in demos/freelance-escrow/src/lib/tholos.ts. I’d bring a practical, ship-it orientation to generating and documenting the Tholos TypeScript SDK: running stellar contract bindings typescript against the contract, scaffolding a clean packages/tholos-sdk, writing the JS/TS section of INTEGRATION.md so it stands alongside the existing Rust path, and proposing a sensible drift-detection story for CI all while respecting the explicit scope boundary of leaving the freelance-escrow demo migration for a follow-up.

[collinsezedike]

Go for it, @Ranny17

[grantfox-oss]

🦊 GrantFox — @Ranny17 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #60)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.