Close out the D&D combat turn extraction roadmap

docs/config.md

@@ -423,14 +423,14 @@ accepts no references. To pass an NPC result to a later spell run, bind the
 normalized payload explicitly at runtime; the maintained sequential example
 documents that operator workflow.
 
-The `dnd/combat-turns` extractor and normalizer declare the same optional
-campaign slots and the structured `npcs` slot. The combat extractor uses the
-NPC payload only to ground actor and target identity; the normalizer uses its
-prepared immutable registry for the same canonicalization. Both slots accept
-exactly one UTF-8 `application/json` file no larger than 1 MiB. The registry's
-source ranges remain provenance for the reference and never become combat
-evidence. Binding `npcs` to extraction and normalization is stage-local, so an
-operator-driven combat run uses two explicit selectors:
+The `dnd/combat-turns` extractor declares the optional campaign slots and the
+structured `npcs` slot. Campaign references guide only the LLM extraction
+stage. The deterministic normalizer declares only `npcs`, whose prepared
+immutable registry supports the same actor and target canonicalization. Each
+`npcs` slot accepts exactly one UTF-8 `application/json` file no larger than 1
+MiB. The registry's source ranges remain provenance for the reference and never
+become combat evidence. Binding `npcs` to extraction and normalization is
+stage-local, so an operator-driven combat run uses two explicit selectors:
 
 ```text
 combat.extract.npcs=<npc-run>/lanes/npcs.json