feat(node-type-registry): blueprint type codegen — TS types from node type definitions

[pyramation]

Summary

Adds a TypeScript codegen script (src/codegen/generate-types.ts) that reads the existing allNodeTypes array and produces blueprint-types.generated.ts — a set of TypeScript types matching the JSONB shape expected by construct_blueprint().

Motivation: Replace the hand-crafted 963-line GraphQL plugin approach (PR #907) with generated client-side types. The GraphQL API stays simple (plain JSONB), while consumers get autocomplete and type safety when building blueprint definitions in TypeScript.

What's generated (916 lines):

• Per-node-type parameter interfaces derived from parameter_schema JSON Schema (e.g. DataIdParams, AuthzDirectOwnerParams)
• BlueprintNode discriminated union (string shorthand 'DataId' or typed object { $type: 'DataId', data: DataIdParams })
• BlueprintRelation discriminated union for 4 relation types
• Static structural types: BlueprintField, BlueprintPolicy, BlueprintIndex, BlueprintFullTextSearch, BlueprintTable, BlueprintDefinition

Cleanup: removed dead blueprint-types plugin + NodeTypeRegistryPreset

• Deleted graphile-settings/src/plugins/blueprint-types/ (3 files, ~730 lines) and its test file (~270 lines). These were the hand-crafted GraphQL plugin approach that this codegen replaces — never imported by any preset or consumer on main.
• Removed blueprint-types exports from graphile-settings/src/plugins/index.ts.
• Deleted node-type-registry/src/preset.ts (NodeTypeRegistryPreset) — it imported createBlueprintTypesPlugin from the now-deleted plugin. This preset is no longer needed; consumers should use the generated TS types directly instead of GraphQL input types.
• Removed graphile-settings and graphile-config from node-type-registry dependencies (only used by the deleted preset). This significantly reduces the package's dependency footprint.

AST-based codegen via schema-typescript

Replaced the hand-rolled jsonSchemaToTsType() string concatenation with a pure Babel AST approach:

• Dependencies: schema-typescript@^0.14.2, @babel/generator@^7.29.0, @babel/types@^7.29.0
• generate-types.ts rewritten (80%): All type construction uses @babel/types AST nodes. Per-node-type parameter interfaces are produced by schema-typescript's generateTypeScriptTypes() which returns t.ExportNamedDeclaration[] directly. Static structural types (BlueprintTable, BlueprintDefinition, etc.) are built with AST helper functions. Final output via @babel/generator's generate().
• Numeric/boolean enums handled upstream: schema-typescript@0.14.2 (dev-utils PR #73) fixes getTypeForProp() to use t.numericLiteral() / t.booleanLiteral() for non-string enum and const values. Generated types now include proper numeric literal unions (e.g. dimension?: 2 | 3 | 4).
• Minimal ensureArrayItems() sanitizer: schema-typescript still throws on array types without an items spec. A small recursive function adds { type: 'string' } as default items for bare arrays — this is the only remaining workaround.
• No string concatenation anywhere in the codegen pipeline.

Review & Testing Checklist for Human

• Verify generated output matches codegen: Run cd graphile/node-type-registry && pnpm generate:types and confirm blueprint-types.generated.ts is unchanged (ensures the committed file isn't stale or manually edited)
• Spot-check static structural types against construct_blueprint(): BlueprintField, BlueprintPolicy, BlueprintTable, BlueprintDefinition are hardcoded in the generator (not derived from schema). Verify field names/types match what the SQL function actually reads — especially BlueprintPolicy.$type, BlueprintTable.grants (unknown[] is very loose), and BlueprintIndex.access_method
• Verify ensureArrayItems() default is safe: The sanitizer adds items: { type: 'string' } for arrays without an items spec. Check whether any node type schemas have array fields that should resolve to something other than string[]
• Verify require('@babel/generator') workaround: The @babel/generator import uses const generate = require(…).default ?? require(…) because @types/babel__generator isn't in dependencies. Confirm this works in both CJS and ESM builds
• Confirm no consumers import NodeTypeRegistryPreset: The preset is deleted — search downstream repos (especially constructive-db) for NodeTypeRegistryPreset or from 'node-type-registry/preset' imports. constructive-db PR refactor(codegen): remove dead maxFieldDepth code and enforce trailing commas #697 removes the only known usage

Notes

• schema-typescript-generated property comments use /* */ style while the hand-written static types use /** */ JSDoc style — minor cosmetic inconsistency in the output
• No automated tests for the codegen script itself — consider adding a snapshot test that runs generate() and compares output
• Companion PRs: constructive-db refactor(codegen): remove dead maxFieldDepth code and enforce trailing commas #697 removes NodeTypeRegistryPreset from the codegen pipeline; agentic-db upgrade all utils packages #41 updates to use the generated types; dev-utils cleaner API #73 (merged) fixes upstream numeric enum handling

Link to Devin session: https://app.devin.ai/sessions/ce1b2dafd42341bea5d7793b0c05ba6c
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 and CI monitoring