Add organization service lifecycle and uniqueness-constraint tests in src/services/organization.test.ts

[1nonlypiece]

📌 Description

src/services/organization.ts has no dedicated test coverage. Org creation,
rename, slug/name uniqueness, and deletion underpin the entire multi-tenant
model, yet none of these paths are exercised by a test, so a uniqueness or
cascade regression could ship silently.

This issue adds lifecycle and constraint tests for the organization service.

Goal: verify org creation, uniqueness constraints, and deletion cascade
behaviour for src/services/organization.ts.

🎯 Requirements and Context

• Must assert name/slug uniqueness is enforced (duplicate rejected).
• Must cover deletion cascade or soft-delete behaviour as implemented.
• Must cover invalid-input rejection paths.
• Must run against the test DB harness.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b test/organization-service-lifecycle

2. Implement changes

• Add src/services/organization.test.ts.

3. Test and commit

• Run with bun test.
• Cover edge cases: duplicate name, rename collision, delete cascade, invalid
  input.

Example commit message

test: organization service lifecycle and uniqueness tests

✅ Guidelines

• Minimum 95% test coverage on the new/changed lines.
• Clear, reviewer-friendly documentation.
• No regressions on existing organization behaviour.
• Timeframe: 96 hours.

🏷️ Labels

type-testing · area-backend · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the Disciplr contributor Discord to coordinate, ask questions, and get
  unblocked fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid
  duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful
  reviews — reach out any time you're blocked.

[mekeke111]

Hi maintainer I am a full stack developer I can handle this

[otobongdev]

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

i want to handle the issue

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

[drips-wave]

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

🧑‍💻 @otobongdev: 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 marked as completed by a Drips Wave moderator for @otobongdev as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor has provided a comprehensive test suite in src/services/organization.test.ts covering all requirements: organization creation, slug uniqueness, retrieval, and cascade deletion of related entities. The PR also correctly updates the Jest configuration and includes a necessary guard in a migration file to ensure the test database harness functions correctly.

😎 @otobongdev: You earned 100 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.