Fix Node test discovery (#1)

Run Node built-in tests using an explicit test-file glob and record the verified fix.

Author: Hhh2178

docs/logbooks/daily/2026/2026-07/2026-07-10.md

@@ -0,0 +1,31 @@
+# 2026-07-10
+
+## Intent
+
+Fix the test command so Node's built-in test runner executes the repository's test files instead of treating the `tests` directory as a module.
+
+## Changed
+
+| Area | Files | Purpose |
+| --- | --- | --- |
+| Verification | `package.json` | Target `tests/*.test.mjs` explicitly in the test script |
+
+## Verification
+
+| Check | Result |
+| --- | --- |
+| `npm run harness:verify:project` | Passed |
+| `npm run type-check` | Passed |
+| `npm test` | Passed (9 tests) |
+
+## Decisions
+
+- Keep the test scope explicit and continue using Node's built-in test runner.
+
+## Risks
+
+- New tests must continue to use the `*.test.mjs` naming convention to be discovered by this command.
+
+## Next
+
+Commit and push the fix so GitHub Actions can rerun with the corrected command.

package.json

@@ -33,7 +33,7 @@
   "scripts": {
     "build": "tsc -p tsconfig.json",
     "type-check": "tsc -p tsconfig.json --noEmit",
-    "test": "npm run build && node --test tests",
+    "test": "npm run build && node --test tests/*.test.mjs",
     "verify:harness": "node scripts/verify-harness.mjs",
     "harness:verify:project": "npm run verify:harness",
     "harness:verify:workspace": "npm run type-check && npm test",