an enterprise prospect is evaluating Coder, and has provided feedback that a second stage of approval after coder templates push would be nice to have.

currently, template changes are handled directly from the template admin and are accepted as the source truth. instead, changes could just request code review of a peer prior to being pushed in. the template owner could be notified via email; "Request for a change in X template."

This will give more administration control to the flow, and will draw a clear line of responsibilities on who is the owner/responsible to maintain templates.