novelforge-agent 0.2.0 → 0.4.0

package/README.md

@@ -57,6 +57,7 @@ The installer is **idempotent and safe**: it never overwrites an existing entry
 |-------|------|---------------------|----------------------|
 | Setup | `novel_metadata` | Output JSON: title, genre, premise, cast | `novel.json` |
 |  | `story_bible` | Output Markdown: characters, world rules, plot threads | `story-bible.md` |
+|  | `style_guide` | Output JSON: narrative voice, pacing, diction, dialogue rules, prohibited patterns, prose rhythm, sample prose | `style-guide.json` |
 |  | `architecture` | Output JSON: full / volume / pacing / chapter outlines | `architecture/{full.md, volumes.json, volume-pacing.json, chapters.json}` |
 | Loop  | `chapter` | Write chapter N Markdown | `chapters/NNN.md` |
 |  | `chapter_review` | Enforce the chapter acceptance gate: required beats, plot/character/thread progress, story-bible consistency, ending hook, repetition check | `reviews/chapter/chapter-NNN.json` |
@@ -67,7 +68,7 @@ The installer is **idempotent and safe**: it never overwrites an existing entry
 |  | `chapter_revision` | Rewrite a chapter; previous version auto-archived | `chapters/.versions/NNN.<ts>.md` |
 |  | `cross_chapter_review` | Cross-chapter continuity audit | `reviews/cross/cross-S-E.json` |
 
-Each chapter / bible / memory write also feeds a per-project BM25 index (`.index/`) so the agent can hand the host semantically relevant snippets when later chapters are generated, or answer ad-hoc `retrieve` queries from the host. Chapter generation context also includes the independent character state table (`characters.json`) and current volume pacing board (`architecture/volume-pacing.json`) when available.
+Each chapter / bible / memory write also feeds a per-project BM25 index (`.index/`) so the agent can hand the host semantically relevant snippets when later chapters are generated, or answer ad-hoc `retrieve` queries from the host. Chapter generation context also includes the style guide (`style-guide.json`), independent character state table (`characters.json`), and current volume pacing board (`architecture/volume-pacing.json`) when available. The style guide includes `proseRhythm`, which checks rhythm anti-patterns such as excessive short-sentence density, consecutive one-sentence paragraphs, fake rhythm through line breaks, overly direct interior explanation, and repeated sentence patterns.
 
 ## Install
 
@@ -170,7 +171,7 @@ NOVELFORGE_WORKSPACE = "/absolute/path/where/projects/should/live"
 ## Tool reference
 
 ### Project lifecycle
-- **`start_novel_project`** `(prompt, language?, outputDir?, targetChapters?)` — create a new project under `<workspaceRoot>/<outputDir>/<slug>-<rand6>/` and return the first step's instruction.
+- **`start_novel_project`** `(prompt, language?, outputDir?, targetChapters?, plannedTotalChapters?)` — create a new project under `<workspaceRoot>/<outputDir>/<prompt-slug>-<rand6>/` and return the first step's instruction. After `novel_metadata` is accepted, the directory is renamed to `<title-slug>-<same-rand6>/`; callers must continue with the returned `state.projectPath`. `targetChapters` is the per-batch planning size; MCP defaults to 5. `plannedTotalChapters` is the whole-book target; MCP defaults to 12.
 - **`list_projects`** `(outputDir?)` — list all projects in the workspace, newest first.
 - **`get_project_status`** `(projectPath)` — compact summary: current step, chapters written, open threads, latest review verdict.
 - **`get_next_step`** `(projectPath)` — return the prompt + packed context for whatever the workflow expects next.
@@ -179,13 +180,15 @@ NOVELFORGE_WORKSPACE = "/absolute/path/where/projects/should/live"
 - **`submit_step_result`** `(projectPath, step, content)` — validate `content` against the step's zod schema, persist it, advance the state machine. On failure the bad submission is written to `.agent-recovery/failed-*.txt` and the state does not advance.
 - **`get_context`** `(projectPath, purpose, chapterNumber?, start?, end?)` — build purpose-specific context without changing state. Useful when the host wants to read what the agent *would* have packed.
 
