fix: artifacts/addresses.json.example is missing a compliance contract entry

[misrasamuelisiguzor-oss]

Description

abis/ contains ABIs for compliance.json, invoice.json, and treasury.json, so artifacts/addresses.json.example (validated against script output in #269) should have a placeholder entry for all three deployed contract addresses; confirm compliance isn't missing given it's a newer contract than invoice/treasury.

This is part of the operational tooling under scripts/, the layer that turns manual, error-prone deployment and verification steps (per docs/MAINNET_DEPLOYMENT.md and docs/TESTNET_ONBOARDING.md) into repeatable, reviewable commands. Because several of these scripts run against mainnet or gate what CI considers a passing build, a bug or missing safeguard in one of them isn't just a developer-experience annoyance, it's a risk multiplier for whatever high-stakes operation the script is supposed to make safe.

Scripts in this category are also disproportionately under-tested relative to application code across most projects, this repository included, simply because shell scripts don't get the same default test-suite treatment that cargo test or npm test gets; that makes gaps here more likely to persist unnoticed until someone hits them during an actual deployment, which is the worst possible time to discover a scripting bug.

Requirements and context

• Add a compliance key with a placeholder address if missing

Suggested execution

1. Fork the repo and create a branch

   git checkout -b fix/addresses-example-add-compliance
   

2. Implement changes

• Update artifacts/addresses.json.example

3. Test and commit

• Run scripts/export_deployed_addresses.sh locally and diff against the example shape

Example commit message

fix: add missing compliance entry to addresses example file

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[divysam]

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

Hello
I would love to work on this issue please

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

[Hollujay]

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

I would like to work on this issue because I will get it done efficiently.

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

[kwest0002-lab]

@kwest0002-lab has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

please i will love to work on this

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

[drips-wave]

Congratulations, @kwest0002-lab! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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