Feedback finance dedup overreach no deploy without asking

Justin caught two mistakes in the same session: (1) a recurring-subscription 'fold/dedup' feature merged records that were actually distinct (his and Krystal's separate Canva subscriptions, and YouTube TV price-change history mistaken for duplicate charges), and (2) a related logo/brand-collapse feature (iconKey/getMerchantIconMap) mislabeled unrelated transactions (an AAPL stock dividend reinvestment and Apple Cash P2P transfers tagged with the Apple storefront logo) because regex rules like \bAPPLE\b were too broad.

Why: Any dedup/collapse logic that reduces distinct financial records to fewer display rows is high-risk: same-brand does not mean same-entity (shared household, price changes over time, unrelated transaction types under the same merchant string). Justin also flagged that this was the second time in the session that a build was merged and deployed without waiting for his explicit go-ahead, despite him not having pre-authorized autonomous deploy.

How to apply: For any feature involving deduplication, merging, or collapsing of financial/subscription records by brand or amount: (a) default to conservative/separate rather than merged, especially when household members share accounts or brands; (b) show the exact diff and verification results to Justin BEFORE merging/deploying, every time, not just for large changes; (c) treat 'safety net' heuristics (like amount-matching) as necessary but not sufficient, since price changes over time and multi-user same-brand subs will fool them; (d) when reverting is proposed, revert entirely rather than partially patching, unless Justin says otherwise.

[auto-memory session 86183751-1c8f-47ba-bcc8-7ed0bdf2ed40, confidence 0.85, mode direct]