Optimized Client Continue

We'll want to look for ways to optimize the client-side continuation code. Instead of regenerating the entire app on the client, we should look to build something similar to Aurelia's progressive enhancement capability, that rather than creating DOM, uses the DOM that is already present. It's more complex than enhance though, since binding has already taken place, repeaters have already rendered, etc. We just need to connect up component classes and bindings and "continue" from that point on.

No files, tests, or entry points are named. Start by locating the client-side continuation code and the existing enhance behavior, then determine how server-rendered DOM, completed bindings, and rendered repeaters are represented. Done means connecting component classes and bindings to the existing DOM without regenerating the entire app.

Written by the indexing model from the issue text.