Update Contact

Every profile field a human can legitimately know about a person -- name, email, phone, job title, state, mailing address, champion flag -- editable from here regardless of the contact's organization's lifecycle stage (build task 2026-08-10: "every person should have a profile... Right now when I go to a person, I can't edit anything"). Deliberately NOT gated the way "Position" is (contact_roles.ACTIVE_CUSTOMER_STAGES, PR #357) -- name/phone/email/title are knowable for anyone, prospect or not. Title (role_title, edited here) and Position (what they do for us, edited through PUT .../roles) are two different facts.

mailing_address -- one call-out worth being explicit about: this is a SECOND writer of contacts.mailing_address. The only prior writer, customer_service.agent_acts.address_update, is ticket-scoped and appends to cs_contact_address_audit for that reason (a b2c consumer disputing what their address was on a given date needs that trail). An account manager correcting a person's address from their profile here does NOT append to that audit table -- it is the same governance every other profile field on this endpoint already gets (a plain updated_at, no per-field history), not a new gap this field alone has.