- Shipped
- September 18, 2026 at 6:11 AM UTC
- Author
- Kamo
- Commit
- fa25989
Four surfaces showed a member by name with no id beside it, so the console's member card had nothing to open. Each now sends the id as TEXT next to the name it already sends (a 19-digit id read as a JSON number is rounded into somebody else's), and only where that name already reaches the caller. - Reply quotes: wireFields adds parentSenderMemberId beside parentSenderName. A web-chat visitor's words are stored under the org's system member, so a visitor's parent carries none — on the live send and on the history read alike, whether or not the visitor gave a name. A system-bug thread withholds it with the name, against the parent's organization. Exec2Exec rows carry it too; the console keeps them plain. - Hold'em: each hand-history line (ActionView) carries memberId, read off the same hand-seat row as the name, so the two cannot name different people. - Support tickets: every system event stores actorMemberId beside actorName. An event that names its own actor (the AI handoff reads "AI Assistant", stored under the system member) drops the stored id. - System bugs: each thread row carries memberOrgId beside memberId, withheld with it. The board is global, and the org is how the console tells a colleague from another organization's member. Tests: ChatReplyPreviewWireFieldsTest, SupportSystemEventActorTest (new); SystemBugThreadRedactionTest (+4), HoldemTableViewTest (+1). Each fails with its change reverted. Full suite 1005/1005 green; clean origin/main was 994/994.