Document scene-aware combat extraction

docs/operations.md

@@ -53,7 +53,8 @@ contains one pipeline with two ordered steps. The first step extracts and
 normalizes NPCs and scene descriptions. Only after those lanes reach accepted
 terminal results does the second step begin; its generated NPC reference is
 supplied in memory to spell, combat-turn, and NPC-interaction extraction and
-the applicable normalizers.
+the applicable normalizers, while its generated scene-description reference is
+supplied to combat-turn extraction.
 
 ```sh
 go run ./cmd/notarius run dnd-session \
@@ -70,6 +71,14 @@ exposed through a filesystem path. The same producer artifact may fan out to
 compatible consumers, while a missing or rejected producer prevents the later
 step from starting.
 
+Combat-turn extraction calls its LLM only when a scene record exactly matches
+the accepted chunk and has kind `combat`. Exact `narrative`, `recap`, and
+`meta` records produce an accepted empty combat-turn result without an LLM call.
+Missing or mismatched scene coverage also produces an accepted empty result and
+a bounded warning. Scene descriptions remain control context rather than combat
+evidence or prompt material; the complete behavior is defined by the
+[D&D combat-turn artifact contract](integrations/dnd-combat-turn-artifacts.md).
+
 Standalone module configurations continue to support external NPC files when a
 workflow intentionally crosses a process or session boundary. Those files are
 validated against the consumer slot and must be protected as sensitive