[2026 Testing] Add property-based tests for configuration round trips

[Nanle-code]

Objective

Preserve valid values and reject malformed combinations across generated inputs.

Target area

config parsing, merging, and serialization

Acceptance criteria

• The objective is implemented with clear handling for invalid input, unsupported environments, and failure paths.
• Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
• User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.

Source: .github/roadmap-issues-2026-07-29.json.

[Frontman-Code]

@Frontman-Code has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i will love to work on this issue

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

[nonso7]

@nonso7 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Can i work on this issue

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

[martinshub-tech]

@martinshub-tech has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to take this issue. I've analyzed the root cause and am confident I can deliver a reliable fix with proper testing

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

[Enniwealth]

@Enniwealth has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to work on this issue.

I have experience building blockchain deployment tooling and developer-focused CLI workflows, making this a good fit.

Implementation Plan
Add a --dry-run deployment mode that generates a deterministic deployment plan without submitting transactions.
Display the target network, deploying account, contract code hash, estimated fees, required authorizations, and all planned state mutations.
Validate inputs and gracefully handle unsupported environments, invalid configurations, and deployment failures with clear error messages.
Ensure the dry-run output is deterministic and mirrors the actual deployment flow as closely as possible.

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

[drips-wave]

Congratulations, @nonso7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @nonso7: 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 🌊

[drips-wave]

This issue has been completed by @nonso7 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @nonso7: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.