Relax private D&D response schemas

docs/integrations/dnd-npc-artifacts.md

@@ -20,6 +20,11 @@ the Unicode-normalized, case-folded canonical name using the identity policy.
 The durable codec enforces the artifact shape and ID syntax; registry identity
 validation remains a separate deterministic concern.
 
+The extractor's private LLM response schema is a separate structural transport
+contract. It omits framework-assigned NPC and source IDs and admits semantic
+candidates for the deterministic shape and source-reference validators; it is
+not part of this durable contract.
+
 ## Output Shape
 
 The payload is one object with a required top-level `npcs` array:

docs/integrations/dnd-spell-artifacts.md

@@ -18,7 +18,9 @@ The durable JSON Schema is owned by the D&D spell artifact codec. The
 extractor's private LLM response schema is a separate transport contract: its
 source-reference objects omit `source_id`, which the extractor assigns while
 mapping the response to the canonical artifact. The LLM DTO and transport
-schema are not part of this durable contract.
+schema are not part of this durable contract. The private schema owns required
+fields, JSON types, object and array shapes, and unknown-field rejection;
+deterministic validators own the durable artifact's semantic constraints.
 
 The output contains canonical spell casts derived from transcript evidence.
 Source IDs are assigned from the input identity; source-unit ranges identify

docs/internal/llm.md

@@ -157,11 +157,11 @@ schemas remain package-owned.
 The spell, NPC, and combat extractors' package-owned prompts declare their
 structured JSON inputs and private response schemas. Each private response
 schema remains separate from its durable artifact codec schema; this work does
-not use shared schema fragments or schema generation. The combat private schema
-owns the transport envelope—required fields, JSON types, nullability, and
-unknown-field rejection—while its deterministic validators own semantic
-constraints such as enum membership, non-empty values and collections, and
-positive numbers. The spell extractor's prompt declares a required
+not use shared schema fragments or schema generation. Those private schemas own
+the transport envelope—required fields, JSON types, nullability, and
+unknown-field rejection—while deterministic validators own semantic constraints
+such as enum membership, non-empty values and collections, and positive
+numbers. The spell extractor's prompt declares a required
 `application/json` `spell_catalog` input and an optional `application/json`
 `npcs` input. The extractor generates
 the catalog input from its prepared

docs/internal/modules.md

@@ -192,6 +192,12 @@ decodes the model response, assigns the generic source identity to every source
 reference, canonicalizes duplicate references, orders spell casts by their
 earliest cited unit, and returns `dnd.SpellList`.
 
+Its private response schema admits only the structural transport envelope:
+required fields, JSON types, array and object shapes, and unknown-field
+rejection. It maps integer source-unit candidates directly without repairing
+semantic values, so the deterministic shape, catalog, and source-reference
+validators own blank values, empty evidence, and invalid or unresolved ranges.
+
 The extractor owns its private model-response DTO, embedded prompt, LLM response
 schema, strict option decoder, injected shared LLM client, and prompt/schema
 manifest metadata. During preparation it resolves the optional `spell_catalog`
@@ -250,6 +256,11 @@ registry slot. Its prompt and private response schema are package-owned. The
 prompt follows the shared D&D extraction ordering and cache policy documented
 in [LLM Runtime](llm.md#dd-extraction-prompt-ordering-and-cache-boundaries).
 
+The private response schema owns only structural transport validation and maps
+integer source-unit candidates unchanged. Required semantic content, non-empty
+evidence, and valid source ranges are rejected by the deterministic shape and
+source-reference validators.
+
 ### `internal/modules/dnd/extract/combatturns`
 
 The combat extractor prepares one structured request per supplied chunk using