feat(broadcasts): add recipients command

[dielduarte]

Adds `resend broadcasts recipients ` for GET /broadcasts/{id}/recipients.

Tests: 1114 passed. Lint/typecheck clean.

---

Summary by cubic

Adds resend broadcasts recipients <id> to list a broadcast’s recipients by event type, enabling recipient inspection that was previously not possible. Uses resend 6.22.0 to call broadcasts.recipients().

• Flags: --type is required (non-interactive) with sent|delivered|opened|clicked|bounced|complained|unsubscribed|suppressed. Optional --email (substring filter) and --bounce-type (permanent|transient|undetermined, only meaningful with --type bounced).
• Pagination and UX: supports --limit (1–100, default 20), --after, --before. Interactive mode prints a table and pagination hints; hints do not shell-quote --email. Table renders missing counts as -.
• Output and docs/tests: non-interactive returns the JSON list (type-specific fields like count, bounce_type, clicked_links). Adds docs and tests for validation, pagination, and SDK errors. Note: responses may be cached for up to 15 minutes.

^{Written for commit 3e42538. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 7 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tests/commands/broadcasts/recipients.test.ts">

<violation number="1" location="tests/commands/broadcasts/recipients.test.ts:138">
P3: The interactive path is never exercised: every test forces non-interactive mode (setupOutputSpies/setNonInteractive), so the table rendering (renderBroadcastRecipientsTable) and the pagination-hint branch of printPaginationHint called from the recipients command are untested. The mock also always returns has_more:false. Add one test with isTTY true (interactive) and has_more:true asserting the table output and the ‘Fetch the next page’ hint including --type/--limit flags.</violation>
</file>

<sub>Tip: instead of fixing issues one by one fix them all with cubic

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 3 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Fix all with cubic | Re-trigger cubic</sub>

[gabrielmfern]

i don't think we can do much about this, or have another option, and this is probably the pattern for the other commands, but it feels slightly weird to put the broadcast ID right after the recipients command

[dielduarte]

yeah, I think in this case worth a redesign of all commands to actually receive it as --broadcast-id param? I also found it not very intuitive. but would be a breaking change how other commands are working, still worth a major version updating it, not the best API design.