Arnas Donauskas 8ac764e3b8 fix(flows): redact customer text from reply_received event payload ... The `reply_received` event was persisting `text: message.text` verbatim into flow_run_events.payload. A customer prompted "what's your card number?" by a collect_input node would leave the PAN sitting in the events table forever, surfaced via the runs viewer to anyone with access. Switch to `text_length` only. The `node_entered` event already records `captured_length` for the same reason after a successful capture; this makes the asymmetry symmetric. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-22 15:35:42 +03:00
..
app	feat(flows): templates + v1.5 nodes (collect_input/condition/set_tag) + run-history viewer (PR 4/4)	2026-05-22 14:27:01 +03:00
components	Merge remote-tracking branch 'origin/main' into feat/flows-unsaved-changes-guard	2026-05-22 15:16:35 +03:00
hooks	feat(beta): per-account beta_features flag on profiles, gating Flows	2026-05-22 12:57:33 +03:00
lib	fix(flows): redact customer text from reply_received event payload	2026-05-22 15:35:42 +03:00
types	feat(flows): foundation for interactive WhatsApp messages (PR 1/4)	2026-05-22 13:12:27 +03:00
middleware.ts	Initial scaffold: WhatsApp CRM with Next.js + Supabase	2026-04-16 18:17:31 +03:00