Compose production D&D combat pipeline

docs/operations.md

@@ -70,6 +70,34 @@ campaign data; protect both output roots and any checkpoint or debug roots that
 retain derived application data. A registry from another session is allowed,
 but its source references are never copied into spell output evidence.
 
+## Sequential NPC And Combat Runs
+
+The maintained [sequential NPC and combat configuration](../examples/dnd-npc-combat-sequential.config.yml)
+also represents two independent runs. Run `dnd-npcs` first, then bind its
+normalized `lanes/npcs.json` payload to both combat stages:
+
+```sh
+go run ./cmd/notarius run dnd-npcs \
+  --config examples/dnd-npc-combat-sequential.config.yml \
+  --input examples/seriatim-minimal-transcript.json \
+  --output-dir ./npc-output
+
+go run ./cmd/notarius run dnd-combat \
+  --config examples/dnd-npc-combat-sequential.config.yml \
+  --input examples/seriatim-minimal-transcript.json \
+  --reference combat.extract.npcs=./npc-output/<run-id>/lanes/npcs.json \
+  --reference combat.normalize.npcs=./npc-output/<run-id>/lanes/npcs.json
+```
+
+Extraction and normalization bindings are stage-local and are intentionally
+specified separately. Notarius does not discover the NPC run, copy its source
+ranges into combat evidence, or compose the two runs into one workflow. The
+combat manifest records both reference bindings and the prepared registry's
+semantic digest/count. Changing the referenced NPC payload, prompt or schema,
+normalization policy, or registry digest makes affected checkpoint state
+incompatible; output, checkpoint, and debug roots remain independent sensitive
+state surfaces.
+
 ## Chunk-Plan Cache
 
 Chunk plans are stored at: