Compose production D&D combat pipeline

docs/integrations/dnd-combat-turn-artifacts.md

@@ -1,9 +1,8 @@
 # D&D Combat-Turn Artifact Contract
 
 This document defines the durable artifact, serialization, extraction,
-candidate-validation, and standalone normalization boundaries for D&D combat
-turns. Production composition and a selectable pipeline lane are not part of
-this contract yet.
+candidate-validation, normalization, and production lane boundaries for D&D
+combat turns.
 
 ## Artifact identity
 
@@ -119,8 +118,9 @@ the shared Unicode-aware NPC identity policy, and checks declaration tokens of
 at least four Unicode code points against complete cited-text tokens. Targets
 are not checked deterministically.
 
-The extractor and validators are package-complete but are not registered by the
-production D&D family registrar yet.
+The production D&D registrar exposes the extractor and these validators. Its
+default extraction chain preserves this order: JSON syntax, private response
+schema, combat shape, source references, then source relatedness.
 
 ## Normalization boundary
 
@@ -149,5 +149,19 @@ canonical evidence ordering, chronology, and duplicate identity. It rejects
 with `invalid_combat_turn_normalization` under policy
 `dnd.combat_turns.validator.normalized.v1`.
 
-The normalizer and normalized-invariants validator are package-complete but are
-not registered by the production D&D family registrar yet.
+The production D&D registrar exposes the normalizer and normalized-invariants
+validator. Its default normalization chain is JSON syntax, durable schema,
+combat shape, normalized invariants, source references, then source
+relatedness. The lane uses the framework's typed append-order merger and has no
+merge validator chain.
+
+## Production manifest and references
+
+The selectable lane uses extractor and normalizer key `dnd/combat-turns`,
+`appendorder` for the typed merger, and the durable codec above. A bound `npcs`
+reference contributes raw-file provenance to the run manifest. Prepared combat
+extractor and normalizer metadata and checkpoint fingerprints contain only the
+NPC registry's semantic digest and count; the registry content, path, and NPC
+source ranges are not copied into combat output. The normalized lane is emitted
+as `lanes/<lane-id>.json` by the JSON output module, and warnings and rejection
+summaries remain in their shared companion files.

docs/integrations/dnd-npc-artifacts.md

@@ -2,8 +2,9 @@
 
 This document defines the durable D&D NPC-list artifact, its JSON codec, and
 the selectable production NPC pipeline. The normalized JSON payload can be
-passed explicitly to the spell extractor as an optional caster-name registry;
-it remains a reference, not spell evidence.
+passed explicitly to the spell extractor as an optional caster-name registry
+or to the combat extractor and normalizer as an actor/target registry. It
+remains a reference, not spell or combat evidence.
 
 ## Identity
 

docs/integrations/json-output.md

@@ -151,8 +151,9 @@ accepts only artifacts whose codec media type is `application/json`. The file
 contains the codec-owned JSON bytes pretty-printed.
 
 The schema of each lane payload is owned by that artifact contract. For the
-current D&D lanes, see [D&D Spell Artifact](dnd-spell-artifacts.md) and
-[D&D NPC Artifact](dnd-npc-artifacts.md).
+current D&D lanes, see [D&D Spell Artifact](dnd-spell-artifacts.md),
+[D&D NPC Artifact](dnd-npc-artifacts.md), and
+[D&D Combat-Turn Artifact](dnd-combat-turn-artifacts.md).
 
 ## `rejected.json`