You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 38c136a
Browse filesBrowse the repository at this point in the historyBrowse files
fix(comms): a send the log never heard about, and the 61% of a relationship it could not see
Two defects, same consequence: the comms log reports success while missing real
correspondence, and it misses it in the direction that looks like silence rather than like
an error.
1. `iris mail send` with --from/--cc/--attachment sent the email and recorded NOTHING. Those
flags have no router path, which is a reason the send cannot be ROUTED — it is not a
reason it cannot be LOGGED. The CLI printed "not logged to comms" and moved on, quietly
reintroducing the failure CR-8 existed to remove. Transport and bookkeeping are separate
concerns: the bridge still carries those sends, and `recordDirectSend` now puts them on
the ledger afterwards. A draft is excluded — it has not gone anywhere, and logging one
would put a message on someone's record that they never received. When the record fails
it says SENT BUT NOT LOGGED with the reason and the command to fix it, because the one
thing this must never do again is look fine.
2. The ingest only ever searched `lead.email`. A lead has one primary address and any number
of alternates in contact_info.emails, and everything written from an alternate was
invisible. Measured on lead anomalyco#10394 today: 27 messages on the primary the ingest reads, 43
on the two it did not — 61% of the correspondence absent from a log that returned "1 new,
0 skipped" and called it done. He is Apple-native and writes from iCloud; the address we
filed him under was his work one. That is not an edge case, it is the common case for
anyone with a work and a personal address.
`leadEmails()` is now the single answer to "what addresses is this person reachable at",
and both the Apple Mail and iMessage paths use it. The bridge filters on one `from` per
call, so it is one search per address; the server dedups on external_message_id, so an
overlapping address costs a round trip rather than a duplicate row.
Not fixed here: the bridge search is capped at days=90, so a backfill cannot reach further
back than that no matter how many addresses it knows about.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01FEVuQjtBdw2Mq3EpE56GFY
0 commit comments