Add UserTags schema
Add packages dir back to repo

Meteorite used the packages directory to store links to all the
dependencies -- so gitignoring it was prudent to avoid sharing broken
symlinks.

But Meteor >v0.9 uses it to store local code that is packaged.  In
particular, we need npm-container to be there to avoid crazy dances when
bundling. It should be safe to not .gitignore it and add all its
contents now.
Upgrade houston to fix spiderable

Fixes #98.
Add bootstrap. Fixes #87.
Upgrade meteor 0.9.3 => 0.9.3.1; add flash msgs
Add basic logging and error display utility

Defines a gloal ``logger``, with methods ``error``, ``info``, and
``debug`` for basic handling of any logging needs.

For displaying errors or info messages to the client, use the following
to both log errors as needed and display a flash message to clients:

    logger.reportInfo("Message to display");
    logger.reportError("Message to display", errorObj);

This framework is intentionally light right now -- it mostly just
shadows ``console.log``.  However, we can use this abstraction to easily
plug into any other logging services such as Loggly, Airbrake, or
whatever else -- or alternatively, implement our own fancier log handler
and sysadmin emailer with it.

With this change, we can regard any appearance of ``console.log``
outside of ``lib/logging.js`` as a bug.  ``console.log`` thus remains
useful as a tool for debugging during development, but all such logging
statements should be removed or converted to ``logger...`` variants
before commiting.

Pertains to issue #94.
Use console.log when outside Meteor environment

The testrunner doesn't have access to the Meteor environment, so just
use vanilla logging there.
Remove meteorite leftovers
Merge master