Harden StarkNet campaign client typing and failure coverage

[pragmaticAweds]

Context

The non-mock Cairo/StarkNet campaign client still uses several any casts for transaction execution and receipt event parsing. It also has only mock-client coverage today. The production client should have focused tests around required environment variables, transaction hash extraction, event campaign ID parsing, and RPC failure handling.

Scope

• Replace broad any usage in StarkNet receipt and execution handling with narrow local types
• Extract and test campaign-created event parsing behavior
• Add tests for missing required Cairo/StarkNet environment variables
• Add tests for missing transaction hash in contract execution result
• Add tests for fallback campaign ID behavior when no campaign-created event key is configured
• Ensure retry behavior is exercised with mocked provider/account calls where practical

Out of Scope

• Changing the Cairo contract interface
• Live testnet integration tests
• Campaign service business-rule changes

Acceptance Criteria

• Production StarkNet client behavior is covered without requiring live RPC access
• Receipt parsing does not depend on unbounded any types
• Missing config and malformed execution results fail with clear errors
• bun run type-check passes
• bun run test passes
• bun run lint passes

Suggested Files or Packages

• src/services/cairo/campaignFactory.starknet.ts
• src/services/cairo/campaignFactory.client.ts
• src/__tests__/

[OluRemiFour]

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

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

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

[daveades]

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

Please I would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @OluRemiFour: 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]

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

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