Implement consistent error handling strategy across the codebase:

• Issue: Email handler catches and sends error emails (inconsistent with "fail fast" philosophy)
• Decision needed: Should we retry on transient failures (SQLite lock, network issues)?
• Consider: Dead-letter queue for failed email processing
• File: emailHandler.ts:29-39

The hardDeleteProcessedRecords() function is implemented but never invoked.

• Action: Create Val.town cron trigger to run cleanup periodically (daily or weekly)
• Function: InboxService.hardDeleteProcessedRecords() (InboxService.ts:88)

Current implementation returns attachment metadata. Consider adding direct download capability:

• Current: GET /:recordId/attachments → returns JSON list of attachments
• Add option 1: GET /:recordId/attachments/:blobId → download specific attachment
• Add option 2: GET /attachments/:blobId → direct blob download (simpler)