coverage-init

# coverage-init Run once per repo. Discovers the repo's shape and drafts the per-repo config. It DRAFTS; a human reviews and corrects before any test generation. Never proceed to generation in the same turn. ## Precondition — run on the latest production branch (master) The manifest, the detected structure, and the baseline number must reflect the code that ships, not an in-flight feature branch. Before doing anything else: 1. Confirm the repo is on the production branch (master). If checked out on a feature/topic branch, **stop** and ask the user to switch — do not init against feature work. 2. Pull it up to date with the remote (`git fetch` + fast-forward) so the baseline matches the current tip of master. 3. Confirm a clean working tree. Uncommitted local changes skew detection and the baseline; if the tree is dirty, stop and report rather than measuring against unknown edits. State the branch and commit you initialized against in the step 11 report, so the eventual `baseline.ref` is traceable to a real production commit. ## Steps 1. **Detect SDK-style.** Confirm projects are SDK-style `.csproj` (dotnet-coverage only supports these). If any target project is a legacy non-SDK `.csproj`, stop and report it — that project needs coverlet instead and is out of scope for this kit. 2. **Inventory projects.** List `.csproj` files and their references. Identify the test project(s) and what they reference. Identify likely roles (domain, application, infr...