harness: caps/segment event sending should be decoupled
You don't always want a new default segment event to be sent when the caps are changed, and you might want to handle segments yourself.
Any ideas for how to do this in a backwards compatible way?