[Initiative] Dynamic GraphQL Schema Synthesis and Stitching for Custom Kinds

[juliuskrah]

Summary

Add runtime GraphQL schema synthesis and stitching for CRD/custom kinds so the graph can evolve from registry definitions without static codegen-only releases.

Scope

In Scope

• Watch resource definition/registry changes and trigger schema refresh
• Synthesize GraphQL types and root fields from registered kind schemas
• Support namespaced root query conventions for generated kinds
• Stitch extension-provided GraphQL sub-schemas into the main graph with conflict handling
• Add schema-version lifecycle (build, publish, rollback) and cache invalidation hooks
• Add tests for type generation, schema stitching conflicts, and resolver wiring

Out of Scope

• Full extension marketplace workflows
• Replacing existing static schema paths for already-stable core types in phase 1
• Query handler internals (tracked separately)

Acceptance Criteria

• New/updated kind definitions can produce corresponding GraphQL types at runtime
• Generated types are queryable from the main graph without service restart (or with defined bounded reload)
• Extension sub-schemas can be stitched with deterministic conflict resolution
• Schema refresh is observable (version, timestamp, result, failure reason)
• Failure in schema synthesis does not crash the API process; last good schema remains active
• Integration tests cover registry update -> schema refresh -> successful query path

Implementation Notes

Dynamic schema generation is required for CRD-style extensibility. The critical design point is safe schema lifecycle management: build candidate schema, validate, then atomically publish. Stitching should prefer explicit namespace/prefix boundaries to avoid field collisions across extensions.

Dependencies

• Depends on: [Initiative] Universal ScyllaDB Resource Table for CRD-Style Resources #140 (Universal ScyllaDB Resource Table for CRD-Style Resources), [Initiative] Migration Plan for Universal ScyllaDB Resource Table #141 (Migration Plan for Universal ScyllaDB Resource Table)
• Related: [Initiative] WASI Extension Marketplace #35 (WASI Extension Marketplace), [Initiative] Query Handler Chain of Responsibility for Standard and Extension Kinds #148 (Query Handler Chain of Responsibility), [Initiative] CLI-First Platform Management (Admin Optional) #120 (CLI-First Platform Management)

Tracking

• Area: infra
• Priority: p2 – high
• Target Milestone / Release: TBD

[juliuskrah]

Blocked by: #148 (Query Handler Chain must be defined first). Blocks: #150 (Agent workers consume stitched schema).

[juliuskrah]

Follow-up: #162 captures the optional federation gateway path for external app subgraphs. Keep this issue focused on direct runtime schema synthesis and stitching for core kinds; federation should remain a separate edge-composition concern.