backend: subscriptions repository's findBySubscriber has no result limit, unlike every other repository's list method

[gboigwe]

Summary

findBySubscriber in the subscriptions repository returns an unbounded result set, inconsistent with every other repository's list method in this codebase.

Location

backend/src/db/repositories/subscriptions.ts, function findBySubscriber: findMany({ where: { subscriber }, orderBy: {...} }) with no take

Problem

Every other repository method checked (auctions, bids, campaigns, impressions, publishers, governance) takes an explicit limit/take parameter. findBySubscriber doesn't — if a single subscriber ever accumulates many subscription records over time, this query returns all of them, unbounded.

Impact

Low-medium currently (subscription counts per user are likely small today), but a real resource-usage risk as the system grows, and a clear inconsistency with the rest of the codebase's established pattern.

Acceptance Criteria

• findBySubscriber takes an explicit take/limit parameter (with a sensible default and a cap), matching the pattern used elsewhere
• Callers of findBySubscriber are updated if their call signature needs to change
• npm test passes in backend/

Suggested Approach

Mirror whatever limit/pagination pattern an already-consistent repository (e.g. campaigns.ts or auctions.ts) uses.

[Nemenwq]

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

Hi maintainer, can you assign me this please? ETA: 5HOURS

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

[devgbmuyiwa]

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

hello can i work on this issue

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

[iamcracked-dev]

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

Hi maintainers!
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[drips-wave]

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

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