Field-transform hooks in twenty-orm (encrypt / tokenize / redact selected fields)

What I'm asking for A small, opt-in extension point in twenty-orm that lets a feature module transform selected object fields on the way into Postgres (persist) and on the way back out (read), keyed by object and field. One place to register, two directions: a persist transform and a read transform. Twenty already has half of this. The common result getters pipeline post-processes every record on the way out. What's missing is a symmetric persist-time transform, and a way for a module to register into both without editing WorkspaceRepository and the result-getters service by hand. Why Some fields in a Twenty workspace are the sensitive part: a person's name, phone, email, the company they work at. A growing number of teams want those columns to be ciphertext at rest (or tokenized, or redacted for people without a role), while the app keeps working with plaintext in-request. The shapes that need this: • Field-level encryption against a KMS, an HSM, o…