Coverage with Kover

When the project has no coverage set up

If there is no Kover plugin and no report module, coverage is a thing to propose rather than assume. Say what you would add — the plugin, a report module aggregating the production modules, and a bound set at whatever the codebase measures today — and wait for a yes.

It is worth proposing when a gate would have caught the thing you are working on, and worth skipping when the user asked for one endpoint. Adding a build gate to someone's project is a standing constraint on everyone who commits to it after you; that is their call, not a detail of your task.

One module aggregates, the others are measured

Coverage is a property of the whole codebase, not of each module in isolation — a class in -core is often exercised by a test in acceptance-tests, and per-module reports under-report every shared type.

Put the whole configuration in one report module. The three imports are required; without them none of this compiles.