Add Tests for GitHub Top 100

These are the GitHub Top 100 projects - everything that doesn't run in a CLI removed.
- [ ] 04) Node
- [x] 10) Rails (uses Ruby)
- [x] 12) Meteor (uses Node)
- [ ] 14) Oh-my-zsh
- [x] 19) httpie (uses Python)
- [ ] 26) Docker
- [x] 28) Jekyll (uses Ruby)
- [ ] 47) Ionic (uses Node)
- [x] 51) json-server (uses Node)
- [ ] 52) phantom-js (uses Node)
- [x] 53) Django (uses Python)
- [ ] 54) Ember.js (uses Node)
- [x] 63) Redis
- [x] 64) Neovim
- [x] 66) less.js (uses Node)
- [x] 67) Bower (uses Node)
- [x] 68) Gulp (uses Node)
- [ ] 70) hhvm (uses C++/PHP)
- [x] 76) Coffeescript (uses Node) (Special note: CoffeeScript is universally hated, but still in use)
- [ ] 84) io.js (uses Node) (Special note: Merged back into Node.js)
- [ ] 86) ElasticSearch (uses Java)
- [x] 99) Rust (Special note: Impressive growth; newcomer)

No files, tests, or entry points are named. Start by identifying the repository's existing test harness and how the completed checklist items were tested, then determine the scope and completion criteria for each unchecked project.

Written by the indexing model from the issue text.