KV: early-access-data blob has no TTL and grows unbounded

[davidcampbelldc]

Problem

The early-access-data KV key stores the entire waitlist CSV as a single blob. It grows with every signup and has:

• No TTL — never expires
• No size cap — KV values max at 25 MB, will silently fail at the limit
• No cleanup — old entries are never pruned

Written by functions/api/early-access.js and functions/api/clean-csv.js, read by functions/api/early-access-csv.js.

Risk

Low velocity (signups are infrequent) but unbounded by design. If this ever becomes higher-volume, it'll hit the 25 MB KV value limit with no warning.

Fix Options

1. Add a TTL (e.g., 90 days) — but this is the canonical store, losing it would be bad
2. Move to D1 or R2 for structured storage (proper solution for growing data)
3. At minimum, add a size check/warning log when the blob exceeds a threshold (e.g., 1 MB)

Files

• functions/api/early-access.js (line ~764/787)
• functions/api/clean-csv.js (line ~83)
• functions/api/early-access-csv.js (read-only)

[davidcampbelldc]

Follow-up report

From: AWS Notifications no-reply@sns.amazonaws.com
Date: 2026-03-06

Same issue as prior 5 alerts. No change in status: nginx missing, 5/6 containers running. Issue #105 (post-deploy smoke test for prod nginx routing) is directly related.

Auto-added by Mandy from email follow-up (message 19cc21a9e8477f39)

[davidcampbelldc]

Follow-up report

From: AWS Notifications no-reply@sns.amazonaws.com
Date: 2026-03-06

Same alert pattern continuing. No change in status — still 5/6 containers, nginx missing. Consider suppressing further alerts until issue #105 is resolved to reduce noise.

Auto-added by Mandy from email follow-up (message 19cc2530f23d929c)