Sprint 56h: fix package step - use source_step+{steps[1].text} to pass chapter text to reviewers; remove chapter_text schema; trim meta on rewind

This commit is contained in:
David Baity
2026-03-25 02:11:26 -04:00
parent ca0e2fad89
commit c08ace762c

View File

@@ -319,31 +319,27 @@ steps:
filename: "character-state-{chapter_ref}" filename: "character-state-{chapter_ref}"
- type: package - type: package
max_tokens: 12000 source_step: 4 # PASS 3 — character-state extraction (compact, describes permanent changes)
max_tokens: 4000
hint: | hint: |
The draft chapter has been written, self-checked, and committed. The draft chapter has been written, self-checked, and committed.
The character-state from PASS 3 is provided above.
CRITICAL — include the `chapter_text` field: Summarize the character state changes for {chapter_ref} in the `chapter_state` field
Copy the COMPLETE chapter text from the self-check output (step 2 — the final chapter draft) (2-3 sentences max). This is used for bookkeeping — the chapter text itself is passed
into the `chapter_text` field. to reviewers directly.
Reviewers have NO other way to access the chapter content.
Do NOT summarize or truncate it — include every word of the chapter.
NEW CHARACTER DETECTION (Bug G fix): NEW CHARACTER DETECTION:
Look at the Character State from PASS 3 above (step 4). For each character listed there For each NEW character introduced this chapter (not previously known), emit one
whose name slug does NOT already have a "character-{slug}" file in PROJECT DELIVERABLES, create_task action using task_type: character_sheet.
emit one additional create_task action per new character using task_type: character_sheet.
This ensures new characters introduced in this chapter get proper character sheets.
PERMANENT CHANGE DETECTION (butterfly effect): PERMANENT CHANGE DETECTION (butterfly effect):
For any character in the Character State whose "Permanent:" field is YES, For any character with "Permanent: YES" in the state, emit a create_task action
emit one additional create_task action using task_type: character_update. using task_type: character_update to record the change in the character sheet.
This triggers the character update pipeline to record deaths, power changes, etc.
Now spawn the three independent editorial reviewers Now confirm the chapter is ready for review.
and the roundtable debate. Use the exact task_names shown — the roundtable depends_on all three.
schema: schema:
chapter_text: string chapter_state: string
spawn: spawn:
- task_type: chapter_review - task_type: chapter_review
task_name: "Review (Devon): {chapter_ref}" task_name: "Review (Devon): {chapter_ref}"
@@ -351,7 +347,7 @@ steps:
priority: 6 priority: 6
_if: "not meta.is_locked" _if: "not meta.is_locked"
context: context:
chapter_text: "{chapter_text}" chapter_text: "{steps[1].text}"
review_focus: developmental review_focus: developmental
genre_name: "{genre_name}" genre_name: "{genre_name}"
genre_audience: "{genre_audience}" genre_audience: "{genre_audience}"
@@ -366,7 +362,7 @@ steps:
priority: 6 priority: 6
_if: "not meta.is_locked" _if: "not meta.is_locked"
context: context:
chapter_text: "{chapter_text}" chapter_text: "{steps[1].text}"
review_focus: line review_focus: line
genre_name: "{genre_name}" genre_name: "{genre_name}"
genre_audience: "{genre_audience}" genre_audience: "{genre_audience}"
@@ -381,7 +377,7 @@ steps:
priority: 6 priority: 6
_if: "not meta.is_locked" _if: "not meta.is_locked"
context: context:
chapter_text: "{chapter_text}" chapter_text: "{steps[1].text}"
review_focus: continuity review_focus: continuity
genre_name: "{genre_name}" genre_name: "{genre_name}"
genre_audience: "{genre_audience}" genre_audience: "{genre_audience}"
@@ -399,7 +395,7 @@ steps:
priority: 7 priority: 7
_if: "not meta.is_locked" _if: "not meta.is_locked"
context: context:
chapter_text: "{chapter_text}" chapter_text: "{steps[1].text}"
genre_name: "{genre_name}" genre_name: "{genre_name}"
genre_audience: "{genre_audience}" genre_audience: "{genre_audience}"
chapter_ref: "{chapter_ref}" chapter_ref: "{chapter_ref}"