fix: restore CI test execution and repair CJS/CLI regressions from dependency bumps

[kilisamemarisaaa]

Summary

The test suite has been silently running zero tests in CI since glob was bumped 11 -> 13 (#852, Dec 2025): glob(pattern, cb) no longer accepts a callback (it returns a promise), so suite-runner.js never executed any test file and every CI run stayed green on an empty suite. That hollow green covered four separate regressions introduced by dependency bumps/migrations, all of which this PR fixes.

What was broken and why

1. suite-runner.js ran nothing — glob(pattern, cb) callback never fires with glob v13; run({ files: [] }) passed instantly with exit code 0. Evidence: CI logs show every suite completing in ~0.1s with zero test output, and c8 coverage only reported suite-runner.js itself. Fix: await glob(pattern) inside an async main(), failing loudly on glob errors.

2. fastify start crashed with TypeError: pkgUp is not a function — pkg-up bumped to v5 (chore: bump the dependencies group with 3 updates #896, ESM-only, named exports) while util.js did const pkgUp = require('pkg-up'), receiving the module namespace. Fix: const { pkgUp } = require('pkg-up').

3. fastify start / generate / watch crashed with chalk.x is not a function — chalk bumped to v6 (chore: bump chalk from 4.1.2 to 6.0.0 in the dependencies group #908, ESM-only, default export) while six files did const chalk = require('chalk'). Fix: require('chalk').default in log.js, generate.js, generate-plugin.js, lib/watch/{fork,index,utils}.js. is-docker v4 (same class of bug in start.js) is fixed the same way.

4. CLI parsing broke after the util.parseArgs migration (Replace yargs-parser with Node.js built-in util.parseArgs #887) — cli.js read argv._ which util.parseArgs().values never contains, so fastify --help and fastify <cmd> --help threw Cannot read properties of undefined (reading 'splice'); and generate-swagger --yaml was rejected by strict mode because yaml was not a registered option. Fix: read parsed.positionals[0] for the help command, and register yaml in args.js CLI options (restoring the lenient pre-migration behaviour).

5. fastify generate-plugin emitted an empty "tstyche": {} into the generated package.json — Object.assign(pkg.tstyche || {}, template.tstyche) with template.tstyche === undefined yields {} (regression from the tsd -> tstyche migration, refactor(types): migrate from tsd to tstyche #886). Fix: guard the assignment.

None of 2–5 was visible to users of published versions (7.4.1/8.0.0 still pin pkg-up@^3.1.0), and none was caught by CI because of 1.

Verification

• npm run lint passes.
• Local (Node 24, Windows): test/**/*.test.js now actually executes — 75/83 pass. The 6 remaining failures are Windows-only EBUSY (rmdir on in-use temp/workdirs) and its knock-on effects (chdir leak, leftover generated workdir being globbed); they do not reproduce on Linux (rimraf retry semantics + Linux allows removing a cwd). I left them out of scope rather than masking them.
• The first CI run on this PR will be the first real test run in ~9 months; if unrelated pre-existing failures surface on the matrix, they are separate from this PR's four fixes.

Notes

• First-time contributor — CI approval may be needed.
• 4 commits, one per root cause: suite-runner glob, ESM/CJS interop, parseArgs migration, tstyche emission.