Failed assertions no longer repeat message.

Failed assertions no longer repeat the assertion message as a comment. In my
Node.js `assert` module function wrappers, I was printing the assertion message
passed into the assertion function as the assertion message. To be thorough, I
printed the assertion message of the caught `AssertionError` as a comment.
However, the `AssertionError` message is, of course, the same as the message
passed into the assertion, the assertion message. It was redundant. It is no
more.
Failed assertions no longer repeat message.

Failed assertions no longer repeat the assertion message as a comment. In my
Node.js `assert` module function wrappers, I was printing the assertion message
passed into the assertion function as the assertion message. To be thorough, I
printed the assertion message of the caught `AssertionError` as a comment.
However, the `AssertionError` message is, of course, the same as the message
passed into the assertion, the assertion message. It was redundant. It is no
more.

Updated `vendor/twinkie` to support upstream changes made for CoffeeScript
1.3.1.
Merge branch `redundant` into `travis-ci`.
Failed assertions no longer repeat message.

Failed assertions no longer repeat the assertion message as a comment. In my
Node.js `assert` module function wrappers, I was printing the assertion message
passed into the assertion function as the assertion message. To be thorough, I
printed the assertion message of the caught `AssertionError` as a comment.
However, the `AssertionError` message is, of course, the same as the message
passed into the assertion, the assertion message. It was redundant. It is no
more.
Update build for CoffeeScript 1.3.3.

Updated for CoffeeScript 1.3.3. Mostly changed owing to octals.

Also, NPM doens't like self dependency any more, so test have been updated to
reference the project's `lib` directory.

Updated `vendor/twinkie` to support upstream changes made for CoffeeScript
1.3.1
Merge branch `redundant` into `travis-ci`.
Update build for CoffeeScript 1.3.3.

Updated for CoffeeScript 1.3.3. Mostly changed owing to octals.

Updating to use production Streameline.js, instead of my stop-gap Streameline.js.

Also, NPM doens't like self dependency any more, so test have been updated to
reference the project's `lib` directory.

Updated `vendor/twinkie` to support upstream changes made for CoffeeScript
1.3.1
Merge branch `redundant` into `travis-ci`.
Update build for CoffeeScript 1.3.3.

Updated for CoffeeScript 1.3.3. Mostly changed owing to octals.

Updating to use production Streameline.js, instead of my stop-gap Streameline.js.

Also, NPM doens't like self dependency any more, so test have been updated to
reference the project's `lib` directory.

Updated `vendor/twinkie` to support upstream changes made for CoffeeScript
1.3.1
Merge branch `redundant` into `travis-ci`.
Correctly summing assertions.

Apparently, I forgot to update some variables after I cut and paste of the line
formatting code from the detail lines to the summary line.
Merge branch `master` into `travis-ci`.
Merge branch `sums` into `travis-ci`.
Release 0.0.2.

Version bump and updates to change log. If this passes tests, it gets pushed to
NPM so that my NPM tests get the nice new summary line.
Merge branch `release-0.0.2` into `travis-ci`.
Remove `proof` as dependency of itself.

NPM does not like installing `proof` as a dependency of itself. This is in the
`.travis.yml` file, not in the `package.json`.
Remove extra call to `npm install`.

I believe the first call to `npm install` is unnecessary. The second call does
it all. We could have two calls, one that reads the `pacakge.json`, the second
that adds `streamline`, but that would be to chatty.

Note that `streamline` is not a build dependency. It is only run if a test
executes one of the `streamline` executables.
Merge branch `travis-ci` into `release-0.0.2`.
Merge branch `release-0.0.2` into `master`.
Check spelling. Proofread `README.md`.

Removed the motivations section. There's enough about Proof that is different
from other frameworks now to distinguish it. It doesn't require so much
exposition. People will ask why, I'm sure, but I'm beyond caring. I have love
for my non-framework. I don't need to invite a debate about NIH, bike sheds, &c.

Removed reference to the special `$teardown` property in the context object
returned harnesses that no longer exists.

Closes #9.
Closes #10.