Don't auto-merge/dedupe finances; don't deploy without being told

Justin (2026-07-08): "stop merging and deploying, I tell you when to do those things."

Two distinct corrections:

1. Do not auto-merge / dedupe finance records. Fragmented-looking rows are often genuinely separate. Concretely: he has two Canva subscriptions (his + Krystal's), separate Crunch Fitness and Planet Fitness memberships, and YouTube TV entries that reflect a real price change, not duplicates. The brand+amount recurring fold I shipped wrongly collapsed these. Logo brand-collapse is fine (same logo); RECORD identity (subscriptions, transactions) is finer than the brand and must not be silently merged.

Why: merging distinct subs destroys real information (who pays for what, price history, per-person accounts) and is hard to notice after the fact.

How to apply: never fold/dedupe/merge financial rows by brand, name, or amount without Justin explicitly asking. When something looks like a duplicate, SHOW him and ask; don't merge.

1. Do not deploy or merge to main without an explicit instruction each time. Build and verify in an isolated slot, then STOP and present the change. Wait for Justin to say "deploy" / "merge" / "ship it." A prior approval does not carry to the next change. [[feedback_robust_over_quick]]

Why: repeated unprompted deploys removed his control over what goes live on his real financial data.

How to apply: default to branch + build + verify + REPORT. Deploy/merge only on an explicit per-change go.