Use-case specific naming in Tree

[TysonMN]

I would prefer if the Tree type, module, and function used language that was use-case agnostic. Instead, for example, the function that returns the root of the tree is called outcome.

[ghost]

I noticed this naming as well. Bad naming isn't limited to just the tree module, of course. But I'm okay with changing the names in this module to be more general. What names would you propose we use here going forward?

[TysonMN]

From memory, there are the renames that I recall wanting.
Tree.outcome -> Tree.root
Tree.shrinks -> Tree.children