Add regression test for per-wallet cap enforced on airdrop recipients

[Chucks1093]

Summary

When an airdrop is sent to a recipient who is already at the per-wallet cap, that recipient should be skipped rather than reverting the whole airdrop. A regression test should confirm the skip behavior and that other recipients still receive their keys.

Scope

• Register a creator with a per-wallet cap of 10
• Give wallet A 10 keys (at the cap)
• Airdrop 5 keys to wallet A and 5 keys to wallet B in one call
• Assert wallet A's balance is still 10 (skipped)
• Assert wallet B received 5 keys

Acceptance Criteria

• Wallet at cap is skipped, not reverted
• Other recipients in the same airdrop receive their keys
• Airdrop summary reflects the skipped recipient

ETA: 12 hours

---

Coordinate on Telegram

[abioye-emma]

Hi, I’m a full-stack Web2 & Web3 developer with open-source contribution experience, and I’d be glad to work on this issue.

[Benedict315]

Please assign

[grantfox-oss]

🦊 GrantFox — @Benedict315 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.