A try should be immutable and repeatable. It should maintain the full state of an execution, including scorer used.

[david-fisher]

Is your feature request related to a problem? Please describe.
If I change the scorer, I should get a new try, which remembers that scorer, so that I can easily return to that try and review the results.

Describe the solution you'd like

Each try should maintain the following state:

Search endpoint used
tuning parameters
query
results list
scores for the result
scorer used

If I make a new judgment, the value for the single score is updated (and propagated to the book.
If I change the query, I get a new try.
If I change a tuning parameter (including displayed fields), I get a new try.
If I change the endpoint, I get a new try.
If I change the scorer, I get a new try.