feat: add partially_verified and partially_failed to DomainRecordStatus type

[vcapretz]

Summary

Adds partially_verified and partially_failed as possible values for the DomainRecordStatus type, aligning it with the statuses the API can actually return for domain verification records.

The DomainStatus type already included these values, but DomainRecordStatus (used for individual DNS record verification statuses like SPF, DKIM, Tracking, etc.) was missing them.

Before

export type DomainRecordStatus =
  | 'pending'
  | 'verified'
  | 'failed'
  | 'temporary_failure'
  | 'not_started';

After

export type DomainRecordStatus =
  | 'pending'
  | 'verified'
  | 'failed'
  | 'temporary_failure'
  | 'not_started'
  | 'partially_verified'
  | 'partially_failed';

All existing tests pass (343 tests across 30 test files).

Slack Thread

  

---

Summary by cubic

Add partially_verified and partially_failed to DomainRecordStatus to match API responses for DNS record verification. This avoids type mismatches and enables handling partial states for records like SPF, DKIM, and Tracking.

• Migration
  • Update switch/if logic and type guards to handle the two new statuses.
  • Adjust UI/metrics mapping for the new partial statuses if applicable.

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

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

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

[rehanvdm]

@vcapretz No please do not. This will be a regression.

A Domain Record can not be. Only a domain can.
| 'partially_verified'
| 'partially_failed';

We finally fixed all the inconsistencies we had in this PR, so this is the correct behavior. https://resend.slack.com/archives/C08HL2WMU73/p1776428952919899

@Vitor Capretz remember? Still asked for your advice on that one, please have a very close look before/if you change things. My recommendation is not.

The API + SDKs are now doing what the Docs have always said it, it is correct.