Because there are a few places where the container and the activity interface (ManagedJob from ESI) overlap in function,
 e.g. state change requests and the state model, it would be simpler to keep them as one specification.

I woould argue for separate specs. The activity interface should follow the lead of the container and stay in sync, but 
not risk slowing down the publication of the container spce.