[CONTRACT-71] Reproducible testnet deployment scripts and a Makefile

[mftee]

Overview

contracts/scripts exists but there's no Makefile at the contracts/ root, and it's unverified whether the existing scripts constitute a documented, reproducible testnet deployment process (initialize each contract with the correct cross-references — e.g. reputation's authorized_contract pointing at the real deployed shipment contract address, escrow's token_contract pointing at the real token). Given this session's confirmed pattern of contract-related documentation/tooling issues being closed without landing, this should be verified against what actually exists rather than assumed present.

Tasks

• Audit contracts/scripts for what deployment automation currently exists.
• Add a Makefile (or equivalent) with targets for build, test, and a full ordered testnet deployment of all five contracts with their cross-references correctly wired.
• Document the deployment order and required environment/secrets in a contracts/DEPLOYMENT.md or the per-crate READMEs from [CONTRACT-69].

Acceptance Criteria

• A contributor can deploy all five contracts to testnet, correctly cross-wired, by following one documented process.

Dependencies

Natural to land alongside [CONTRACT-69].

Notes for Contributors

Requires Rust + Soroban. Workspace: contracts/ (members: identity, shipment, escrow, document, reputation). Run cargo test --all, cargo fmt --all -- --check, and cargo clippy --all-targets --all-features -- -D warnings before opening a PR — CI enforces all three. Comment below to be assigned.

[Ranjeet2063]

Hello! I'd like to work on this issue.

I'd love to take ownership of this issue.

Technical Approach:

1. Core Work: Implement [CONTRACT-71] Reproducible testnet deployment scripts and a Makefile with explicit require_auth checks, clean storage schemas, and robust Soroban contract logic.
2. Quality Gate: Add unit tests asserting both happy-path invocations and unauthorized revert conditions.

Background: Active open-source contributor with 130+ merged PRs across Web3/Stellar ecosystems.

Let me know if this approach looks good and please assign!

[guptakumarranjeet150]

Hey team,

I would love to take this on. My planned approach:

• Implement [CONTRACT-71] Reproducible testnet deployment scripts and a Makefile with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.

Happy to pick this up today—please assign to me!

[shobhamerabacha-star]

Hello! I'd like to work on this issue.

I would love to take this on. My planned approach:

• Implement [CONTRACT-71] Reproducible testnet deployment scripts and a Makefile with explicit require_auth checks, clean storage layouts, and robust Soroban contract logic.
• Add comprehensive unit tests verifying both happy-path invocations and unauthorized revert scenarios.

Excited to work on this—please assign to me and I'll submit a clean PR shortly!