Add instructions about the use of conditionals
Improve error message on undefined value
Add interpolator
Rename NodePresenter to ConditionalResolver
Refactor node presenter to invoke conditional resolver
Integrate variable interpolation to Engine#evaluate_node
Add interpolation instructions to readme
Bugfix: interpolation needs to work with parslet slices

the parser actually produces parslet 'slices' rather than strings.
A parslet slice behaves like a string but doesn't have all of
the methods of string.

So, interpolate needs to #to_s the thing it receives to be able to
handle slices.

This test is to document that fact and catch any regressions.
Bump to version 0.0.3
Merge pull request #14 from alphagov/bump_to_version_0.0.3

Bump to version 0.0.3
Merge pull request #13 from alphagov/interpolation

Interpolation
Get next node from start button

This was an intended behaviour all along. If next node rules are not
defined then they will be taken from the start button.
Merge pull request #15 from alphagov/next-node-from-start-button

Get next node from start button
Use question name for input variable name

The next-node transition rules have until now been independent from
question definitions. However, now that questions can be named
explicitly then we should use the question name when capturing the input
value.

It was an oversight to have missed this when I implemented the choice
question tag with an explicit question name.