Remove custom wire protocol and replace with REST API over HTTP

The slim custom wire protocol for 1.0.0.Alpha1 is premature optimization; there's no need to shave bytes on the protocol when the intended payload is a deployable archive. Implementing as HTTP (via some RESTful API) will pave the way towards fulfilling feature requests for secure transfer (ie. SSL) and authentication/authorization (ie. BASIC).