test runs the guards through bun, not through npm

`test` was "npm run check", so reaching bun meant shelling out to npm
first. It is "bun run check" now — one runner, and npm is out of the
path.

Not the eight-guard chain copied into `test`: that is the same shape of
mistake the rule formulas made before rules.mjs existed, a list written
twice and changed once. `check` stays the only place the guards are
named.

Verified: npm test exit 0, bun run test exit 0, bun run check exit 0.

Worth knowing: bare `bun test` does NOT run this. It is bun's own test
runner, it matches no files here, and it exits with an error. The ways
in are `npm test`, `bun run test` and `bun run check` — which is what
the README already tells you to use.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

package.json

@@ -11,7 +11,7 @@
     "mj": "node tools/mj-queue.mjs",
     "simulate": "node tools/simulate.mjs",
     "check": "bun tools/check-rules.mjs && bun tools/check-kits.mjs && bun tools/check-lang.mjs && bun tools/check-templates.mjs && bun tools/check-behaviour.mjs && bun tools/check-scenarios.mjs && bun tools/check-creatures.mjs && bun tools/check-lethality.mjs",
-    "test": "npm run check",
+    "test": "bun run check",
     "readme": "bun tools/update-readme.mjs"
   },
   "keywords": [],