Add NPC registry grounding for spell extraction

docs/operations.md

@@ -40,6 +40,36 @@ names, schemas, and media types inside a run directory.
 Remove an output run directory only after its consumer data is no longer
 needed. This is data deletion, not cache cleanup.
 
+## Sequential NPC And Spell Runs
+
+The maintained [sequential configuration](../examples/dnd-npc-spell-sequential.config.yml)
+contains two independent pipelines over the same Seriatim input shape. Run the
+NPC pipeline first and retain its normalized payload:
+
+```sh
+go run ./cmd/notarius run dnd-npcs \
+  --config examples/dnd-npc-spell-sequential.config.yml \
+  --input examples/seriatim-minimal-transcript.json \
+  --output-dir ./npc-output
+```
+
+Then bind that completed run's `lanes/npcs.json` file to the spell extractor:
+
+```sh
+go run ./cmd/notarius run dnd-spells \
+  --config examples/dnd-npc-spell-sequential.config.yml \
+  --input examples/seriatim-minimal-transcript.json \
+  --reference spells.extract.npcs=./npc-output/<run-id>/lanes/npcs.json
+```
+
+The NPC file is a reference for canonical caster names and aliases, not spell
+evidence. The spell manifest records the bound file's raw reference provenance
+and the prepared registry's count and semantic digest separately. The NPC
+payload, names, aliases, source references, and file bytes can be sensitive
+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.
+
 ## Chunk-Plan Cache
 
 Chunk plans are stored at: