Add documentation to Lore describing a proposal for urgent unplanned work. Currently it is to create a new issue and label it as "Unplanned Work". If you are going to work on it then assign it to yourself and move to In Progress. If you are not going to work on it, then put it at the top of TODO. In either case bring it to the team's attention. Finally be sure to paste any IRC or email conversations as well as comments as you debug and discover (or don't discover) root cause.

Currently, when a test fails, it provides information on what failed and why. If it passes, there is no output. This is not a best practice, because it makes tracing issues in the CI system difficult. For example: #18 failed in Travis-CI, but passed in BonnyCI, and it's tricky to see that the tests actually passed in the BonnyCI log, because it never says it passed.

Required:

• Scripts at tests/*.sh print a message indicating success when the test completes successfully
• Failure message is still clear (or unchanged)

Requirements:

• README.md is rendered on GitHub
• README.md is not rendered on the production site
• README.md contains a Travis build status badge on GitHub
• README.md directs the user to the production site

There are links in other repos which point to lore that need to be updated to point to bonnyci.org.

This helps with diffs on small changes, and it's also just more friendly to terminal based editors who tend to size around 80 - 120 chars.

I think we can do this phased in, maybe have something lint only changed files, but eventually I'd like to seem them all wrapped.

Quick tip for Vim users:

V-I-P will select the current paragraph. Then typing !fmt will use the unix fmt command to wrap the text at 72 chars.