Enable the Emails / Calendar reader on custom objects (the read path already looks generic)

What I'm trying to do We run a construction business on Twenty. Our real unit of work is a Project (a custom object) that a deal converts into. We'd love the Emails tab — the actual inline thread reader — to appear on a Project record the way it does on People, Companies, and Opportunities, so the correspondence for a job is readable on the job. Today custom objects don't get the Emails/Calendar tabs. From reading the code, that looks deliberate rather than missing (see #19544, "Skip email/calendar tab creation for custom object record page layouts"), and I completely understand why it was scoped out. But the surprising thing is how *close* the rest of the stack already is to supporting it, so I wanted to raise it as an idea and offer to help. What I found in the code (main) The read path is almost entirely object-agnostic already: • Frontend reader is generic. EmailsCard (packages/twenty-front/.../activities/emails/components/EmailsCard.t…