feat(batch): reflect tags in batch send

[cpenned]

Summary

The batch send API supports tags on each email in the batch. This crate already exposes tags on CreateEmailBaseOptions, which batch send uses — this change documents that and adds coverage.

Changes

• Document batch support for tags on BatchSvc::send
• Add a serialization unit test asserting the batch payload includes tags
• Add an integration test for batch sends with tags
• Changelog entry under Unreleased

  

---

Summary by cubic

Documented and tested batch send support for per-email tags. Updated docs to state that batch supports tags only and not attachments or scheduled_at, removing a CreateEmailBaseOptions link that implied otherwise.

• Added unit and integration tests to verify tag serialization in batch sends.

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

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Documentation and test-only changes for batch send fields (scheduled_at, tags, attachments). No production code logic changes.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 2 files (changes from recent commits).

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="src/batch.rs">

<violation number="1" location="src/batch.rs:23">
P3: Users can still infer from this `CreateEmailBaseOptions` documentation that all of the shared send-email fields work in a batch, including `attachments` and `scheduled_at`, even though the batch endpoint rejects or ignores them. A concise limitation note here would prevent misuse of the shared builder.</violation>
</file>

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

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Users can still infer from this CreateEmailBaseOptions documentation that all of the shared send-email fields work in a batch, including attachments and scheduled_at, even though the batch endpoint rejects or ignores them. A concise limitation note here would prevent misuse of the shared builder.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/batch.rs, line 23:

<comment>Users can still infer from this `CreateEmailBaseOptions` documentation that all of the shared send-email fields work in a batch, including `attachments` and `scheduled_at`, even though the batch endpoint rejects or ignores them. A concise limitation note here would prevent misuse of the shared builder.</comment>

<file context>
@@ -20,8 +20,8 @@ impl BatchSvc {
     ///
-    /// Each [`CreateEmailBaseOptions`] in the batch supports `scheduled_at`, `tags`,
-    /// and `attachments`, in addition to the other send-email body parameters.
+    /// Each [`CreateEmailBaseOptions`] in the batch supports `tags`, in addition to
+    /// the other send-email body parameters.
     ///
</file context>

Suggested change

	/// Each [`CreateEmailBaseOptions`] in the batch supports `tags`, in addition to
	/// the other send-email body parameters.
	/// Batch sends support `tags` on each [`CreateEmailBaseOptions`]. The
	/// `attachments` and `scheduled_at` fields are not supported.

Dismissed because Cubic found issues in a newer review.

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

<sub>Requires human review: Auto-approval blocked by 1 unresolved issue from previous reviews.

Re-trigger cubic</sub>