Overlord

Resubmitting for review, since previous could not be reopened from my end.

The test for 3x wrong deactivation code succeeds, but since the explosion is implemented as an exception, Sinatra intercepts it in Development mode and displays the exception instead of rendering the BombExploaded exception code. when running in production, it works correctly.
They seem to have a nice use, especially why doing this sort of thing.

If you just want to run the happy and sad paths to document for the user you can do this:
cucumber --tags @happy_path,@sad_path
And it will only show you the results for those, including the examples. Makes for very clean separation IMHO.