Compose production D&D combat pipeline

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