Bridge launches another routine to handle actual transmission.
Tactical strike to remove the old logger.
Embeddable default context. Default context in a box. Boilerplate reducer.

Embeddable types & interfaces = very yes.
Ahhh it's infectious.
Oh noooo.
Merge branch 'feature/ref-logging' into feature/bridge-concurrent
Merge branch 'feature/bridge-concurrent' into develop
Merge branch 'master' into develop
Merge branch 'develop'

Here goes nothing.

ApplicationController has been replaced with an embeddable context.
So long as their method-sets don't intersect: they can be accessed unqualified.
Otherwise one simply needs to call `<instance>.App.<context>` to access an inner context.

If you really wanted to: you could override the methods and call the App controller [or not]
to hijack the contexts for your own controller.

This is the first step on the way to request lifecycle `hooks` which will intercept and wrap
a  request by default. (Two hooks are planned: request logging, and a catch-all `panic trap`)