> which failed to drive chrome so it wrote its own chrome driver protocol server

This is one of the things I hate the most. Super complicated workarounds which take loads of time (and sometimes money) for even the simplest problems. Human would pause and ask. I would blame harness, not the model though.