From cd9ac22db4433e04eee33b1ff225fc370f29f5a8 Mon Sep 17 00:00:00 2001 From: vegu-ai-tools <152010387+vegu-ai-tools@users.noreply.github.com> Date: Sat, 4 Apr 2026 14:44:07 +0300 Subject: [PATCH] update test baselines --- tests/data/prompts/baselines/narrator/progress_story.txt | 6 ++++++ .../prompts/baselines/narrator/progress_story__default.txt | 6 ++++++ .../prompts/baselines_cached/narrator/progress_story.txt | 6 ++++++ .../baselines_cached/narrator/progress_story__default.txt | 6 ++++++ .../narrator/progress_story.txt | 6 ++++++ .../narrator/progress_story__default.txt | 6 ++++++ .../baselines_noncoercible/narrator/progress_story.txt | 6 ++++++ .../narrator/progress_story__default.txt | 6 ++++++ .../prompts/baselines_reasoning/narrator/progress_story.txt | 6 ++++++ .../narrator/progress_story__default.txt | 6 ++++++ 10 files changed, 60 insertions(+) diff --git a/tests/data/prompts/baselines/narrator/progress_story.txt b/tests/data/prompts/baselines/narrator/progress_story.txt index 62c0ee6e..1fe17583 100644 --- a/tests/data/prompts/baselines/narrator/progress_story.txt +++ b/tests/data/prompts/baselines/narrator/progress_story.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines/narrator/progress_story__default.txt b/tests/data/prompts/baselines/narrator/progress_story__default.txt index 241f963e..5608247d 100644 --- a/tests/data/prompts/baselines/narrator/progress_story__default.txt +++ b/tests/data/prompts/baselines/narrator/progress_story__default.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_cached/narrator/progress_story.txt b/tests/data/prompts/baselines_cached/narrator/progress_story.txt index 62c0ee6e..1fe17583 100644 --- a/tests/data/prompts/baselines_cached/narrator/progress_story.txt +++ b/tests/data/prompts/baselines_cached/narrator/progress_story.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_cached/narrator/progress_story__default.txt b/tests/data/prompts/baselines_cached/narrator/progress_story__default.txt index 241f963e..5608247d 100644 --- a/tests/data/prompts/baselines_cached/narrator/progress_story__default.txt +++ b/tests/data/prompts/baselines_cached/narrator/progress_story__default.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_no_response_length/narrator/progress_story.txt b/tests/data/prompts/baselines_no_response_length/narrator/progress_story.txt index 62c0ee6e..1fe17583 100644 --- a/tests/data/prompts/baselines_no_response_length/narrator/progress_story.txt +++ b/tests/data/prompts/baselines_no_response_length/narrator/progress_story.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_no_response_length/narrator/progress_story__default.txt b/tests/data/prompts/baselines_no_response_length/narrator/progress_story__default.txt index 241f963e..5608247d 100644 --- a/tests/data/prompts/baselines_no_response_length/narrator/progress_story__default.txt +++ b/tests/data/prompts/baselines_no_response_length/narrator/progress_story__default.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_noncoercible/narrator/progress_story.txt b/tests/data/prompts/baselines_noncoercible/narrator/progress_story.txt index 62c0ee6e..1fe17583 100644 --- a/tests/data/prompts/baselines_noncoercible/narrator/progress_story.txt +++ b/tests/data/prompts/baselines_noncoercible/narrator/progress_story.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_noncoercible/narrator/progress_story__default.txt b/tests/data/prompts/baselines_noncoercible/narrator/progress_story__default.txt index 241f963e..5608247d 100644 --- a/tests/data/prompts/baselines_noncoercible/narrator/progress_story__default.txt +++ b/tests/data/prompts/baselines_noncoercible/narrator/progress_story__default.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_reasoning/narrator/progress_story.txt b/tests/data/prompts/baselines_reasoning/narrator/progress_story.txt index 988de524..443ffdfd 100644 --- a/tests/data/prompts/baselines_reasoning/narrator/progress_story.txt +++ b/tests/data/prompts/baselines_reasoning/narrator/progress_story.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ``` diff --git a/tests/data/prompts/baselines_reasoning/narrator/progress_story__default.txt b/tests/data/prompts/baselines_reasoning/narrator/progress_story__default.txt index d78f4d8d..2d733603 100644 --- a/tests/data/prompts/baselines_reasoning/narrator/progress_story__default.txt +++ b/tests/data/prompts/baselines_reasoning/narrator/progress_story__default.txt @@ -21,6 +21,12 @@ Marcus: What brings you to these woods? Move the story forward with a specific, purposeful event or action. Focus on what happens next rather than elaborating on the current state. Use vivid details only to support the progression of the narrative. +Write ONLY as the narrator. Do NOT generate dialogue entries for characters (e.g., no "CHARACTER NAME\n dialogue..." blocks). Your output should be a single continuous narration passage. You may paraphrase or summarize what characters say or do, but never write their direct dialogue lines as if you were them. + +Do NOT re-describe sensory details, atmosphere, or environmental conditions that are already established in the scene history. If the scene has already conveyed that a corridor is warped, the air smells wrong, or the lights are flickering — trust that the reader knows. Reference established details briefly if needed for continuity, but do not re-render them at full length. Spend your words on NEW events, actions, and information. + +Avoid repeating distinctive adjectives and similes that appear in the scene history. If you need to reference an established detail, use plain language rather than inventing a new elaborate description for the same thing. + ``` the current moment in the scene Elena: Hello there, traveler. ```