Consolidate grounded event extraction instructions

assets/dnd/enemy-events/prompts/instructions.md

@@ -1,14 +1,25 @@
+Extract Dungeons & Dragons enemy events from the supplied combat transcript.
+An `engaged` event requires direct establishment that a subject is actively
+opposing the party in combat. A `killed`, `fled`, `captured`, or
+`incapacitated` event requires explicit establishment of that outcome. An
+outcome may share evidence with an engagement, and a later engagement or
+outcome for the same subject remains a separate observation. Emit at most one
+`engaged` observation for the same subject in this combat scene.
+
+For `killed`, direct death or killing is required. For `fled`, the subject
+must explicitly escape, retreat, or leave combat to avoid continued engagement.
+For `captured`, the subject must be explicitly taken prisoner or secured
+under the party's control. For `incapacitated`, the subject must be explicitly
+unable to continue acting without being established as killed or captured.
+
+When the transcript identifies a named NPC, use its normalized registry
+spelling. A hostile creature without a registry entry is allowed. For unnamed
+individuals or groups, use only the narrowest transcript-grounded label, such
+as `Orcs`, `One orc`, or `Remaining orcs`; never invent member names, IDs,
+or quantities.
+
 Exclude party members, allies, neutral observers, mentioned-but-absent enemies,
 hazards, traps, environmental effects, uncertain allegiance, table talk,
 planning, hypotheses, recaps outside this passage, and downstream inference.
-
 Do not infer an engagement or outcome from initiative, turn absence, damage,
-defeat, movement, a scene ending, combat-opponent grounding, or any auxiliary
-artifact. Auxiliary inputs can guide attention but cannot prove or supply an
-event. Cite only narrow current-transcript ranges that establish each event.
-
-Return the `events` array even when no enemy event is established. Every event
-must contain only `name`, `kind`, and `source_refs`. Use exactly one kind:
-`engaged`, `killed`, `fled`, `captured`, or `incapacitated`. Each source range
-uses integer `start_unit_id` and `end_unit_id`; omit `source_id` because
-Notarius assigns the current source identity.
+defeat, movement, or a scene ending.

assets/dnd/enemy-events/prompts/prompt.yaml

@@ -42,8 +42,6 @@ messages:
     content_file: ./sharedassets/common-dnd-npcs.md
   - role: user
     content_file: ./combat-grounding.md
-  - role: user
-    content_file: ./task.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/enemy-events/prompts/task.md

@@ -1,20 +0,0 @@
-Extract Dungeons & Dragons enemy events from the supplied combat transcript.
-
-Return an `engaged` event only when the transcript directly establishes that a
-subject is actively opposing the party in combat. Return `killed`, `fled`,
-`captured`, or `incapacitated` only when the transcript explicitly establishes
-that outcome. An outcome may share evidence with an engagement, and a later
-engagement or outcome for the same subject remains a separate observation.
-Emit at most one engagement for the same subject in this combat scene.
-
-For `killed`, direct death or killing is required. For `fled`, the subject must
-explicitly escape, retreat, or leave combat to avoid continued engagement. For
-`captured`, the subject must be explicitly taken prisoner or secured under the
-party's control. For `incapacitated`, the subject must be explicitly unable to
-continue acting without being established as killed or captured.
-
-Use a normalized NPC registry spelling when the transcript identifies that
-named NPC. A hostile creature without a registry entry is allowed. For unnamed
-individuals or groups, use only the narrowest transcript-grounded label, such
-as `Orcs`, `One orc`, or `Remaining orcs`; never invent member names, IDs, or
-quantities.