Remove "write to the global" coffeescript instructions.

As part of a docs pass we will explain the new way to use coffeescript globals.

(In short: in a package, anything declared with `api.export` becomes
package-level and exported. If you want something package-level and not
exported, or app-level, there's an object `share` and you can assign to fields
on it.)
Update examples to 0.6.5-rc12.
Update docs to 0.6.5-rc12. Link to EJSON binary.
Re-enable cli-test with fake warehouse.
history notes
Add note about is_client and is_server, since tripped me up for an hour.
Merge branch 'devel' into release-0.6.5
update history for new changes.
Minimongo find/findOne support fields options.

First draft.
Check projection object.
Typos.
Simplest tests for minimongo fields.
Minimongo: preserve _id if not explicitly blacklisted.
Some weird nested key paths tests for minimongo.
More tests for minimongo.
Fix regression: display stdout/stderr in the meteor-is-crashed page in development mode.
Docs and typos in minimongo.
Fields filtering should happen *before* transformations.

Since 'fields' options relate to mongo 'find' query, i.e. raw data in mongo, it
has nothing to do with transformed data.
Upgrade to newly release mongodb 1.3.17, instead of using git version.
Fields projection in Cursor.observeChanges works.

Now 'changed' callback is not even called if change didn't affect the result of
projection.

Note: diff.js distinguishes changes only on one granularity level.

Ex.: You have object { foo: { bar: 1, baz: 2 }, qux: "something" }, and you
observe a cursor things.find({}, { fields: { 'foo.bar': 1 } }).

If 'foo.baz' changes, you still get notified as the whole 'foo' field was
changed. However, if you change 'qux' only, callback will not fire.