First Regression Contribution

Add a focused assertion to an existing test case, then use the repository’s test commands to check the change. Keep the contribution to one behavior and one small change per task group.

Use Node 22.13.0, the version pinned in .nvmrc; the package requires Node >=22.13.0.

Add and verify the assertion

  1. Choose one behavior within the scope of an existing test. For example, tests/reminder-time.test.mjs groups clock-normalization checks in a named test case and uses assertions such as assert.equal(normalizeClockTime('15:07:00'), '15:07');.
  2. Add a focused assertion to the relevant existing case. Base its expected result on the behavior and acceptance criteria for your change.
  3. From the repository directory containing package.json, use the package commands below. The testing guidance lists all three as required before merge.
Command Scope
npm run test:source Runs Node’s test runner with --experimental-strip-types over six explicitly listed files, including tests/reminder-time.test.mjs.
npm test Runs npm run build first; if that succeeds, starts Node’s test runner with the Cloudflare registration shim and ./tests/*.test.mjs.
npm run lint:baseline Runs the lint-baseline check through scripts/sites-env.sh; the testing guidance states a 173-warning baseline ceiling.

[!NOTE] The declared test commands do not establish the result for a new assertion. Run the relevant package test command against the unchanged behavior and confirm the assertion fails; then make the correction, rerun the same command, and confirm it passes.

Updated