Forced consideration of long chain, expands only, plan in the query plan...

Forced consideration of long chain, expands only, plan in the query plan solver
I think <code>tryPlan</code> should not be exposed on the trait since it is only used internally.

What about implementing a template method pattern with an abstract class having the <code>tryPlan</code>?