♻️ Run doc-test generation as an explicit CI step

Drop the `pretest:ci` lifecycle hook and call `create:doc-tests` from the
`build` job before `test:ci`. The hook hid the step from the job log and
made `test:ci` behave differently under npm than when run directly.

development/docs.md

@@ -55,3 +55,7 @@ Compile every `ts / `typescript fence in the prose docs into a real
   (`git ls-files 'src/*.test.ts'` — the generated files are untracked), and
   `test:doc` runs the examples in a separate process without c8. `test:ci`
   chains the two, so correctness and coverage stay independent.
+- The CI `build` job runs `npm run create:doc-tests` as an explicit step before
+  `npm run test:ci`, not a `pretest:ci` lifecycle hook: the hook hides the step
+  from the job log and makes `test:ci` behave differently under npm than when
+  run directly.