+Dynamic planning is built into the state machine: after each accepted chapter and memory card, the agent checks `plannedTotalChapters` and the highest chapter covered by `architecture/chapters.json`. If the next chapter is still inside the whole-book target but not yet planned, the next step becomes `architecture_extension`; after the host submits that JSON, generation resumes at `chapter`.
+
 ### Semantic actions (verb-style; safe to call any time)
 - **`generate_chapter`** `(projectPath, chapterNumber)` — return generation context for a specific chapter.
 - **`extract_memory_card`** `(projectPath, chapterNumber)` — return memory-extraction context for a specific chapter.
 - **`review_chapter`** `(projectPath, chapterNumber)` — switch into a single-chapter editorial review side-track and return its prompt. After `submit_step_result(step="chapter_review")`, the workflow resumes its prior step automatically.
 - **`revise_chapter`** `(projectPath, chapterNumber, feedback?)` — switch into a chapter-revision side-track. Submitting `chapter_revision` content auto-archives the previous version under `chapters/.versions/`.
 - **`cross_chapter_review`** `(projectPath, start?, end?)` — switch into a cross-chapter audit side-track over the given range (defaults to all generated chapters).
-- **`save_chapter`** `(projectPath, chapterNumber, title, content)` — write a chapter Markdown file directly, without going through the state machine.
+- **`save_chapter`** `(projectPath, chapterNumber, title, content)` — submit the current chapter through the state machine; it requires `currentStep="chapter"` and then advances to mandatory `chapter_review`.
 
 ### Project operations
 - **`amend_story_bible`** `(projectPath, content, reason?)` — replace `story-bible.md`, archive the previous version, and rebuild the bible index.
@@ -204,11 +207,12 @@ NOVELFORGE_WORKSPACE = "/absolute/path/where/projects/should/live"
 A project on disk:
 
 ```
-novels/<slug>-<rand6>/
+novels/<title-slug>-<rand6>/
 ├── agent-state.json              # workflow state (currentStep, currentChapter, files map, …)
 ├── novel.json                    # metadata (NovelMetadataSchema)
 ├── characters.json               # independent character state table
 ├── story-bible.md
+├── style-guide.json              # enforceable prose style guide
 ├── architecture/
 │   ├── full.md
 │   ├── volumes.json
@@ -237,15 +241,15 @@ The whole directory is self-contained — copy it, share it, delete it.
 ## How the workflow advances
 
 ```
-novel_metadata → story_bible → architecture → chapter
-                                              ↓
-                                         chapter_review
-                                              ↓
-                                   ┌──────────┴──────────┐
-                                 clean             issues_found
-                                   ↓                    ↓
-                              memory_card       chapter_revision
-                                   ↓                    ↓
+novel_metadata → story_bible → style_guide → architecture → chapter
+                                                            ↓
+                                                       chapter_review
+                                                            ↓
+                                                 ┌──────────┴──────────┐
+                                               clean             issues_found
+                                                 ↓                    ↓
+                                            memory_card       chapter_revision
+                                                 ↓                    ↓
                      ┌─────────────┴─────────────┐      │
              (more chapters)                (all done)   │
                      ↓                            ↓       │

package/dist/src/cli/index.js

@@ -38,9 +38,17 @@ export async function runCli(argv = process.argv.slice(2), cwd = process.cwd())
         if (!prompt.trim())
             throw new Error('Missing --prompt');
         const language = parseLanguage(valueAfter(argv, '--language') || 'zh-CN');
-        const chapters = Number(valueAfter(argv, '--chapters') || 3);
+        const chapters = Number(valueAfter(argv, '--chapters') || 5);
+        const totalChapters = Number(valueAfter(argv, '--total-chapters') || 12);
         const outputDir = valueAfter(argv, '--output') || 'novels';
-        const result = await createProject({ workspaceRoot: cwd, prompt, language, outputDir, targetChapters: chapters });
+        const result = await createProject({
+            workspaceRoot: cwd,
+            prompt,
+            language,
+            outputDir,
+            targetChapters: chapters,
+            plannedTotalChapters: totalChapters,
+        });
         const next = await getNextStep(result.state.projectPath);
         console.log(JSON.stringify({ state: result.state, next }, null, 2));
         return;

package/dist/src/core/contextBuilder.js

