Compose production D&D combat pipeline

docs/internal/llm.md

@@ -39,9 +39,9 @@ without exposing Scriptorium types through stage contracts.
 7. injecting that one shared client into complete pipeline preparation before
    the source file is read or the runner is invoked.
 
-The D&D scene chunker and spell and NPC extractors retain this injected client
-and use it for every structured completion. Operation requests do not carry an
-LLM client.
+The D&D scene chunker and spell, NPC, and combat extractors retain this
+injected client and use it for every structured completion. Operation requests
+do not carry an LLM client.
 
 The CLI separately gathers explicit profile IDs from resolved LLM-capable stage
 and validator bindings. It prepares a small internal check prompt for each ID so
@@ -103,18 +103,22 @@ return defensive copies, and expose a diagnostics map that omits schema bytes.
 The small framework registry contains only generic test schemas; production
 schemas remain package-owned.
 
-The spell extractor's package-owned prompt declares a required
+The spell and combat extractors' package-owned prompts declare their structured
+JSON inputs and private response schemas. 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
 effective catalog as `{"spell_names":[...]}` using sorted canonical names only.
 The shared D&D prompt assets include a generic NPC grounding fragment directly
-after the campaign reference message. When an NPC registry is bound, the
+after the campaign reference message for both extractors. When an NPC registry
+is bound, the
 domain registry boundary strictly decodes and identity-validates one durable
 artifact, re-encodes canonical JSON, and generates a semantic digest over
 those bytes. The unbound input is exactly `{"npcs":[]}`. Input digests cover
 the generated bytes; manifests record catalog identity and optional NPC
 registry digest/count rather than names, aliases, overlay bytes, registry
-paths, or source metadata.
+paths, or source metadata. Combat prompt, response-schema, mapping,
+normalization, identity, and bound-registry fingerprints remain separate
+semantic inputs to checkpoint identity.
 
 ## Debug And Redaction Boundaries
 

docs/internal/modules.md

@@ -17,17 +17,17 @@ validator registry. Package-family registrars compose those leaf registrations
 into the production catalog and own family-level policy such as default
 validator chains and prompt asset collection.
 
-Production input, chunk, output, and D&D spell-extract packages register strict
-option decoders and run-local builders. Preparation decodes their options into
+Production input, chunk, output, and D&D spell- and combat-extract packages
+register strict option decoders and run-local builders. Preparation decodes their options into
 implementation-owned values and injects dependencies plus the materialized
 reference set for the selected target. Each builder receives an isolated clone
-of that set; input and output builders receive no references. The spell
-extractor is typed over the canonical D&D model. D&D validators, merge, and
-normalize use typed variants; JSON representation validators use serialized
+of that set; input and output builders receive no references. The spell and
+combat extractors are typed over the canonical D&D model. D&D validators, merge,
+and normalize use typed variants; JSON representation validators use serialized
 requests; and unconditional validators expose separate chunk and typed
-variants. The D&D production registrar registers the canonical typed spell and
-NPC implementations, including their kind-specific merge and normalize
-behavior.
+variants. The D&D production registrar registers the canonical typed spell,
+NPC, and combat implementations, including their kind-specific merge and
+normalize behavior.
 
 Prepared extractors, extract validators, and codecs may be reused concurrently
 by the run-wide extract pool. Production implementations are immutable after
@@ -98,8 +98,8 @@ candidate versus approved encode/decode operations.
 
 The `internal/modules/dnd/codec/combatturns` package owns the durable
 `dnd/combat-turn-list` schema and candidate versus approved JSON boundary. It
-is available as a package contract but is not registered by the production D&D
-family registrar yet.
+is registered by the production D&D family registrar for the selectable combat
+lane.
 
 ## Input Adapter
 
@@ -235,8 +235,8 @@ source-document position while preserving malformed candidate fields for
 deterministic validators. Its prompt and private response schema are
 package-owned, and its prepared metadata and checkpoint fingerprints contain
 only prompt/schema/mapping identities plus an optional NPC registry digest.
-The package exposes typed registration for focused composition but is not in
-the production D&D registrar yet.
+The package exposes typed registration and is included in the production D&D
+registrar with the default combat extraction chain.
 
 ### `internal/modules/dnd/normalize/npcs`
 
