Spec conformance: Section 3 — Type System

[craigsmitham]

Scope

Section 3 — Type System. Covers schema definition, type kinds (scalars, objects, interfaces, unions, enums, input objects), wrapping types (list, non-null), and directive definitions. Subsections TBD during design.

Context

This is part of the phased spec conformance effort started in #57. Phase 1 (Section 5 — Validation) is complete and established conventions documented in test/GraphZen.SpecConformance.Tests/CLAUDE.md. Phase 1 patterns were designed around validation rules — this section covers type system construction rules and constraints, which will likely need different infrastructure.

Stage 1 — Design

• Read spec Section 3, extract all subsections and normative statements
• Review graphql-js test coverage for type system (~/Code/graphql/graphql-js/src/type/)
• Determine test infrastructure needs (can we reuse SpecValidation? do we need a schema construction harness?)
• Determine class/folder structure and naming
• Determine how implementation gaps should be expressed
• Update test/GraphZen.SpecConformance.Tests/CLAUDE.md with patterns and infrastructure decisions for this section
• Update this issue with the design below

Subsections

To be filled in during design.

Infrastructure

To be filled in during design.

Open Questions

To be filled in during design.

Stage 2 — Implementation

• Add manifest entries
• Create conformance classes
• PR