Source snapshot bcc79fcc · Declared package version 2.0.4. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
Native ProviderLifecyclePortV1 adapter for governed Resend delivery. The adapter accepts only opaque message, recipient, sender-profile, template, and encrypted-content references. Credential resolution and email content stay behind the injected driver and never enter work orders, receipts, logs, or errors.
Every send is durably reserved and marked attempted before provider I/O. A timeout or unknown response remains indeterminate; retry must reconcile the same provider idempotency key. Success is returned only after a create-once V2 receipt is persisted, read back, and verified. Read actions use the driver's non-mutating observation path. Rollback and decommission are explicit rejected receipts because delivered email cannot be recalled.
This package is an offline adapter and conformance surface. It is not a live Resend qualification claim until exact-version provider evidence is recorded.
Declared capabilities.
Governed Resend delivery provider
Execute Resend email delivery through the Runtime Node provider lifecycle with durable idempotency, indeterminate-outcome reconciliation, and verified receipts.
Use it to
Send governed email from opaque recipient, template, sender-profile, and content references
Reconcile unknown delivery outcomes before a retry can repeat an external effect
Requires
Resend driver
durable provider state
LSSM OS Runtime Node
Choose another boundary when
Provider credentials or message bodies must appear in work orders, receipts, logs, or errors.
The integration requires recall or rollback of an email after Resend accepts delivery.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.
