generate-tests

# generate-tests Generates tests under the base rules and this repo's overlay + manifest. Read all three before generating: - `${CLAUDE_PLUGIN_ROOT}/rules/unit-testing.base.md` - `.claude/coverage/refs/unit-testing.md` (repo overlay) - `.claude/coverage/refs/coverage-manifest.yml` (categories, exclusions, gate) ## Preflight: is this repo on the current kit? Run this before building the worklist, every time, whether or not anyone mentioned an upgrade: ``` python .claude/coverage/tools/coverage-gate.py \ --manifest .claude/coverage/refs/coverage-manifest.yml --print-kit-drift ``` Any state other than `current` means the repo has not been reconciled against today's rules, and a backfill is the worst moment to discover that: a pass run on superseded mechanics wastes every token it spends. Consult `${CLAUDE_PLUGIN_ROOT}/MIGRATIONS.md` ("Preflight") and split what you find: - **`auto` entries governing how THIS pass runs** (refresh the `.claude/coverage/tools/` copies, the fan-out contract, frozen-bug recording): apply them now, silently, and note them in the closing summary. - **`sign-off` entries** (anything that moves scope, the denominator, or the floor): report them in one line and leave them alone. Re-scoping mid-backfill moves the worklist under your own feet. `coverage-redo` is what applies them; say so and carry on with the pass as scoped today. If the state is `current`, say nothing and continue. ## Build the full worklist first — then cover ALL of it (d...