Admin Subscription Plan Endpoints

[codebestia]

Background

SubscriptionPlan and Subscription already exist in the schema (fields match the contract's structs — id, planId, merchantId, description, token, amount, interval, active for plans) — no new schema is needed for this issue.

Proposed Steps

1. GET /admin/subscription-plans — paginated, filterable by merchantAddress (join), token, active (bool), sortable by sortBy in [createdAt, amount, interval] / sortDir.
2. GET /admin/subscription-plans/:id — plan detail, including a subscriberCount (via Prisma's _count on the subscriptions relation) since an admin looking at a plan will reasonably want to know how many active subscribers it has without a second request.
3. Tests, as explicitly requested: tests/unit/admin.subscription-plan.services.test.ts (filter/sort/pagination logic) and tests/integration/admin.subscription-plan.routes.test.ts (route-level, following the existing mocked-Prisma pattern used throughout tests/integration/).

Acceptance Criteria

• GET /admin/subscription-plans supports all listed filters, sort options, and pagination
• GET /admin/subscription-plans/:id includes subscriberCount; 404 for unknown id
• Unit tests cover the filter/sort/pagination parsing logic in isolation
• Integration tests cover the routes end-to-end against a mocked Prisma client, matching the existing test suite's conventions
• No new Prisma models or fields required

[Peculiarr7]

Hi! I’m a full-stack developer with a strong blockchain background, and I’m confident I can resolve this issue quickly and effectively. I’ll deliver a clean, reliable solution with immediate attention to detail, ensuring it’s completed as soon as possible. Please assign it to me—I’m ready to get started right away.

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[codeZe-us]

Hello, i can work on this task. I will build the two admin endpoints using Prisma queries on the existing SubscriptionPlan model, no schema changes, adding filtering by merchantAddress, token, and active status plus sorting and pagination to the list endpoint, and a _count on the subscriptions relation for subscriberCount with a 404 fallback on the detail endpoint, then write unit tests for the filter/sort/pagination logic and integration tests against a mocked Prisma client following the existing test suite conventions.

[grantfox-oss]

🦊 GrantFox — @codeZe-us has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #44)
2. Your PR will be reviewed by the ShadeProtocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@codeZe-us's PR #58 was approved and merged by @codebestia.

🏆 @codeZe-us: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (284 total points). Track your full progress on GrantFox.

👏 Great work, @codeZe-us! Keep contributing to ShadeProtocol.