@@ -294,8 +294,8 @@ position, and collapses only exact duplicate identities with fully valid
 evidence. It deep-clones output storage and emits bounded warnings scoped to
 merged input indexes. Its metadata and fingerprints identify the normalization
 and NPC identity policies, with registry digest/count only when bound. The
-normalizer is package-complete but is not registered in the production D&D
-registrar.
+normalizer is included in the production D&D registrar with the default combat
+normalization chain.
 
 ## Output Encoder
 
@@ -365,8 +365,8 @@ turn for unrelated actor or declaration text. The normalized-invariants
 validator owns display normalization, comparison-unique targets, canonical
 source-reference order, chronology, and exact duplicate identity; it defers
 shape and source-reference failures. All four validators are deterministic and
-expose local policy fingerprints; they are package-complete but not yet in a
-production validator chain.
+expose local policy fingerprints. The D&D registrar orders them after generic
+JSON and response-schema validation at extraction and normalization.
 
 ## Production Registration
 
@@ -376,8 +376,9 @@ complete framework registry set and one LLM asset registry. It invokes
 `internal/modules/seriatim/register`, and `internal/modules/dnd/register` in
 that order, then exposes the matching catalog for resolution. The generic and
 Seriatim registrars own their production leaf registrations. The D&D registrar
-owns D&D leaf registrations, typed spell and NPC default-validator chains,
-typed append-order specializations, and D&D prompt/schema asset collection.
+owns D&D leaf registrations, typed spell, NPC, and combat default-validator
+chains, typed append-order specializations, and D&D prompt/schema asset
+collection.
 
 Concrete implementation packages do not import generic implementation
 packages directly. A concrete family's `register` package is its composition

docs/internal/overview.md

@@ -65,9 +65,10 @@ run-local construction closures. Preparation injects shared dependencies and
 constructs input, chunk, validators, ordered lanes, and output before source
 parsing. Production modules use strict construction-time option decoding, and
 LLM-backed modules retain the injected shared client. The D&D family registers
-the canonical `dnd/spell-list` and `dnd/npc-list` codecs, typed spell and NPC
-extractors and normalizers, validators, plus kind-specific generic merge
-strategies; generic JSON validators use the serialized-validation contract. The runner executes lanes through
+the canonical `dnd/spell-list`, `dnd/npc-list`, and `dnd/combat-turn-list`
+codecs, typed spell, NPC, and combat extractors and normalizers, validators,
+plus kind-specific generic merge strategies; generic JSON validators use the
+serialized-validation contract. The runner executes lanes through
 private exact-type-checked closures, coordinates extract results independently
 of completion timing, and serializes artifacts only through their codec at
 checkpoint, debug, and output boundaries.
@@ -91,8 +92,8 @@ Configuration. The implemented module packages are:
 | `internal/modules/dnd/extract/spells` | Maps private structured model output to canonical source-grounded D&D spell lists. |
 | `internal/modules/dnd/extract/npcs` | Maps private structured model output to canonical source-grounded D&D NPC lists. |
 | `internal/modules/dnd/extract/combatturns` | Maps private structured model output to source-grounded D&D combat-turn candidates and preserves chronology and invalid candidate values for validators. |
-| `internal/modules/dnd/normalize/combatturns` | Canonicalizes and orders merged combat turns, applies exact NPC identity matches, and collapses only exact valid-evidence duplicates without production composition. |
-| `internal/modules/dnd/validate/combatturns` | Provides deterministic shape, source-reference, source-relatedness, and normalized-invariant validation for combat turns without production composition. |
+| `internal/modules/dnd/normalize/combatturns` | Canonicalizes and orders merged combat turns, applies exact NPC identity matches, and collapses only exact valid-evidence duplicates. |
+| `internal/modules/dnd/validate/combatturns` | Provides deterministic shape, source-reference, source-relatedness, and normalized-invariant validation for the production combat chains. |
 | `internal/modules/dnd/npcs/registry` | Resolves validated normalized NPC references into immutable grounding data and exact identity lookup. |
 | `internal/modules/dnd/npcs/identity` | Owns Unicode-aware NPC identity, ID derivation, and registry collision validation. |
 | `internal/modules/dnd/spells/catalog` | Embeds and validates the versioned D&D 5e 2014 SRD catalog, composes optional overlays, and provides immutable effective lookup. |