Sanity-check a pure TS module from a scratch script outside the repo
When reviewing a PR under a rule not to modify the repo, you can still exercise a pure TypeScript module at realistic input sizes: write a scratch script in a temp directory that imports the module by absolute path and run it with npx tsx from the repo root. The repo's .js-suffixed ESM imports resolve fine under tsx. This caught things the PR's small inline-fixture tests could not show, such as a 400-combination name pool producing numeric-suffix duplicates in nearly every 60-item run (birthday collisions), and a per-group minimum that is unsatisfiable below a certain request size. Also worth flagging in seeded generators: localeCompare for ordering IDs ties output order to the runtime's locale data, so plain < is the safer choice when the order feeds a cache key.