@@ -15,6 +15,7 @@ export async function buildContext(input) {
     const parts = [];
     const metadata = await readOptional(join(input.projectPath, 'novel.json'));
     const storyBible = await readOptional(join(input.projectPath, 'story-bible.md'));
+    const styleGuideJson = await readOptional(join(input.projectPath, 'style-guide.json'));
     const chaptersJson = await readOptional(join(input.projectPath, 'architecture/chapters.json'));
     const charactersJson = await readOptional(join(input.projectPath, 'characters.json'));
     const volumePacingJson = await readOptional(join(input.projectPath, 'architecture/volume-pacing.json'));
@@ -22,6 +23,8 @@ export async function buildContext(input) {
         parts.push(`## Novel Metadata\n${metadata}`);
     if (storyBible)
         parts.push(`## Story Bible\n${storyBible.slice(0, 4000)}`);
+    if (styleGuideJson)
+        parts.push(`## Style Guide\n${styleGuideJson}`);
     if (charactersJson)
         parts.push(`## Character State Table\n${charactersJson}`);
     function addVolumePacing(volumeId) {
@@ -104,6 +107,35 @@ export async function buildContext(input) {
         if (memoryParts.length)
             parts.push(`## Memory Cards\n${memoryParts.join('\n')}`);
     }
+    if (input.purpose === 'architecture_extension') {
+        if (chaptersJson)
+            parts.push(`## Existing Chapter Architecture List\n${chaptersJson}`);
+        if (volumePacingJson)
+            parts.push(`## Existing Volume Pacing Boards\n${volumePacingJson}`);
+        const start = Math.max(1, (input.chapterNumber ?? 1) - 5);
+        const end = Math.max(0, (input.chapterNumber ?? 1) - 1);
+        const memoryParts = [];
+        for (let i = start; i <= end; i += 1) {
+            const memory = await readOptional(join(input.projectPath, 'memory', memoryFileName(i)));
+            if (memory)
+                memoryParts.push(`### Chapter ${i} Memory\n${memory}`);
+        }
+        if (memoryParts.length)
+            parts.push(`## Recent Memory Cards\n${memoryParts.join('\n')}`);
+        const allThreads = await loadThreads(input.projectPath);
+        const active = activeThreads(allThreads);
+        if (active.length) {
+            const lines = active.map((t) => {
+                const flags = [`#${t.id}`, `status=${t.status}`, `planted=ch${t.plantedAt}`];
+                if (t.plannedPayoffAt)
+                    flags.push(`payoff=ch${t.plannedPayoffAt}`);
+                if (t.lastTouchedAt !== t.plantedAt)
+                    flags.push(`touched=ch${t.lastTouchedAt}`);
+                return `- ${t.description}  (${flags.join(', ')})`;
+            });
+            parts.push(`## Active Foreshadow Threads\n${lines.join('\n')}`);
+        }
+    }
     if (input.purpose === 'chapter_review' && input.chapterNumber) {
         if (chaptersJson) {
             const chapters = JSON.parse(chaptersJson);

package/dist/src/core/fileNames.js

@@ -8,12 +8,12 @@ export function makeProjectSlug(title) {
     const replaced = title
         .trim()
         .split('')
-        .map((char) => PINYIN_FALLBACK[char] || char)
-        .join('-')
+        .map((char) => PINYIN_FALLBACK[char] ? `-${PINYIN_FALLBACK[char]}-` : char)
+        .join('')
         .normalize('NFKD')
         .replace(/[\u0300-\u036f]/g, '')
         .toLowerCase()
-        .replace(/[^a-z0-9]+/g, '-')
+        .replace(/[^\p{Letter}\p{Number}]+/gu, '-')
         .replace(/^-+|-+$/g, '');
     return replaced || `novel-${Date.now()}`;
 }

package/dist/src/core/projectDiscovery.js

@@ -36,6 +36,7 @@ async function summarizeOne(projectPath) {
         currentStep: state.currentStep,
         currentChapter: state.currentChapter,
         targetChapters: state.targetChapters,
+        plannedTotalChapters: state.plannedTotalChapters ?? state.targetChapters,
         completedSteps: state.completedSteps.length,
         chaptersWritten: countChapters(state),
         updatedAt: state.updatedAt,

package/dist/src/core/projectOps.js

@@ -107,12 +107,14 @@ export async function deleteChapter(input) {
 const STEP_FILE_KEYS = {
     novel_metadata: ['novel'],
     story_bible: ['storyBible'],
+    style_guide: ['styleGuide'],
     architecture: ['architecture'],
     continuity_review: ['continuityReview'],
 };
 const STEP_FILE_PATHS = {
     novel_metadata: ['novel.json'],
     story_bible: ['story-bible.md'],
+    style_guide: ['style-guide.json'],
     architecture: ['architecture/full.md', 'architecture/volumes.json', 'architecture/chapters.json'],
 };
 export async function redoStep(input) {
@@ -143,7 +145,11 @@ export async function redoStep(input) {
         state.currentStep = input.step;
         state.pendingAction = undefined;
     }
-    else if (input.step === 'novel_metadata' || input.step === 'story_bible' || input.step === 'architecture' || input.step === 'continuity_review') {
+    else if (input.step === 'novel_metadata'
+        || input.step === 'story_bible'
+        || input.step === 'style_guide'
+        || input.step === 'architecture'
+        || input.step === 'continuity_review') {
         const paths = STEP_FILE_PATHS[input.step] ?? [];
         for (const p of paths) {
             if (await tryUnlink(join(state.projectPath, p)))

package/dist/src/core/projectStore.js

@@ -45,7 +45,9 @@ export async function archiveStoryBible(projectPath, versionRelative) {
 export async function createProject(input) {
     const workspaceRoot = resolve(input.workspaceRoot);
     const baseDir = input.outputDir || 'novels';
-    const targetChapters = Math.max(1, Math.floor(Number(input.targetChapters || 3)));
+    const hasExplicitTargetChapters = input.targetChapters !== undefined;
+    const targetChapters = Math.max(1, Math.floor(Number(input.targetChapters || 5)));
+    const plannedTotalChapters = Math.max(targetChapters, Math.floor(Number(input.plannedTotalChapters ?? (hasExplicitTargetChapters ? targetChapters : 12))));
     const baseSlug = makeProjectSlug(input.prompt.slice(0, 48));
     const suffix = randomBytes(3).toString('hex');
     const slug = `${baseSlug}-${suffix}`;
@@ -59,6 +61,7 @@ export async function createProject(input) {
         initialPrompt: input.prompt,
         language: input.language || 'zh-CN',
         targetChapters,
+        plannedTotalChapters,
         currentStep: 'novel_metadata',
         currentChapter: 1,
         completedSteps: [],

package/dist/src/core/prompts/en-US.js

@@ -74,6 +74,55 @@ Rules:
 - Do not output JSON.`,
     };
 }
+function buildStyleGuidePrompt(input) {
+    return {
+        purpose: 'style_guide',
+        expectedFormat: 'JSON matching StyleGuideSchema',
+        prompt: `You are the style editor for a long-form novel. From the user prompt, metadata, and story bible, create a style guide that chapter writing and review can enforce over the whole project.
+
+## User Prompt
+${input.state.initialPrompt}
+
+${input.context ? `## Existing Context\n${input.context}\n` : ''}## Output Requirements
+Output valid JSON only, in this shape:
+{
+  "narrativeVoice": "Narration person, POV distance, narrator texture, emotional temperature",
+  "pacing": "Rules for openings, transitions, conflict movement, and chapter-end hooks",
+  "diction": "Word choice, sentence density, genre terminology boundaries",
+  "dialogueRules": [
+    "Rules for core character dialogue length, tone, subtext, and forms of address"
+  ],
+  "prohibitedPatterns": [
+    "Patterns to avoid: modern memes, explanatory narration, lore dumping, voice drift, etc."
+  ],
+  "proseRhythm": {
+    "sentenceRhythm": "How short, medium, and long sentences should be used; short sentences should serve turns, danger, or emotional landings, not default narration",
+    "paragraphing": "Paragraphs should form complete narrative units; avoid consecutive one-sentence paragraphs and line breaks used as fake rhythm",
+    "interiorityMode": "How interiority should be refracted through action, hesitation, and sensory response; avoid frequent direct explanation of thoughts",
+    "emphasisBudget": "Budget for repetition, dashes, isolated short sentences, and other emphasis tools",
+    "antiPatterns": [
+      "3 or more consecutive one-sentence short paragraphs",
+      "many short sentences used to simulate tension",
+      "explaining psychology immediately after every action",
+      "repeating the same sentence pattern to create fake rhythm"
+    ]
+  },
+  "sampleParagraph": "A 120-250 word target-style sample. Do not turn it into plot outline.",
+  "consistencyChecks": [
+    "Concrete checks future chapter reviews should use to detect style drift"
+  ]
+}
+
+Rules:
+- Match genre, premise, character identities, and reader expectations.
+- Do not rely on abstract adjectives only; every field must guide actual prose.
+- proseRhythm must not be fixed word-count rules; describe reviewable rhythm principles and anti-patterns.
+- sampleParagraph demonstrates prose texture only. Do not reveal future plot.
+- prohibitedPatterns must contain at least 3 entries; consistencyChecks must contain at least 3 entries.
+- proseRhythm.antiPatterns must contain at least 4 entries.
+${strictJsonOutputRules()}`,
+    };
+}
 function buildArchitecturePrompt(input) {
     return {
         purpose: 'architecture',
@@ -84,7 +133,7 @@ function buildArchitecturePrompt(input) {
 ${input.state.initialPrompt}
 
 ## Goals
-- Generate at least ${input.state.targetChapters} chapter architectures for this first run.
+- Whole-book target is about ${input.state.plannedTotalChapters ?? input.state.targetChapters} chapters; generate only the first ${input.state.targetChapters} chapter architectures in this first batch.
 - The full-book architecture should define the long-term main line and ending direction.
 - Volume architecture should define phase conflict, climax, and volume-end hooks.
 - Chapter architecture must cover only what should happen in that chapter and must not reveal later concrete events early.
@@ -126,6 +175,7 @@ Output valid JSON only, in this shape:
 
 Rules:
 - chapters.length must be at least ${input.state.targetChapters}.
+- chapters do not need to cover the whole book; when writing reaches the boundary, the workflow will request architecture_extension.
 - chapterNumber must start at 1 and increase contiguously.
 - volumeId must reference an id from volumes.
 - volumePacing must provide one pacing board for every volume.
@@ -133,6 +183,71 @@ Rules:
 ${strictJsonOutputRules()}`,
     };
 }
+function buildArchitectureExtensionPrompt(input) {
+    const start = input.state.currentChapter;
+    const total = input.state.plannedTotalChapters ?? input.state.targetChapters;
+    const end = Math.min(total, start + input.state.targetChapters - 1);
+    return {
+        purpose: 'architecture_extension',
+        expectedFormat: 'JSON matching ArchitectureExtensionPayloadSchema',
+        prompt: `You are the chief architect for a long-form novel. The manuscript has reached the edge of the existing chapter plan; extend the architecture from current continuity.
+
+## Extension Range
+- Start at chapter ${start}.
+- This batch should plan through chapter ${end} at most.
+- The whole-book target ends at chapter ${total}.
+
+## Extension Principles
+- Do not rewrite existing chapter architecture; append only new chapter architecture.
+- New chapters must follow recent memory, the character state table, active foreshadow threads, and volume pacing boards.
+- If the next chapters enter a new volume, add volumes and volumePacing. If they remain in an existing volume, you may provide an updated pacing board for that volume.
+- If the full-book direction needs adjustment because of written material, include fullUpdate. fullUpdate must be a complete replacement for architecture/full.md, not a change note.
+- Chapter architecture must cover only what should happen in that chapter and must not reveal later concrete events early.
+
+${input.context ? `## Existing Context\n${input.context}\n` : ''}## Output Requirements
+Output valid JSON only, in this shape:
+{
+  "fullUpdate": "optional complete updated full-book architecture",
+  "volumes": [
+    {
+      "id": "v2",
+      "title": "New or updated volume title",
+      "summary": "Volume goal, conflict, climax, and end hook",
+      "order": 2
+    }
+  ],
+  "volumePacing": [
+    {
+      "volumeId": "v2",
+      "start": "Volume starting state",
+      "promise": "Volume promise",
+      "keyTurns": ["Key turn 1", "Key turn 2"],
+      "midpoint": "Midpoint turn",
+      "climax": "Volume climax",
+      "payoffs": ["Planned payoffs"],
+      "lingeringMysteries": ["Lingering mysteries"]
+    }
+  ],
+  "chapters": [
+    {
+      "chapterNumber": ${start},
+      "title": "Chapter title",
+      "volumeId": "v1",
+      "summary": "Chapter plot summary",
+      "requiredBeats": ["Required beat 1"]
+    }
+  ]
+}
+
+Rules:
+- chapters[0].chapterNumber must equal ${start}.
+- chapterNumber must increase contiguously and must not exceed ${total}.
+- chapters.length should be ${end - start + 1} unless the book has reached its ending.
+- requiredBeats must include at least one concrete, actionable beat.
+- volumeId must reference an existing volume id or a volume id supplied in this response.
+${strictJsonOutputRules()}`,
+    };
+}
 function buildChapterPrompt(input) {
     const ch = input.state.currentChapter;
     const isFirstChapter = ch <= 1;
@@ -142,7 +257,7 @@ function buildChapterPrompt(input) {
         prompt: `You are a professional long-form fiction writer. Write chapter ${ch} directly.
 
 ## Priority Order
-1. Strictly follow the current chapter architecture, user additions, story bible hard constraints, and previous-chapter continuity.
+1. Strictly follow the current chapter architecture, user additions, story bible hard constraints, style guide, and previous-chapter continuity.
 2. Use relevant memory, prior text evidence, and active foreshadow threads.
 3. Treat full-book and volume plans as distant planning context only. Do not write concrete future events early.
 
@@ -157,6 +272,8 @@ ${isFirstChapter
 - The chapter must end on a clear hook: cliffhanger, mystery, emotional resonance, reveal, or volume close — per the chapter architecture endHookFocus. Default: cliffhanger.
 
 ## Style
+- Enforce the Style Guide from context. Treat sampleParagraph as prose texture only; do not copy its content.
+- Enforce Style Guide.proseRhythm: short sentences, one-line paragraphs, repeated sentences, and dashes are emphasis tools, not default narration. Ordinary narration should form natural sentence groups.
 - Match the novel's genre, world, character identities, and emotional tone.
 - Natural, stable, readable language; prioritize narrative progress, character work, and emotional accumulation.
 - Dialogue fits each character's identity, relationship, and situation.
@@ -250,7 +367,7 @@ ${strictJsonOutputRules()}`,
     };
 }
 function buildContinuityReviewPrompt(input) {
-    const end = Math.max(input.state.targetChapters, input.state.currentChapter - 1);
+    const end = Math.max(input.state.plannedTotalChapters ?? input.state.targetChapters, input.state.currentChapter - 1);
     return {
         purpose: 'continuity_review',
         expectedFormat: 'JSON matching ContinuityReviewSchema',
@@ -299,6 +416,8 @@ ${input.context ? `## Review Context\n${input.context}\n` : ''}## Review Focus
 - Whether every requiredBeat is fulfilled; missing beats must appear in acceptance.requiredBeats.missingBeats.
 - Whether this chapter advances the main line, character state, or active foreshadow threads. If it is static, at least one of narrativeProgress/characterProgress/foreshadowProgress must fail.
 - Whether it violates the story bible, character state table, volume pacing board, or prior memory.
+- Whether it violates the Style Guide: narrative voice, sentence density, genre diction, dialogue rules, or prohibited patterns.
+- Whether it violates Style Guide.proseRhythm: excessive short-sentence density, consecutive one-sentence paragraphs, fake rhythm through line breaks, overly direct interior explanation, or repeated sentence patterns.
 - Whether the ending has a clear hook that matches the chapter architecture endHookFocus.
 - Whether it repeats prior chapter beats, conflict patterns, reveals, or dialogue functions.
 - Character voice, motivation, and state vs the story bible and prior memory.
@@ -334,6 +453,10 @@ Output valid JSON only, in this shape:
       "status": "pass | fail",
       "evidence": "Whether it matches the story bible, character state table, and world rules"
     },
+    "proseRhythm": {
+      "status": "pass | fail",
+      "evidence": "Whether it follows Style Guide.proseRhythm; explain whether short sentences, one-line paragraphs, repetition, and interior explanation are controlled"
+    },
     "endingHook": {
       "status": "pass | fail",
       "evidence": "The ending hook passage and its function"
@@ -428,8 +551,12 @@ function buildPromptForStep(input) {
             return buildMetadataPrompt(input);
         case 'story_bible':
             return buildStoryBiblePrompt(input);
+        case 'style_guide':
+            return buildStyleGuidePrompt(input);
         case 'architecture':
             return buildArchitecturePrompt(input);
+        case 'architecture_extension':
+            return buildArchitectureExtensionPrompt(input);
         case 'chapter':
             return buildChapterPrompt(input);
         case 'memory_card':

package/dist/src/core/prompts/zh-CN.js

@@ -74,6 +74,55 @@ ${input.context ? `## 已有上下文\n${input.context}\n` : ''}## 输出结构
 - 不要输出 JSON。`,
     };
 }
+function buildStyleGuidePrompt(input) {
+    return {
+        purpose: 'style_guide',
+        expectedFormat: 'JSON matching StyleGuideSchema',
+        prompt: `你是一名长篇小说文风主编。请根据用户提示、metadata 和故事圣经，生成可被每章写作与审稿长期执行的风格圣经。
+
+## 用户提示词
+${input.state.initialPrompt}
+
+${input.context ? `## 已有上下文\n${input.context}\n` : ''}## 输出要求
+请只输出合法 JSON，格式如下：
+{
+  "narrativeVoice": "叙事人称、视角距离、旁白气质、情绪温度",
+  "pacing": "开章、转场、冲突推进、章末钩子的节奏规则",
+  "diction": "词汇选择、句式密度、题材术语使用边界",
+  "dialogueRules": [
+    "核心人物对白的长度、语气、潜台词、称谓规则"
+  ],
+  "prohibitedPatterns": [
+    "禁止出现的现代梗、解释型旁白、设定堆砌、口吻漂移等"
+  ],
+  "proseRhythm": {
+    "sentenceRhythm": "短句、中句、长句的使用原则；短句应服务转折、危险、情绪落点，而不是默认叙述单位",
+    "paragraphing": "段落应形成完整叙事单元；避免连续单句成段、靠频繁换行制造伪节奏",
+    "interiorityMode": "心理活动如何通过动作、迟疑、感官反应折射；避免频繁直接解释人物想法",
+    "emphasisBudget": "重复句、破折号、孤立短句等强调资源的使用预算",
+    "antiPatterns": [
+      "连续 3 个以上单句短段",
+      "用大量短句模拟紧张感",
+      "每个动作后立刻解释心理",
+      "重复同一句式制造伪节奏"
+    ]
+  },
+  "sampleParagraph": "一段 120-250 字的目标风格示例，不要写成剧情大纲",
+  "consistencyChecks": [
+    "后续章节审稿时用于判断风格是否跑偏的具体检查项"
+  ]
+}
+
+要求：
+- 风格必须匹配 genre、premise、人物身份和目标读者预期。
+- 不要只写抽象形容词；每个字段都要能指导实际行文。
+- proseRhythm 不要写成固定字数规则；要描述可审稿的节奏原则和反模式。
+- sampleParagraph 只展示语言质感，不要提前泄露后续剧情。
+- prohibitedPatterns 至少 3 条，consistencyChecks 至少 3 条。
+- proseRhythm.antiPatterns 至少 4 条。
+${strictJsonOutputRules()}`,
+    };
+}
 function buildArchitecturePrompt(input) {
     return {
         purpose: 'architecture',
@@ -84,7 +133,7 @@ function buildArchitecturePrompt(input) {
 ${input.state.initialPrompt}
 
 ## 目标
-- 本次至少生成 ${input.state.targetChapters} 个章架构。
+- 全本目标约 ${input.state.plannedTotalChapters ?? input.state.targetChapters} 章；本次只生成首批 ${input.state.targetChapters} 个章架构。
 - 全本架构负责长期主线和结局方向。
 - 卷架构负责阶段冲突、高潮和卷尾钩子。
 - 章架构必须只覆盖本章应发生的内容，不要提前泄露后续具体事件。
@@ -126,6 +175,7 @@ ${input.context ? `## 已有上下文\n${input.context}\n` : ''}## 输出要求
 
 要求：
 - chapters.length 必须大于等于 ${input.state.targetChapters}。
+- chapters 不需要一次覆盖全本；后续写到边界时会进入 architecture_extension 续规划。
 - chapterNumber 从 1 开始连续递增。
 - volumeId 必须引用 volumes 中存在的 id。
 - volumePacing 必须为每个 volume 提供节奏板。
@@ -133,6 +183,71 @@ ${input.context ? `## 已有上下文\n${input.context}\n` : ''}## 输出要求
 ${strictJsonOutputRules()}`,
     };
 }
+function buildArchitectureExtensionPrompt(input) {
+    const start = input.state.currentChapter;
+    const total = input.state.plannedTotalChapters ?? input.state.targetChapters;
+    const end = Math.min(total, start + input.state.targetChapters - 1);
+    return {
+        purpose: 'architecture_extension',
+        expectedFormat: 'JSON matching ArchitectureExtensionPayloadSchema',
+        prompt: `你是一名长篇小说总架构师。当前已写到既有章纲边界，请基于已有内容续写后续章架构。
+
+## 续规划范围
+- 从第 ${start} 章开始。
+- 本批最多规划到第 ${end} 章。
+- 全本目标到第 ${total} 章结束。
+
+## 续规划原则
+- 不要改写已经存在的章节架构；只追加新的 chapter architecture。
+- 新增章节必须承接最近记忆、角色状态表、活跃伏笔和卷级节奏板。
+- 如果后续章节进入新卷，可以新增 volumes 和 volumePacing；如果仍在旧卷，可以补充/更新该卷节奏板。
+- 如果全本方向因已写内容需要微调，可以输出 fullUpdate；fullUpdate 必须是可覆盖 architecture/full.md 的完整更新版，而不是变更说明。
+- 章架构必须只覆盖本章应发生的内容，不要提前泄露更后面的具体事件。
+
+${input.context ? `## 已有上下文\n${input.context}\n` : ''}## 输出要求
+请只输出合法 JSON，格式如下：
+{
+  "fullUpdate": "可选：完整更新后的全本架构 Markdown/文本",
+  "volumes": [
+    {
+      "id": "v2",
+      "title": "新增或更新卷标题",
+      "summary": "本卷目标、冲突、高潮和卷尾钩子",
+      "order": 2
+    }
+  ],
+  "volumePacing": [
+    {
+      "volumeId": "v2",
+      "start": "本卷起点",
+      "promise": "本卷承诺",
+      "keyTurns": ["关键转折1", "关键转折2"],
+      "midpoint": "中点转折",
+      "climax": "本卷高潮",
+      "payoffs": ["计划回收点"],
+      "lingeringMysteries": ["遗留悬念"]
+    }
+  ],
+  "chapters": [
+    {
+      "chapterNumber": ${start},
+      "title": "章标题",
+      "volumeId": "v1",
+      "summary": "本章剧情摘要",
+      "requiredBeats": ["必须完成的情节点1"]
+    }
+  ]
+}
+
+要求：
+- chapters[0].chapterNumber 必须等于 ${start}。
+- chapterNumber 必须连续递增，且不能超过 ${total}。
+- chapters.length 建议为 ${end - start + 1}，除非已经到全本结尾。
+- requiredBeats 至少 1 条，且必须具体可执行。
+- volumeId 必须引用已有或本次新增 volumes 中存在的 id。
+${strictJsonOutputRules()}`,
+    };
+}
 function buildChapterPrompt(input) {
     const ch = input.state.currentChapter;
     const isFirstChapter = ch <= 1;
@@ -142,7 +257,7 @@ function buildChapterPrompt(input) {
         prompt: `你是一位擅长创作长篇网络小说的职业作者。请直接完成第 ${ch} 章正文。
 
 ## 执行优先级
-1. 先严格遵守"本章架构、用户补充要求、故事圣经硬约束、上一章承接"。
+1. 先严格遵守"本章架构、用户补充要求、故事圣经硬约束、风格圣经、上一章承接"。
 2. 再参考"历史相关记忆、历史原文证据、活跃伏笔"保证一致性。
 3. 最后才参考"全本/本卷远场规划"，且不得提前写出尚未发生的情节。
 
@@ -157,6 +272,8 @@ ${isFirstChapter
 - 章末必须有清晰的"钩子"：可以是悬念、反转、剧情承诺、情绪余韵或卷末高潮——按本章架构 endHookFocus 字段决定。如果未指定，默认用悬念。
 
 ## 风格
+- 严格执行上下文中的 Style Guide；sampleParagraph 只作为语言质感参考，不要复写其内容。
+- 严格执行 Style Guide.proseRhythm：短句、单句段、重复句、破折号是强调资源，不是默认叙述单位；常规叙述要形成自然句群。
 - 文风必须与本书题材、世界观、人物身份、情感基调一致。
 - 语言自然、稳定、可读，优先服务叙事推进、人物塑造和情绪积累。
 - 对话符合人物身份、关系和处境；重要情绪通过动作、神态、节奏、潜台词体现。
@@ -249,7 +366,7 @@ ${strictJsonOutputRules()}`,
     };
 }
 function buildContinuityReviewPrompt(input) {
-    const end = Math.max(input.state.targetChapters, input.state.currentChapter - 1);
+    const end = Math.max(input.state.plannedTotalChapters ?? input.state.targetChapters, input.state.currentChapter - 1);
     return {
         purpose: 'continuity_review',
         expectedFormat: 'JSON matching ContinuityReviewSchema',
@@ -298,6 +415,8 @@ ${input.context ? `## 审阅上下文\n${input.context}\n` : ''}## 审阅重点
 - requiredBeats 是否全部完成；缺失项必须写入 acceptance.requiredBeats.missingBeats。
 - 本章是否推进主线、人物状态或活跃伏笔；如果完全原地踏步，narrativeProgress/characterProgress/foreshadowProgress 至少一项必须 fail。
 - 是否违反故事圣经、角色状态表、卷级节奏板或历史记忆。
+- 是否违反 Style Guide：叙事声音、句式密度、题材词汇、对白规则和禁用模式。
+- 是否违反 Style Guide.proseRhythm：短句密度过高、连续单句短段、靠换行制造伪节奏、心理解释过直白、重复同一句式。
 - 章末是否有清晰钩子，且符合本章 endHookFocus。
 - 是否重复之前章节已经完成的桥段、冲突结构、信息揭示或对话功能。
 - 人物声音、动机、状态是否符合故事圣经与历史记忆。
@@ -333,6 +452,10 @@ ${input.context ? `## 审阅上下文\n${input.context}\n` : ''}## 审阅重点
       "status": "pass | fail",
       "evidence": "是否符合故事圣经、角色状态表和世界规则"
     },
+    "proseRhythm": {
+      "status": "pass | fail",
+      "evidence": "是否符合 Style Guide.proseRhythm；说明短句/单句段/重复句/心理解释是否被合理控制"
+    },
     "endingHook": {
       "status": "pass | fail",
       "evidence": "章末钩子的具体段落和作用"
@@ -427,8 +550,12 @@ function buildPromptForStep(input) {
             return buildMetadataPrompt(input);
         case 'story_bible':
             return buildStoryBiblePrompt(input);
+        case 'style_guide':
+            return buildStyleGuidePrompt(input);
         case 'architecture':
             return buildArchitecturePrompt(input);
+        case 'architecture_extension':
+            return buildArchitectureExtensionPrompt(input);
         case 'chapter':
             return buildChapterPrompt(input);
         case 'memory_card':