I realized this, but instead of making the name very long and descriptive, I've made the taskId unique. This is because even if you put browser version into the name, what if platformName changes or platform version, or what if someone used the same capability multiple times.

I've made the taskId as #(capabilityId) if we don't shard the test and #(capabilityId)(specId) if we shard the test, so you could have something like this:

```
[launcher] chrome #1a passed
[launcher] firefox #2a passed
[launcher] chrome #1b passed
[launcher] firefox #2b passed
[launcher] chrome #3a passed
[launcher] chrome #3b passed
[launcher] chrome #4 passed
```

Then you can cross reference the header with the taskId to see the details of the platform

i.e. 
```
PID: 96433 (capability: firefox #2b)
Specs: /workspace/protractor/spec/basic/lib_spec.js
```

Let me know if you think it's better to just spell out all the capability details in the name