Why did haproxy job ignore standard naming scheme for monit control script and use "haproxy.init" instead of "haproxy_ctl"?

There is a very obvious naming convention in all bosh releases. The `monit` script calls a script called `bin/JOBNAME_ctl [start|stop]`. 

But the haproxy job named it `bin/haproxy.init`. Why?

a) its not just for "init" since it also includes the "stop" command
b) it ignores the convention set out in every other job (in all public bosh releases) and makes comprehension and discoverability more difficult