[Backend] Implement Consistency Checks for Task Registration and Sequential ID Allocation

[ayomideadeniran]

Contributor Focus: [Data Integrity] Verify backend assumptions around task creation and identifier sequencing remain true
ETA: 2 days

Context

Task registration often underpins indexing, execution lookup, and analytics assumptions across the system.

Problem

If registration or id allocation semantics drift, many downstream systems can break subtly.

Task Breakdown

1. Review how task ids are allocated and consumed today.
2. Add consistency checks and targeted tests around sequential or expected allocation behavior.
3. Cover concurrent or repeated registration edge cases where relevant.
4. Document any assumptions that downstream tooling should not make.
5. Make the tests readable for contributors unfamiliar with the contract.

Acceptance Criteria

• Registration and id behavior are explicitly tested.
• Downstream assumptions are clearer.
• Edge cases are covered well enough to catch regressions.
• Contributors can understand why the checks matter.

[LaahAbba]

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

Hi my name is Abba and I'm a full stack develop I'll like to work on this issue because It picks my interest and Ive got experience with similar projects I'll have it solved in 24 hours or less

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

[OkeyAmy]

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

Hello Chief, I would like to work on this issue. I have 3 years of experience as an open source contributor

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

[OSEH-svg]

@OSEH-svg has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hello Maintainer,
I’d love to work on this issue. I'm a software developer with 5 years of experience and I’m confident I can deliver a good solution. Please feel free to assign it to me.

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

[kingfavourjudah]

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

I would like to apply for bounty #275 focused on implementing consistency checks for task registration and sequential ID allocation in SoroTask.

I have experience working with backend systems, smart contract integrations, and test-driven development, particularly in environments where data integrity and predictable state transitions are critical. For this task, I would begin by reviewing the current task registration flow and how identifiers are generated, stored, and consumed across the system.

My approach would include adding clear consistency checks, writing targeted and readable tests for sequential allocation behavior, and covering repeat or concurrent registration edge cases that may cause subtle downstream issues. I would also document important assumptions so future contributors and external tooling maintainers understand what can and cannot be relied upon.

I can complete this within an ETA of 6 hours and ensure the final contribution is clean, well-tested, and easy to maintain.

Thank you for your consideration.

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

[drips-wave]

Congratulations, @OkeyAmy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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