Update History.md
Fix JSDoc template
Improve packages concepts section
Improve "deploying" section of docs
Simplify the word "obviates" into "removes"
Improve the templates concepts section
Improved formatting for what is meteor
Version bump for rc.6
Update contributors for 0.9.4
Update license file.
Allow `null` in appId check. This can happen when a client passes
`undefined` for appId and it gets translated to `null` by DDP.
Hide spurious message that pops up sometimes. Users don't need to see
this "everything is OK" message. (Especially since sometime we sync right
after printing it!)
Bump versions for -rc.7
Re-order and linewrap History entries. No content changes.
Rewording pass over History.md
Work towards fixing the "do-not-update-to-rcs" self-test.

The test was failing because it was written to run against the real
local warehouse, instead of a stubbed one. When initializing the
Sandbox with an explicit warehouse, the test failed because of
incorrect logic piping the right path to the packages database
(in this case "test-packages.data.db" instead of "packages.data.db").

Unfortunately, the test still fails -- this time potentially due to a bug:
After publishing the package for the first time with `--create`,
the next step tries to update but gets the following error:
    There is no package named test:i1iyhj. If you are creating a
    new package, use the --create flag.
Revert "Work towards fixing the "do-not-update-to-rcs" self-test."

This reverts commit 89b394d9744a6b6399b469c2801dee73264f4626.

I cherry-picked the change onto devel, since this change isn't
even supposed to change the behavior of the tool. Why risk
it just before the release? Thanks @nim for the suggestion.
Update todos
Update banner.json
Add 0.9.4 heading to History