Consolidate testing steps into `tools/test`.

I've opted to run with `--coverage` to ensure that we continue exercising coverage support. Hat tip to @wlonk for holding me accountable on this - I had thought coverage was broken, but I was holding it wrong.

Also adjusts the code coverage failure thresholds to match here-and-now reality. I'm not offering a policy thought here, just making sure we

1. use the coverage checking we have, and
2. set standards we are actually achieving.

This was originally part of [another proposal][pr-6]. I've broken it out to make the intent clearer, and to make the proposal easier to get a handle on in isolation from other, related changes. Thanks to @wlonk for their input on this!

[pr-6]: https://codeberg.org/ojacobson/pilcrow/pulls/6

Merges prop/test-tool into main.

1 files changed, 4 insertions, 4 deletions

diff --git a/vite.config.js b/vite.config.js
index 4bd448f..fcf28aa 100644
--- a/vite.config.js
+++ b/vite.config.js
@@ -13,10 +13,10 @@ export default defineConfig({
     restoreMocks: true,
     coverage: {
       thresholds: {
-        statements: 49,
-        branches: 60,
-        functions: 14,
-        lines: 49
+        statements: 12,
+        branches: 85,
+        functions: 75,
+        lines: 12
       },
       exclude: [
         ...configDefaults.exclude,