At a very minimum, we need to ensure that running eventually legacy webservice start ... commands doesn't clobber a buildpack-based deployment. It should look to see whether the managed-by label is "tfb" and if so, refuse to take action.
It would be good if webservice status would output that a buildpack web server is running instead of saying there's no running webservice.
Open question: we probably need webservice restart/stop CLI functionality for buildpack web servers. Should we just reuse webservice for that or have a different set of CLI tooling?