Wizard and Scripts
==================

We'd like Wizard to be sufficiently general so as to not work
on Scripts. To some degree, it already is; Wizard can be easily
set up in a development type environment on a non-Scripts server.

Here documents Scripts specific code inside Wizard that should
be moved away:

    * We store Wizard info inside .scripts/; this should really be
      .wizard.  This might be kind of crappy to change, though.  Maybe
      .scripts should still contain Scripts specific info, but we
      should instantiate a .wizard directory automatically (which should
      be ignored) that doesn't need to be created in repositories.

    * [HOOK] wizard.install contains strategies for guessing variables
      for an installation that are Scripts specific

    * We should have `wizard install` do something intelligent about
      prompting a user about possibilities; not everyone is going to
      use the scripts-start wrapper.

    * [DEFER] The mass-* commands are especially designed for Scripts,
      so while they're ostensibly portable, they'd probably need a bit
      of working to be easy-to-use for other people.  They also rely on
      a "versions" directory whose code exists independently of Wizard.