Update order expiration email copy

The assistant used context-mode tools to search the codebase for email templates, sending pipeline, database-backed templates, and expiration/recovery logic. It found three Blade templates (orders-expiring, order-expired, orders-pending-deletion), the queue job CustomerEmail.php that sends them, and the scheduled commands ProcessExpiringOrderEmails and ProcessExpiringOrders. The database template system exists but all seeded templates have is_active=0, so file-based templates are used in production. The assistant also discovered that the 'Old Orders - 10 days before expiration' email does not exist in the codebase.

3 weeks ago → 3 weeks ago

The assistant investigated four marketing claims from the new email copy: 1) 6-month recovery window for expired albums, 2) $1.50/month or $18/year pricing, 3) albums re-enabled within 24 hours, 4) expiration timing. It found that there is no 6-month recovery window in the code; the actual purge eligibility is 90 days disabled and 2 years order age. The $18/year pricing was confirmed in WooCommerce. Re-enabling is automatic via Customer::updateSubscriptionStatus() when a subscription is detected. The 7-day warning and expiration emails are scheduled daily at 9am and 10am respectively. The assistant concluded the 6-month recovery claim is inaccurate and the 10-day old-order email is a net-new build.

3 weeks ago → 3 weeks ago