chore(ts): moduleResolution node -> nodenext (CJS) / bundler (ESM)

[pyramation]

Summary

Same convention as constructive-io/constructive-db#3764 (tracked in constructive-planning#2056): retire moduleResolution: node (deprecated in TS 6, removed in TS 7) without changing what we emit or how we publish.

• Root tsconfig.json: module: commonjs / moduleResolution: node -> nodenext / nodenext. No package sets type: module, so nodenext classifies every .ts as CJS and dist/ is byte-identical CommonJS.
• Every tsconfig.esm.json (106 files): + "moduleResolution": "bundler" next to the existing module: es2022, describing what dist/esm is (bundler ESM consumed via the module field). No exports map, no .mjs, no type: module — dist-folder publishing untouched.

Things nodenext's stricter resolution surfaced and how they were fixed:

• graphile-presigned-url-plugin: build.getTypeByName('JSON') is a GraphQLNamedType (may be an input type); real bug hidden by node resolution. Now isOutputType(t) ? t : null.
• graphql/codegen/generate.ts: dropped three await import('./codegen/cli') / import('./output') calls whose targets were already statically imported in the same file (under nodenext a CJS import() is preserved, not downleveled, and needs an extension). Test-file import()s are untouched: ts-jest forces module: commonjs, so they still downlevel to require (verified, suites pass).
• @agentic-kit/ollama resolved through its import entry has no default export; embedder.ts (sdk/constructive-cli) and the codegen template that generates it now use m.OllamaClient.
• parse-package-name@1.0.0 ships types only for its require condition; added an ambient declare module in pgpm/core/src/types/.
• graphile-llm was compiling its __tests__ into dist/; excluded like sibling packages.
• Runtime await import() of hard deps / Node builtins in CJS packages is now preserved by tsc (no longer downleveled to require), and Jest's CJS runtime cannot execute it (A dynamic import callback was invoked without --experimental-vm-modules). This is what broke site-deploy-ssg, graphile-search (BM25 index discovery silently skipped) and the uploads preset tests on the first CI run. pg in graphile-search/bm25-codec.ts and graphile-realtime-subscriptions in graphile-cache/create-instance.ts are declared dependencies, so they're plain static imports now. site-deploy/walk.ts must stay browser-safe, so it loads fs/promises / path via process.getBuiltinModule (Node >= 22.3, engines is >=22), which works from CJS and ESM and is simply absent in a browser. Left alone on purpose: agentic/cli (ESM-only pi), db-tools/pg-fixups.ts (best-effort, pg undeclared), codegen/output/writer.ts (oxfmt is ESM-only, optional) and the ollama embedders (lazy by design, no CJS test crosses them).
• agentic/pi-host depended on @constructive-io/coerce via literal ^0.4.1 (the only non-workspace: intra-repo dep). lerna version's syncWorkspaceLock step then runs pnpm install --lockfile-only and fails with ERR_PNPM_NO_MATCHING_VERSION for the bumped ^0.4.2. Switched to workspace:^; lockfile updated accordingly.

Verification on this branch (CI fully green): pnpm build clean (0 TS errors), pnpm lint 0 errors, graphql/codegen 21 suites / 364 tests + graphile-presigned-url-plugin 24 tests pass, lerna version --conventional-commits --no-push --no-git-tag-version succeeds (127 packages), and pnpm -r publish --dry-run --no-git-checks (what lerna publish delegates to) packs all 121 public packages from dist/ with workspace:^ rewritten to concrete ranges. Sample dist/package.json still has main/module/types and no exports; require('./dist') loads.

Follow-up (separate, mechanical): rewriteRelativeImportExtensions with .ts source imports + makage emitting dist/esm/package.json {"type":"module"} so dist/esm is also Node-loadable.

Link to Devin session: https://app.devin.ai/sessions/d34558e831ad4bbf986f64cc4bd509bd
Open in Devin Desktop: https://app.devin.ai/desktop/session/d34558e831ad4bbf986f64cc4bd509bd?variant=devin
Requested by: @pyramation

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[tenki-reviewer]

Review complete. No issues found — approved ✅.

---

This PR introduces dual ESM builds by adding a tsconfig.esm.json to ~100 packages and switching the root tsconfig.json module/moduleResolution strategy, alongside a handful of targeted code changes. The bulk tsconfig additions are consistent and reference the shared base config, so the ESM rollout is low-risk.

Files	Change
100+ tsconfig.esm.json across agentic/, graphile/, graphql/, packages/, pgpm/, postgres/, uploads/, sdk/	Add per-package ESM build config with module=es2022 / moduleResolution=bundler, pointing at dist/esm.
tsconfig.json	Switch root module/moduleResolution settings to drive the new ESM output.
graphql/codegen/src/core/generate.ts, .../templates/embedder.ts, sdk/.../cli/embedder.ts	Refactor dynamic imports to static and rename @agentic-kit/ollama access from m.default to m.OllamaClient.
graphile/graphile-presigned-url-plugin/src/plugin.ts	Add isOutputType() guard before projecting the JSON scalar.
pgpm/core/src/types/parse-package-name.d.ts, agentic/pi-host/package.json	Add type shim and adjust a dependency version.

Candidate findings surfaced during review were checked against the actual source and did not hold up, so no actionable issues remain.

_{Reviewed commit: 71a4b78}