Labels: Backend, Stellar Wave, receipts, database, tech-debt
Complexity: Medium (150)
Description
receipts/receipts.service.ts:206 carries a TODO: replace with actual Supabase/database call. Receipt reads are served from a non-persistent store, so receipts disappear on restart and cannot be shared across instances — which breaks the receipt share and support-bundle flows built in earlier waves.
Acceptance Criteria
- Receipt reads and writes go through the database rather than in-process state.
- Receipts survive a process restart and are consistent across multiple instances.
- The existing receipt normalization and hash behaviour is unchanged.
- Tests cover persistence, not-found handling, and multi-instance consistency assumptions.
Labels: Backend, Stellar Wave, receipts, database, tech-debt
Complexity: Medium (150)
Description
receipts/receipts.service.ts:206carries aTODO: replace with actual Supabase/database call. Receipt reads are served from a non-persistent store, so receipts disappear on restart and cannot be shared across instances — which breaks the receipt share and support-bundle flows built in earlier waves.Acceptance Criteria