- Shipped
- August 26, 2026 at 2:48 AM UTC
- Author
- Kamo
- Commit
- 7b5c9b2
Several leads commonly hang off one account precisely because they are the same person enquiring twice, and each of their calls was matched to whichever lead held the number at the time. So "this customer's communications" is the union of the account's own rows and every one of its leads' — reading one lead's timeline answers a narrower question than the one being asked. findUidsByAccount projects uids rather than entities on purpose: Lead sits in a JOINED inheritance hierarchy, and selecting entities here would drag the whole fetch plan in to produce a list of ids. PhiResourceType.ACCOUNT so the account timeline's audit rows name what was actually read. Appended, never inserted — the enum is ordinal-persisted.