feat(lifecycle): attach the whitepaper PDF to the fulfillment email

[blove]

What

The whitepaper fulfillment email ("Here is the guide you requested") pointed at a URL. It now carries the guide as an attachment, with the link kept underneath as a fallback.

New body:

Here is the guide you requested, attached to this message.

If the attachment does not come through, it is also here:
https://threadplane.ai/whitepapers/angular.pdf

Read it when you have a quiet hour.
If something in it does not hold up in your own code, reply and tell me.

Subjects stay per-paper. The link is kept because corporate mail gateways do strip PDF attachments from an unfamiliar sender, and a link-free email would leave those recipients with nothing. It is still one link, still an approved one, so campaignDraftViolations passes unchanged.

How

Resend's attachments[].path takes a hosted URL and Resend fetches the bytes itself. So no PDF flows through the lifecycle function, nothing is bundled, and the attachment is always whatever generate-whitepaper.ts last deployed. The alternatives — inlining ~1.4 MB of base64 per send, or shipping the four PDFs inside the lifecycle artifact where they would drift from the website's generated copies — both cost more than they buy.

Attachment filenames match the ones WhitePaperForm.tsx puts on the on-page download.

The guard

Resend performs that fetch under the Threadplane sender, so the attachment is a closed registry, not a free-form field — the same shape as the existing campaignTemplate handling, and validated in the same place, after authorization, because the rule depends on the authorized job.kind:

• only fulfill mail may carry an attachment (send_step throws)
• at most one
• filename must match /^[a-z0-9]+(?:-[a-z0-9]+)*\.pdf$/
• path must be one of the four approved threadplane.ai deliverables

No code path can talk Resend into fetching an arbitrary URL on our behalf.

Failure behavior

If Resend cannot fetch the PDF it returns an error, and the existing classifyResendProviderError split applies unchanged: 4xx marks the job provider_rejected, 5xx/429 marks it unknown. No new retry path was added — a missing deliverable is something to hear about, not to silently retry.

Cleanup

dispatchRecipient took nine positional parameters and would have taken ten. Its message-shaped arguments collapse into one object. Two call sites, same file.

Verification

• apps/lifecycle — 313 passed (was 305)
• libs/growth — 547 passed
• nx lint lifecycle growth — 0 errors
• nx check lifecycle (tsc + Dawn) — green
• nx build growth — green

Every guard was mutation-tested rather than assumed. Seven mutants, all killed:

Mutation	Tests failed
path registry check removed	7
job-kind check removed	1
filename pattern removed	5
attachments never reach the provider payload	5
exactly-one-attachment check removed	2
send.ts drops the attachment	5
template attaches the wrong paper	6

Note that this ships behind the lifecycle app's own Vercel project, which ci.yml's promote job does not cover — worth a live send check after deploy.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
threadplane	Ready	Preview	Sep 9, 2026 5:27pm UTC

[github-actions]

Automated approval: this PR received an intelligent (AI) code review. See the review comments on this PR.

[github-actions]

Claude finished @blove's task in 0s —— View job

---

I'll analyze this and get back to you.