Engineering Gap
sendReceiptViaEmail in app/backend/src/claims/claims.service.ts line 642 is a TODO stub. The method logs but never sends email. Core receipt-sharing feature non-functional.
Codebase Evidence
app/backend/src/claims/claims.service.ts lines 637-651: sendReceiptViaEmail logs with "[EMAIL STUB]" prefix, TODO comment references SendGrid/AWS SESapp/backend/src/notifications/notifications.processor.ts: BullMQ processor exists with concurrency config, ready for email jobs- No email provider SDK in package.json dependencies
app/backend/src/notifications/notifications.module.ts: Module infrastructure exists
Risk Profile
Current Risk
Receipt sharing feature non-functional. Users requesting email receipts receive nothing.
Business Impact
Broken user trust. Inability to deliver proof-of-claim. Non-compliance with humanitarian accountability standards.
Remediation Strategy
Integrate SendGrid (free tier for dev) or AWS SES. Add provider SDK. Create EmailService in notifications module. Wire into BullMQ processor for async delivery. Add email-specific Prometheus metrics.
Success Conditions
Change Surface
Files: claims/claims.service.ts, new notifications/email/email.service.ts, notifications/notifications.module.ts, package.json
Security Review
Email provider API keys must be stored via env vars. Must not log email addresses or receipt content in production.
Completion Checklist
Engineering Gap
sendReceiptViaEmailinapp/backend/src/claims/claims.service.tsline 642 is a TODO stub. The method logs but never sends email. Core receipt-sharing feature non-functional.Codebase Evidence
app/backend/src/claims/claims.service.tslines 637-651: sendReceiptViaEmail logs with "[EMAIL STUB]" prefix, TODO comment references SendGrid/AWS SESapp/backend/src/notifications/notifications.processor.ts: BullMQ processor exists with concurrency config, ready for email jobsapp/backend/src/notifications/notifications.module.ts: Module infrastructure existsRisk Profile
Current Risk
Receipt sharing feature non-functional. Users requesting email receipts receive nothing.
Business Impact
Broken user trust. Inability to deliver proof-of-claim. Non-compliance with humanitarian accountability standards.
Remediation Strategy
Integrate SendGrid (free tier for dev) or AWS SES. Add provider SDK. Create EmailService in notifications module. Wire into BullMQ processor for async delivery. Add email-specific Prometheus metrics.
Success Conditions
Change Surface
Files:
claims/claims.service.ts, newnotifications/email/email.service.ts,notifications/notifications.module.ts,package.jsonSecurity Review
Email provider API keys must be stored via env vars. Must not log email addresses or receipt content in production.
Completion Checklist