[29] Add a Soroban deployment script (`stellar contract deploy` orchestrator)

[merlik787-droi]

Problem Statement

The workspace has a Makefile in course-registry (stellar contract build) but no workspace-level deployment script. Deploying Orivex end-to-end currently requires manual sequencing with no idempotency:

1. Deploy reward-pool, initialize.
2. Deploy badge-nft, initialize.
3. Deploy course-registry, initialize.
4. set_reward_pool_address, set_badge_nft_address.
5. Deploy quest-engine, initialize.
6. Deploy stake-vault, initialize.
7. Deploy governance, initialize.
8. add_approved_spender reward-pool(course-registry) and reward-pool(quest-engine).

There is no automation; operators run these by hand.

Why It Matters

• Manual deployments are error-prone.
• Disaster recovery requires exact sequence, which should be in source control.

Expected Outcome

• A tools/deploy.ts (preferred: TypeScript with Stellar SDK).
• A tools/deploy.sh shell alternative.
• A tools/Cargo.toml workspace at the repo root for tooling crates.
• Idempotent: re-running on a fully-deployed state should not double-initialize.
• Tested against screento or stellar-cli's local network.

Acceptance Criteria

• New tools/deploy.sh <network> deploys all six contracts to the target network.
• tools/status.sh queries each contract and prints a health report.
• README documents both commands.

Implementation Notes

• Use stellar-cli's contract deploy subcommand.
• Save deployment config to deployments/<network>.json (admin addresses, contract IDs).
• Reference https://developers.stellar.org/docs/smart-contracts/deployment.

Files / Modules Affected

• New tools/ directory at repo root.
• README.md updated.

Dependencies

None.

Difficulty

Medium.

Estimated Effort

2–3 days.

Suggested Labels

devops, tooling, P2

---

[Songu3020]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[grantfox-oss]

🦊 GrantFox — @Songu3020 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.