Hmm. ok thanks.
My two cents: That is a potential source for error and unexpected behavior. Circumventing the lifecycle hooks and having to always think of triggering these manually feels very “low level”-ish… I am pretty sure that I will forget to call them here and there 
So I will stick to
strapi.query('restaurant').update({...}, {...})
for now…
Consider this a feature request:
“As a Developer I would like to query documents via strapi API (find() or findOne()) that I can alter and persist again using document.save(). This would basically be a helper method that calls the underlying mongoose .save() function AND also triggers the strapi lifecycle methods.”
BTW: Where is the best place to submit feature requests, if these are welcome?