Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
frontend/src/lib/api-types.ts defines StreamEventType as CREATED | TOPPED_UP | WITHDRAWN | CANCELLED | COMPLETED | PAUSED | RESUMED — it omits FEE_COLLECTED, which the backend emits and stores (see prisma/schema.prisma and the /v1/events filter enum). BackendStreamEvent.eventType is consequently too narrow; a FEE_COLLECTED event from the API is not representable in the type, and exhaustive switches over event types won't account for it.
Acceptance criteria
Files to touch
frontend/src/lib/api-types.ts
Out of scope
Telegram: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
frontend/src/lib/api-types.tsdefinesStreamEventTypeasCREATED | TOPPED_UP | WITHDRAWN | CANCELLED | COMPLETED | PAUSED | RESUMED— it omitsFEE_COLLECTED, which the backend emits and stores (seeprisma/schema.prismaand the/v1/eventsfilter enum).BackendStreamEvent.eventTypeis consequently too narrow; aFEE_COLLECTEDevent from the API is not representable in the type, and exhaustive switches over event types won't account for it.Acceptance criteria
"FEE_COLLECTED"to theStreamEventTypeunionFiles to touch
frontend/src/lib/api-types.tsOut of scope