- Ya
- 21 Agosti 2026, 03:35 UTC
- Mwandishi
- Kamo
- Ahadi ya
- b2f048b
Matching is point-in-time by design — a contact point only claims traffic inside its window, so editing a lead cannot retroactively rewrite history. The cost is that a lead entered after the conversation started can never show that conversation, and the member has no way to say "this address was already theirs". linkHistoric is that way. It widens exactly one thing, the window, and nothing else: the address must still be a contact point of that exact lead, in that exact org, in some window. It cannot invent a match, cross a tenant, or reach a lead that never held the address — the tests pin each of those, because all three fail silently, as mail attached to the wrong lead reads as a lead who really did write to us. LeadService gains the seam that carries the member's intent (an optional LeadEmailBackfillTrigger, absent in services with no mail access) and both request DTOs gain the flag. The flag is deliberately not persisted: it describes one save, and every existing caller — imports, intake endpoints, MeridianLink patches, the lock sweeper's auto-save — sends nothing and so acquires no mailbox scan it never asked for.