From c08ace762ca01d9e346553913c9917c8b0d24309 Mon Sep 17 00:00:00 2001 From: David Baity <158404677+MazakTheDwarf@users.noreply.github.com> Date: Wed, 25 Mar 2026 02:11:26 -0400 Subject: [PATCH] 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 --- templates/book_chapter.yml | 38 +++++++++++++++++--------------------- 1 file changed, 17 insertions(+), 21 deletions(-) diff --git a/templates/book_chapter.yml b/templates/book_chapter.yml index 4067d32..7c69a5e 100644 --- a/templates/book_chapter.yml +++ b/templates/book_chapter.yml @@ -319,31 +319,27 @@ steps: filename: "character-state-{chapter_ref}" - type: package - max_tokens: 12000 + source_step: 4 # PASS 3 — character-state extraction (compact, describes permanent changes) + max_tokens: 4000 hint: | 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: - Copy the COMPLETE chapter text from the self-check output (step 2 — the final chapter draft) - into the `chapter_text` field. - Reviewers have NO other way to access the chapter content. - Do NOT summarize or truncate it — include every word of the chapter. + Summarize the character state changes for {chapter_ref} in the `chapter_state` field + (2-3 sentences max). This is used for bookkeeping — the chapter text itself is passed + to reviewers directly. - NEW CHARACTER DETECTION (Bug G fix): - Look at the Character State from PASS 3 above (step 4). For each character listed there - whose name slug does NOT already have a "character-{slug}" file in PROJECT DELIVERABLES, - 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. + NEW CHARACTER DETECTION: + For each NEW character introduced this chapter (not previously known), emit one + create_task action using task_type: character_sheet. PERMANENT CHANGE DETECTION (butterfly effect): - For any character in the Character State whose "Permanent:" field is YES, - emit one additional create_task action using task_type: character_update. - This triggers the character update pipeline to record deaths, power changes, etc. + For any character with "Permanent: YES" in the state, emit a create_task action + using task_type: character_update to record the change in the character sheet. - Now spawn the three independent editorial reviewers - and the roundtable debate. Use the exact task_names shown — the roundtable depends_on all three. + Now confirm the chapter is ready for review. schema: - chapter_text: string + chapter_state: string spawn: - task_type: chapter_review task_name: "Review (Devon): {chapter_ref}" @@ -351,7 +347,7 @@ steps: priority: 6 _if: "not meta.is_locked" context: - chapter_text: "{chapter_text}" + chapter_text: "{steps[1].text}" review_focus: developmental genre_name: "{genre_name}" genre_audience: "{genre_audience}" @@ -366,7 +362,7 @@ steps: priority: 6 _if: "not meta.is_locked" context: - chapter_text: "{chapter_text}" + chapter_text: "{steps[1].text}" review_focus: line genre_name: "{genre_name}" genre_audience: "{genre_audience}" @@ -381,7 +377,7 @@ steps: priority: 6 _if: "not meta.is_locked" context: - chapter_text: "{chapter_text}" + chapter_text: "{steps[1].text}" review_focus: continuity genre_name: "{genre_name}" genre_audience: "{genre_audience}" @@ -399,7 +395,7 @@ steps: priority: 7 _if: "not meta.is_locked" context: - chapter_text: "{chapter_text}" + chapter_text: "{steps[1].text}" genre_name: "{genre_name}" genre_audience: "{genre_audience}" chapter_ref: "{chapter_ref}"