- Shipped
- November 13, 2026 at 5:30 AM UTC
- Author
- Kamo
- Commit
- 182b112
users.address_residence_id / address_shipping_id point at user_addresses, and nothing ever wrote either: the table held no row on the whole platform, so a home address could not be kept anywhere. PUT /api/security/members/{id} now takes homeAddress and mailingAddress (MemberAddressWire's shape, same validation) and homePhone (users.u_phone_*), written to the person's own user_addresses rows by the new UserAddressBook. They are USER-account fields, so the legal name's rule governs them: the person, or a platform operator. GET returns them to the same audience.