feat(swap-service): unified affiliate registration

[kaladinlight]

Description

• POST /v1/affiliate now requires partnerCode and bps and enforces RESERVED_PARTNER_CODES (previously bypassable via this endpoint).
• POST /v1/affiliate/claim-code route and AffiliateService.claimPartnerCode are deleted. The matching dashboard/gateway changes ship in a separate web PR that must merge before this one (deploy order matters so the gateway never proxies to a 404).
• PARTNER_CODE_REGEX tightened to /^[a-z0-9]{3,32}$/ — lowercase letters/digits only, no hyphens or mixed case.
• New isReservedPartnerCode helper supports exact-match against a focused brand + env list and substring match for shapeshift (catches myshapeshift, shapeshift-airdrop, etc.).
• Reserved-code rejection now returns 400 instead of 409 — a reserved code is a validation failure, not a resource conflict.
• Unit tests added for AffiliateService.createAffiliate (happy path, duplicate wallet, reserved code, taken code).
• Pre-existing affiliates with partner_code IS NULL are left as-is; no backfill, no admin claim path.

Testing

• yarn workspace @shapeshift/swap-service test passes (4 new affiliate.service tests).
• POST /v1/affiliate/claim-code returns 404.
• POST /v1/affiliate missing partnerCode or bps returns 400 with class-validator messages.
• Registering with a reserved code (e.g. admin, myshapeshift) returns 400 with "This partner code is reserved".
• Registering an already-claimed code returns 409 with "Partner code already taken".
• Re-registering the same wallet returns 409 with "Affiliate already registered".
• Pre-existing affiliates with partner_code IS NULL are unaffected.

[coderabbitai]

Warning

Review limit reached

@kaladinlight, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 minute and 50 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5f3c79aa-050d-4311-ad58-74cf6447d14a

📥 Commits

Reviewing files that changed from the base of the PR and between f53f99d and 3b751b0.

📒 Files selected for processing (5)

• apps/swap-service/src/affiliate/__tests__/affiliate.service.test.ts
• apps/swap-service/src/affiliate/affiliate.controller.ts
• apps/swap-service/src/affiliate/affiliate.service.ts
• apps/swap-service/src/affiliate/types.ts
• apps/swap-service/src/affiliate/utils.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/affiliate-register-with-code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}