[P1][backend] Validate puzzle dependency graphs

[dzekojohn4]

Reject self-dependencies, cycles, missing nodes, duplicate edges, and dependencies across incompatible states.

[blegodwin]

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

Hello, I'm interested in taking this issue on.

I'll implement this following the existing conventions in the codebase, with tests covering the new behavior.

I'd appreciate being assigned to this issue and look forward to contributing.

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

[Hamda-gbade]

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

I can handle this efficiently if assigned to me

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

[Magrexy]

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

I'd like to harden puzzle dependency configuration in the backend. The core deliverable is validating puzzle dependency graphs so that self-dependencies, cycles, missing nodes, duplicate edges, and incompatible cross-state dependencies are rejected. My approach is to implement a graph validator with clear error messages and add unit tests covering each invalid shape.

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

[Kappa16]

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

Hi MAINTAINER, I'd like to take this on.
I understand what's being asked here and I'm confident I can implement an accurate fix correctly and efficiently. pls i beg of you just help me out please

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

[chainsmt]

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

Hi, I'd like to work on this issue please.

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

[Alimzy]

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

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

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.

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

[drips-wave]

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

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