Is there any documentation about the fields in auth.user table? Can I alter it, what parts of supabase-provided auth might break?

Consider a case when we need incremental/progressive sign up - as in sign in via Google/Facebook, provide phone number before placing order, etc. If developer has home built SMS verification solution then how can [s]he integrate it to auth.user?