Klever

At the moment code coverage details are specified in rule specs.json. But indeed verifiers collect and output code coverage independently on this option (there is another option in verifier profiles.json and it's in the right place). So this option doesn't affect verification results (indeed there can be some influence but it is the same as for, say, logging).

It will be much easier and convenient to choose code coverage details when starting a job decision. Moreover, in the development mode by default there should be full code coverage, while in the production mode Core should render lightweight code coverage.