Add missing fields

[adv76]

Add missing Email Status "Sent" and missing "Tags" field to Email Receipt.

---

Summary by cubic

Add the missing EmailStatus "sent" and the "tags" field on EmailReceipt to align with the Resend API. This enables clients to read tag metadata and the sent status from receipts.

• New Features
  • Added EmailStatus.Sent mapped to JSON value "sent".
  • Added EmailReceipt.Tags: List? serialized as "tags".

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

[cubic-dev-ai]

1 issue found across 2 files

Confidence score: 3/5

• There is a concrete regression risk in src/Resend/EmailStatus.cs: adding Sent in the middle of EmailStatus reindexes later enum values, which can change serialized/stored values seen by existing consumers.
• This is moderate risk (severity 6/10, confidence 8/10) because behavior can break at integration boundaries even if local compilation/tests pass.
• Pay close attention to src/Resend/EmailStatus.cs - enum numeric value shifts may break compatibility for Suppressed/Failed consumers unless explicit values are assigned.

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/Resend/EmailStatus.cs">

<violation number="1" location="src/Resend/EmailStatus.cs:77">
P2: Inserting the new `Sent` enum member in the middle of `EmailStatus` changes the underlying integer values of existing members (`Suppressed`, `Failed`) because no explicit values are assigned. This can break consumers that rely on numeric casts, database storage, or ordinal positions.</violation>
</file>

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

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Inserting the new Sent enum member in the middle of EmailStatus changes the underlying integer values of existing members (Suppressed, Failed) because no explicit values are assigned. This can break consumers that rely on numeric casts, database storage, or ordinal positions.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/Resend/EmailStatus.cs, line 77:

<comment>Inserting the new `Sent` enum member in the middle of `EmailStatus` changes the underlying integer values of existing members (`Suppressed`, `Failed`) because no explicit values are assigned. This can break consumers that rely on numeric casts, database storage, or ordinal positions.</comment>

<file context>
@@ -71,6 +71,12 @@ public enum EmailStatus
+    /// <summary>
+    /// Email has been sent.
+    /// </summary>
+    [JsonStringValue( "sent" )]
+    Sent,
+
</file context>