technically, mojito apps do not require an application.{json,yaml} since specs can be provided by other means. Maybe I missed the discussion of removing this "feature"; I understand that supporting the no-application.json case was a pain point in the past.

by the way, `mojito start` will exit with an error/warning if the current working directory doesn't:
1. have a package.json
1. doesn't declare "mojito" in the dependency field