SDK: define contract binding generation workflow

[Otaiki1]

Build location

Work primarily in sdk/src/contract. Keep related tests/docs beside that package unless this issue explicitly calls for a cross-package update.

Why this matters

Contract bindings should be reproducible and tied to deployed Soroban contract versions.

What to build

• Document binding source, generation command, and expected output files.
• Add version metadata for contract ID/network/schema.
• Fail tests when bindings and constants are incompatible.

Acceptance criteria

• README documents how to regenerate bindings.
• Tests assert supported contract version metadata.

Suggested verification

cd sdk && npm run lint && npm run test && npm run build

[od-hunter]

@od-hunter has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi can I be assigned this issue please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @od-hunter to this issue.

[drips-wave]

Congratulations, @od-hunter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @od-hunter: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