The best I've found is http://www.ng-newsletter.com/posts/angular-ui-router.html. It doesn't go as deep as, for example, the order in which $stateChangeStart, exampleState.onEnter, exampleState.resolve, and exampleState.templateProvider fire.
A great answer format would be clean. Something like:
Initial pageload of state foo:
- Angular lifecycle step 1
- UI router lifecycle step 1
- UI router lifecycle resolves occur
- UI router lifecycle onEnter fires
- Angular lifecycle step 2
State change foo -> bar
$stateChangeStartevent fires- foo
onExitfires - bar
onEnterFires templateUrlgets the template- UI router plugs back into the Angular lifecycle in the digest loop (or wherever).
Nested states
Multiple named views:
ui-sref clicked
Etc... Thanks!
EDIT: Debugging functions provided enough insight to meet the need. See my answer below for a snippet.