@actalk/inkos-core 1.3.6 → 1.3.7-canary.36.1

package/dist/agents/architect.js

@@ -3,7 +3,13 @@ import { readGenreProfile } from "./rules-reader.js";
 import { writeFile, mkdir, rm } from "node:fs/promises";
 import { join } from "node:path";
 import { renderHookSnapshot } from "../utils/memory-retrieval.js";
-/** 拆 markdown 的首部 YAML frontmatter 和正文。没有 frontmatter 时返回 frontmatter: null。 */
+import { shouldPromoteHook, } from "../utils/hook-promotion.js";
+/**
+ * Split a markdown string into its leading YAML frontmatter block and the
+ * remaining body. Returns `frontmatter: null` when no frontmatter is present.
+ * Only recognises a frontmatter block that starts on the FIRST non-empty
+ * line — embedded `---` sections in prose are left alone.
+ */
 function extractYamlFrontmatter(raw) {
     if (!raw)
         return { frontmatter: null, body: "" };
@@ -32,19 +38,13 @@ export class ArchitectAgent extends BaseAgent {
             ? this.buildRevisePrompt(options.reviseFrom)
             : "";
         const numericalBlock = gp.numericalSystem
-            ? `- 有明确的数值/资源体系可追踪
-- 在 book_rules 中定义 numericalSystemOverrides（hardCap、resourceTypes）`
+            ? "- 有明确的数值/资源体系可追踪\n- 在 book_rules 中定义 numericalSystemOverrides（hardCap、resourceTypes）"
             : "- 本题材无数值系统，不需要资源账本";
-        const powerBlock = gp.powerScaling
-            ? "- 有明确的战力等级体系"
-            : "";
-        const eraBlock = gp.eraResearch
-            ? "- 需要年代考据支撑（在 book_rules 中设置 eraConstraints）"
-            : "";
-        const basePrompt = resolvedLanguage === "en"
+        const powerBlock = gp.powerScaling ? "- 有明确的战力等级体系" : "";
+        const eraBlock = gp.eraResearch ? "- 需要年代考据支撑（在 book_rules 中设置 eraConstraints）" : "";
+        const systemPrompt = resolvedLanguage === "en"
             ? this.buildEnglishFoundationPrompt(book, gp, genreBody, contextBlock, reviewFeedbackBlock, numericalBlock, powerBlock, eraBlock)
             : this.buildChineseFoundationPrompt(book, gp, genreBody, contextBlock, reviewFeedbackBlock, numericalBlock, powerBlock, eraBlock);
-        const systemPrompt = revisePrompt + basePrompt;
         const langPrefix = resolvedLanguage === "en"
             ? `【LANGUAGE OVERRIDE】ALL output (story_frame, volume_map, roles, book_rules, pending_hooks) MUST be written in English. Character names, place names, and all prose must be in English. The === SECTION: === tags remain unchanged. Do NOT emit rhythm_principles or current_state sections — rhythm principles live inside the last paragraph of volume_map; environment/era anchors (when relevant) are woven into story_frame's world-tonal-ground paragraph.\n\n`
             : "";
@@ -52,52 +52,46 @@ export class ArchitectAgent extends BaseAgent {
             ? `Generate the complete foundation for a ${gp.name} novel titled "${book.title}". Write everything in English.`
             : `请为标题为"${book.title}"的${gp.name}小说生成完整基础设定。`;
         const response = await this.chat([
-            { role: "system", content: langPrefix + systemPrompt },
+            { role: "system", content: langPrefix + systemPrompt + revisePrompt },
             { role: "user", content: userMessage },
-        ], { temperature: 0.8, maxTokens: 16384 });
-        return this.parseSections(response.content);
+        ], { temperature: 0.8 });
+        return this.parseSections(response.content, resolvedLanguage);
     }
     buildRevisePrompt(reviseFrom) {
-        return `你在把一本已有书的架构稿从条目式升级成段落式架构稿 + 一人一卡的角色目录。
+        return `\n\n## 既有架构稿修订模式
+你在把一本已有书的架构稿从条目式升级为当前的段落式架构稿 + 一人一卡角色目录；如果它已经是 Phase 5 结构，则按用户反馈二次重写。
 
-原书信息（条目式架构稿原文，这是权威内容，必须完整保留里面的世界观 / 角色 / 主线 / 伏笔）：
+原书信息（这是权威内容，必须完整保留其中的世界观、角色、主线、伏笔和语气）：
 
-【story_bible.md 全文】
+【story_bible / story_frame 全文】
 ${reviseFrom.storyBible || "（无）"}
 
-【volume_outline.md 全文】
+【volume_outline / volume_map 全文】
 ${reviseFrom.volumeOutline || "（无）"}
 
-【book_rules.md 全文】
+【book_rules 全文】
 ${reviseFrom.bookRules || "（无）"}
 
-【character_matrix.md 全文】
+【character_matrix / roles 全文】
 ${reviseFrom.characterMatrix || "（无）"}
 
 你的任务：
-1. 把 story_bible 的内容重新组织成 4 段段落式 story_frame.md（主题 / 核心冲突 / 世界观底色 / 终局方向）
-2. 把 volume_outline 的内容重新组织成 5 段 volume_map.md + 末尾 1 段节奏原则
-3. 把 character_matrix 里的每个角色拆成一份 roles/主要角色/<name>.md 或 roles/次要角色/<name>.md
-
-严格约束：
-- 世界观设定、角色设定、主线走向、已埋下的伏笔一个字都不能丢
-- 如果原内容里有 bullet 点，把它们连成段落；不要只是把 bullet 转成句号分隔
-- 主次角色的判断依据：character_matrix 里已标注的如果有，沿用；没有的话，把在 volume_outline 里出现频次高、或者承担主线冲突的列为主要，其余为次要
-- 基调 / 语气不要改变
-- 如果原内容里留有空白或未展开项，保留为空，不要主动补全
+1. 把现有内容重新组织成当前 5 段 SECTION：story_frame / volume_map / roles / book_rules / pending_hooks
+2. story_frame 使用段落式世界观与核心冲突，不要退回条目表格
+3. volume_map 使用段落式卷/章级方向，并把节奏原则放进末段
+4. roles 必须按一人一卡输出，主要/次要角色判断沿用原内容，缺失才按主线重要性推断
+5. pending_hooks 必须保留原有未回收伏笔，不要因为重写架构稿而清空
+6. 不要改动已写章节的运行时事实，不要重置 current_state / pending_hooks 之外的运行时日志
 
 用户额外要求：
 ${reviseFrom.userFeedback || "（无）"}
-
----
-
 `;
     }
     // -------------------------------------------------------------------------
-    // Phase 5 段落式 prompt — zh
+    // Prose prompt — zh (primary)
     // -------------------------------------------------------------------------
     buildChineseFoundationPrompt(book, gp, genreBody, contextBlock, reviewFeedbackBlock, numericalBlock, powerBlock, eraBlock) {
-        return `你是这本书的总架构师。你的唯一输出是**段落密度的基础设定**——不是表格、不是 schema、不是条目化 bullet。这本书的"灵气"从你这里来。你的段落密度决定了后面 planner 能不能读出"稀疏 memo"，writer 能不能写出活人，reviewer 能不能校准硬伤。${contextBlock}${reviewFeedbackBlock}
+        return `你是这本书的总架构师。你的唯一输出是**散文密度的基础设定**——不是表格、不是 schema、不是条目化 bullet。v6 以后这本书的"灵气"从哪里来？从你这里来。你的散文密度决定了后面 planner 能不能读出"稀疏 memo"，writer 能不能写出活人，reviewer 能不能校准硬伤。${contextBlock}${reviewFeedbackBlock}
 
 ## 书籍元信息
 - 平台：${book.platform}
@@ -117,46 +111,64 @@ ${eraBlock}
 ## 输出结构（5 个 SECTION，严格按 === SECTION: === 分块，不要漏任何一块）
 
 ## 去重铁律（必读）
-禁止在多段里重复同一事实。主角的完整角色线只写在 roles；世界铁律只写在 story_frame.世界观底色；节奏原则只写在 volume_map 最后一段；角色当前现状只写在 roles.当前现状；初始钩子只写在 pending_hooks（startChapter=0 行）。**如果本书是年代文/历史同人/都市重生等需要年份、季节、重大历史事件作为锚点的题材**，把环境/时代锚自然织进 story_frame.世界观底色（"1985 年 7 月，非典刚过"这类）；**修仙/玄幻/系统等没有真实年份的题材直接省略**，不要硬凑。如果一个段落写了另一段的内容，删掉。
+禁止在多段里重复同一事实。主角弧线只写在 roles；世界铁律只写在 story_frame.世界观底色；节奏原则只写在 volume_map 最后一段；角色当前现状只写在 roles.当前现状；初始钩子只写在 pending_hooks（startChapter=0 行）。**如果本书是年代文/历史同人/都市重生等需要年份、季节、重大历史事件作为锚点的题材**，把环境/时代锚自然织进 story_frame.世界观底色（"1985 年 7 月，非典刚过"这类）；**修仙/玄幻/系统等没有真实年份的题材直接省略**，不要硬凑。如果一个段落写了另一段的内容，删掉。
 
 ## 预算（超预算必删）
-- story_frame ≤ 3000 字
-- volume_map ≤ 5000 字
-- roles 总 ≤ 8000 字
-- book_rules ≤ 500 字（仅 YAML）
-- pending_hooks ≤ 2000 字
+- story_frame ≤ 3000 chars
+- volume_map ≤ 5000 chars
+- roles 总 ≤ 8000 chars
+- book_rules ≤ 500 chars（仅 YAML）
+- pending_hooks ≤ 2000 chars
 
 === SECTION: story_frame ===
 
-这是段落式骨架。**4 段**，每段约 600-900 字，不要写表格，不要写 bullet list，写成能被人读下去的段落。段落标题用 \`## \` 开头，段落内部是正经段落。**主角的完整角色线不写在本 section；它的权威来源是 roles/主要角色/<主角>.md。** 本段只需一句指针："本书主角是 X，完整角色线详见 roles/主要角色/X.md"。
+这是散文骨架。**4 段**，每段约 600-900 字，不要写表格，不要写 bullet list，写成能被人读下去的段落。段落标题用 \`## \` 开头，段落内部是正经段落。**主角弧线不写在本 section；它的权威来源是 roles/主要角色/<主角>.md。** 本段只需一句指针："本书主角是 X，完整弧线详见 roles/主要角色/X.md"。
 
 ### 段 1：主题与基调
-写这本书到底讲的是什么——不是"讲主角如何从弱到强"这种空话，而是具体的命题（"一个被时代按在泥里的人，如何选择不被改写"、"当所有人都在撒谎时，坚持记录真相要付出什么代价"）。主题下面跟着基调——温情冷冽悲壮肃杀，哪一种？为什么是这种而不是另一种？结尾用一句话指向主角并引向 roles（例："本书主角是林辞，完整角色线详见 roles/主要角色/林辞.md"）。
+写这本书到底讲的是什么——不是"讲主角如何从弱到强"这种空话，而是具体的命题（"一个被时代按在泥里的人，如何选择不被改写"、"当所有人都在撒谎时，坚持记录真相要付出什么代价"）。主题下面跟着基调——温情冷冽悲壮肃杀，哪一种？为什么是这种而不是另一种？结尾用一句话指向主角并引向 roles（例："本书主角是林辞，完整弧线详见 roles/主要角色/林辞.md"）。
 
-### 段 2：核心冲突与对手定性
+### 段 2：核心冲突、对手定性、前台/后台双层故事
 这本书的主要矛盾是什么？不是"正邪对抗"，而是"因为 A 相信 X、B 相信 Y，所以他们一定会在某件事上对撞"。主要对手是谁（至少 2 个：一个显性对手 + 一个结构性对手/体制），他们的动机从哪里长出来。对手不是工具，对手有自己的逻辑。
 
+**本段必须显式写出"前台故事 / 后台故事"两条线**（番茄老师弈青锋的"台前台后"分层法）：
+- **前台故事**：读者每章看得到的表层冲突（查案、打怪、升级、谈恋爱、搞事业等），每个卷/arc 有独立的显性目标和完结点
+- **后台故事**：贯穿全书的暗线——藏在所有前台事件背后的那台"机器"（幕后黑手、阴谋、身世秘密、体制压迫、命运诅咒等），读者只能通过碎片拼出来，大结局时才整体兑现
+
+两条线必须有因果关联，不能是平行宇宙——每一段前台冲突的背后都应该能追溯到后台故事的某个齿轮在转。**如果只有前台没有后台，故事会散成"独立事件集"，没有往前拉的引力；如果只有后台没有前台，故事会憋闷、看不到爽感**。本段用散文明确写出：本书前台是什么、后台是什么、两者怎么咬合。
+
 ### 段 3：世界观底色（铁律 + 质感 + 本书专属规则）
-这个世界的运行规则是什么？3-5 条**不可违反的铁律**——以段落形式写出，不要 bullet。这个世界的质感是什么——湿的还是干的、快的还是慢的、噪的还是静的？给 writer 一个明确的感官锚。**这一段同时承担原先 book_rules 正文里写的"叙事视角 / 本书专属规则 / 核心冲突驱动"等内容**——全部合并到这里写一次就够，不要再去 book_rules 重复。
+这个世界的运行规则是什么？3-5 条**不可违反的铁律**——以 prose 写出，不要 bullet。这个世界的质感是什么——湿的还是干的、快的还是慢的、噪的还是静的？给 writer 一个明确的感官锚（这是原来 particle_ledger 承载的基调部分）。**这一段同时承担原先 book_rules 正文里写的"叙事视角 / 本书专属规则 / 核心冲突驱动"等 prose 内容**——全部合并到这里写一次就够，不要再去 book_rules 重复。
 
-### 段 4：终局方向
+### 段 4：终局方向 + 全书 Objective（OKR 大纲的根）
 这本书最后一章大概是什么感觉——不是"主角登顶"、"大结局"这种套话，而是**最后一个镜头**大致长什么样。主角最后在哪、做什么、身边有谁、心里想什么。这是给全书所有后面的规划一个远方靶子。
 
+**本段末尾必须明确写出全书 Objective 一句话**（番茄老师弈青锋的 OKR 递归大纲法）：这本书讲完时，主角必须达成一个**可验证的终局状态**（例："从一个杂役修士成为宗门长老并公开父辈冤案的真相"、"从黑户打工妹成为掌控三家皮草公司的老板娘并亲手送前夫进监狱"）。不要写"变强"、"复仇"这类抽象词，要写**一个能被外部观察者判定"达成 / 未达成"的具体状态**。这个 Objective 是全书 OKR 递归大纲的根——下面 volume_map 的每一卷会分解出这个 O 对应的 Key Results。
+
 === SECTION: volume_map ===
 
-这是分卷段落式地图，**5 段主体 + 1 段节奏原则尾段**。**关键要求：只写到卷级内容**——写清楚每卷的主题、情绪曲线、卷间钩子、角色阶段目标、卷尾不可逆事件。**禁止指定具体章号任务**（不要写"第 17 章让他回家"这种章级布局）。章级规划是 Phase 3 planner 的职责，架构师只搭骨架、不编章目。
+这是分卷散文地图，**5 段主体 + 1 段节奏原则尾段**。**关键要求：只写到卷级 prose**——写清楚每卷的主题、情绪曲线、卷间钩子、角色阶段目标、卷尾不可逆事件。**禁止指定具体章号任务**（不要写"第 17 章让他回家"这种章级布局）。章级规划是 Phase 3 planner 的职责，架构师只搭骨架、不编章目。
 
 ### 段 1：各卷主题与情绪曲线
 有几卷？每卷的主题一句话，每卷的情绪曲线一段（哪里压、哪里爽、哪里冷、哪里暖）。不要机械的"第一卷打小怪第二卷打大怪"，写情绪的流动。
 
-### 段 2：卷间钩子与回收承诺
-第 1 卷埋什么钩子、在哪一卷回收；第 2 卷埋什么、在哪一卷回收。段落式写，不要表格。**只写卷级**（如"第 1 卷埋的身世之谜在第 3 卷回收"），不要写具体章号。
+### 段 2：卷间钩子与回收承诺（前台/后台双层都要覆盖）
+第 1 卷埋什么钩子、在哪一卷回收；第 2 卷埋什么、在哪一卷回收。散文写，不要表格。**只写卷级**（如"第 1 卷埋的身世之谜在第 3 卷回收"），不要写具体章号。
+
+**钩子必须覆盖前台 + 后台两层**（对应 story_frame.段 2 建立的双层故事）：
+- 前台钩子：当前卷内 arc 层面的短期钩子（查案谜题、对手身份、资源争夺等），预期在 1-2 卷内回收
+- 后台钩子：贯穿全书的主线钩子（幕后真相、身世、体制秘密等），预期在终卷前后回收，核心的 3-7 条属于 core_hook=true
+
+**如果本段只写前台钩子、没有后台钩子暗桩，说明你漏了整本书的引力轴，必须补上。**
 
-### 段 3：角色阶段性目标
-主角在第 1 卷末要到什么状态？第 2 卷末？每一卷结束时主角的身份/关系/能力/心境应该是什么。次要角色的阶段性变化也要点到（师父在第 2 卷会死、对手在第 3 卷会黑化等）。写阶段性，不写完整角色线（完整角色线在 roles）。
+### 段 3：各卷 OKR（Objective + Key Results）
+用 OKR 递归大纲法分解全书 Objective（story_frame.段 4 末尾定的根 O）：每一卷都必须明确给出：
+- **Objective（卷级目标）**：本卷结束时主角必须达成的**可验证状态**，一句话，与全书 Objective 逻辑递进相连（例：全书 O = "成为宗门长老并公开冤案"；卷 1 O = "从杂役转入正式弟子籍并拿到第一份能指向真相的线索"）
+- **Key Results（3 条，可量化/可观察）**：支撑该 O 达成的三个关键子成果，每条必须是外部观察者能判定是否完成的状态变更（例 KR1 = "拿下药园执事位置"、KR2 = "与灵安峰结成稳定盟约"、KR3 = "发现父辈案卷的第一半页残片"）。不要写"变强"、"成长"这类模糊 KR
+
+次要角色的阶段性变化也要点到（师父在第 2 卷会死、对手在第 3 卷会黑化等），写在 KR 条目下作为附注。写阶段性，不写完整弧线（完整弧线在 roles）。**每一卷 3 个 KR 是下游 planner 分解章节任务的直接依据——planner 拿到一卷的 3 个 KR 后，按每 3-5 章推进一个 KR 的节奏排章。**
 
 ### 段 4：卷尾必须发生的改变
-每一卷最后一章必须发生什么不可逆的事——权力结构改变、关系破裂、秘密暴露、主角身份重定位。写段落，一卷一段。**只写"必须发生什么"，不指定是第几章**。
+每一卷最后一章必须发生什么不可逆的事——权力结构改变、关系破裂、秘密暴露、主角身份重定位。写散文，一卷一段。**只写"必须发生什么"，不指定是第几章**。
 
 ### 段 5：节奏原则（具体化 + 通用）
 **这是节奏原则的唯一归宿，不再有独立 rhythm_principles section。** 本段输出 6 条节奏原则。**至少 3 条必须具体化到本书**（例："前 30 章每 5 章一个小爽点"），其余可保留通用原则（例："拒绝机械降神"、"高潮前 3-5 章埋伏笔"）。具体化 + 通用混合是合法的。反面例子："节奏要张弛有度"（废话）。正面例子："前 30 章每 5 章一个小爽点，且小爽点必须落在章末 300 字内"。6 条各写 2-3 句，覆盖（顺序不强制、可替换同权重议题）：
@@ -167,20 +179,15 @@ ${eraBlock}
 5. 爽点节奏——爽点间距多少章一个？什么类型为主？（具体化优先）
 6. 情感节点递进——情感关系每多少章必须有一次实质推进？
 
-### 黄金三章法则（前三章必须遵循）
-- 第1章：抛出核心冲突（主角立即面临困境/危机/选择），禁止大段背景灌输
-- 第2章：展示金手指/核心能力（主角如何应对第1章的困境），让读者看到爽点预期
-- 第3章：明确短期目标（主角确立第一个具体可达成的目标），给读者追读理由
-
 === SECTION: roles ===
 
-一人一卡。**主角卡是本书角色线的唯一权威来源**——story_frame 不再写主角的完整角色线，writer/planner 都从这里读。用以下格式分隔：
+一人一卡 prose。**主角卡是本书角色弧线的唯一权威来源**——story_frame 不再写主角弧线，writer/planner 都从这里读。用以下格式分隔：
 
 ---ROLE---
 tier: major
 name: <角色名>
 ---CONTENT---
-（这里写段落式角色卡，下面的小标题必须全部出现，每段至少 3 行正经段落，不要写表格）
+（这里写散文角色卡，下面的小标题必须全部出现，每段至少 3 行正经散文，不要写表格）
 
 ## 核心标签
 （3-5 个关键词 + 一句话为什么是这些词）
@@ -189,10 +196,10 @@ name: <角色名>
 （1-2 个与核心标签反差的具体细节——"冷酷杀手但会给流浪猫留鱼骨"。反差细节是人物立体化的公式，必须有。）
 
 ## 人物小传（过往经历）
-（一段段落，说这个人怎么变成现在这样。童年/重大事件/塑造性格的那件事。只写关键过往，简版。）
+（一段散文，说这个人怎么变成现在这样。童年/重大事件/塑造性格的那件事。只写关键过往，简版。）
 
-## 主角线（起点 → 终点 → 代价）
-**只有主角必须写本段；其他 major 角色如果分量重也可以写，否则略过。**主角从哪里出发（身份、处境、核心缺陷、一开始最想要什么），到哪里落脚（最终变成什么样的人、拿到/失去什么），为了这个落脚他付出了什么不可逆的代价（关系、身体、信念、某段过去）。不要只写"变强"这种平面变化，要写**内在的位移**。写足写实。
+## 主角弧线（起点 → 终点 → 代价）
+**只有主角必须写本段；其他 major 角色如果弧线分量重也可以写，否则略过。**主角从哪里出发（身份、处境、核心缺陷、一开始最想要什么），到哪里落脚（最终变成什么样的人、拿到/失去什么），为了这个落脚他付出了什么不可逆的代价（关系、身体、信念、某段过去）。不要只写"变强"这种平面变化，要写**内在的位移**。本段是之前 story_frame.段 2 迁移过来的权威位置，写足写实。
 
 ## 当前现状（第 0 章初始状态）
 （第 0 章时他在哪、做什么、处境如何、最近最烦心的事。**只写角色个人处境**——初始钩子写在 pending_hooks 的 startChapter=0 行；环境/时代锚（如果是需要年份的题材）织进 story_frame.世界观底色。不再有独立的 current_state section。）
@@ -203,7 +210,7 @@ name: <角色名>
 ## 内在驱动
 （他想要什么、为什么想要、愿意付出什么代价。）
 
-## 成长变化
+## 成长弧光
 （他在这本书里会经历什么内在位移——变好变坏变复杂，落在哪里。非主角可短可长。）
 
 ---ROLE---
@@ -224,7 +231,7 @@ name: <次要角色名>
 
 === SECTION: book_rules ===
 
-**只输出 YAML frontmatter 一块——零段落正文。** 所有的"叙事视角 / 本书专属规则 / 核心冲突驱动"等段落已经合并到 story_frame.世界观底色，不要在这里重复写。
+**只输出 YAML frontmatter 一块——零散文。** 所有的"叙事视角 / 本书专属规则 / 核心冲突驱动"等散文已经合并到 story_frame.世界观底色，不要在这里重复写。
 \`\`\`
 ---
 version: "1.0"
@@ -249,29 +256,34 @@ enableFullCastTracking: false
 
 === SECTION: pending_hooks ===
 
-初始伏笔池（Markdown表格，8 列基础版）：
-| hook_id | 起始章节 | 类型 | 状态 | 最近推进 | 预期回收 | 回收节奏 | 备注 |
+初始伏笔池（Markdown表格），Phase 7 扩展列：
+| hook_id | 起始章节 | 类型 | 状态 | 最近推进 | 预期回收 | 回收节奏 | 上游依赖 | 回收卷 | 核心 | 半衰期 | 备注 |
 
 伏笔表规则：
 - 第5列必须是纯数字章节号，不能写自然语言描述
 - 建书阶段所有伏笔都还没正式推进，所以第5列统一填 0
 - 第7列必须填写：立即 / 近期 / 中程 / 慢烧 / 终局 之一
+- 第8列「上游依赖」：列出必须在本伏笔之前种下/回收的上游 hook_id，格式如 [H003, H007]；若无依赖填「无」
+- 第9列「回收卷」：用自然语言写该伏笔计划在哪一卷哪一段回收（例："第2卷中段"、"终卷终章前"）。不强制解析为章号
+- 第10列「核心」：是否主线承重伏笔 true / false。主线承重伏笔一本书最多 3-7 条（主谜团、身世、核心承诺），其余次要伏笔填 false
+- 第11列「半衰期」：可选，整数章数。若不填自动按回收节奏推导（立即/近期 = 10、中程 = 30、慢烧/终局 = 80）
 - 初始线索放备注列，不放第5列
-- **初始世界状态 / 初始敌我关系** 如果有关键信息（例如"主角身上带着父亲的笔记本"、"体制已经开始监视码头"），可以作为 startChapter=0 的种子行录入，备注列说明其"初始状态"属性
+- **初始世界状态 / 初始敌我关系** 如果有关键信息（例如"主角身上带着父亲的笔记本"、"体制已经开始监视码头"），可以作为 startChapter=0 的种子行录入，备注列说明其"初始状态"属性。
 
 ## 最后强调
 - 符合${book.platform}平台口味、${gp.name}题材特征
 - 主角人设鲜明、行为边界清晰
 - 伏笔前后呼应、配角有独立动机不是工具人
-- **story_frame / volume_map / roles 必须是段落密度，不要退化成 bullet**
-- **book_rules 只留 YAML，不要写段落正文**
-- **不要输出 rhythm_principles 或 current_state 独立 section**——节奏原则合并进 volume_map 尾段；角色初始状态写在 roles.当前现状，初始钩子写在 pending_hooks（startChapter=0 行），环境/时代锚（仅历史/年代/都市重生等需要年份的题材）织进 story_frame.世界观底色，不要硬凑`;
+- **story_frame / volume_map / roles 必须是散文密度，不要退化成 bullet**
+- **book_rules 只留 YAML，不要写散文**
+- **不要输出 rhythm_principles 或 current_state 独立 section**——节奏原则合并进 volume_map 尾段；角色初始状态写在 roles.当前现状，初始钩子写在 pending_hooks（startChapter=0 行），环境/时代锚（仅历史/年代/都市重生等需要年份的题材）织进 story_frame.世界观底色，不要硬凑
+- **pending_hooks 表必须包含 Phase 7 扩展列——depends_on 标出因果链、pays_off_in_arc 锁定回收大致位置、core_hook 标记主线承重伏笔（3-7 条）、half_life 仅给重点伏笔设置**
+
+## 硬性完结检查（生成前读一遍）
+必须依次输出全部 **5 个 SECTION 块**：story_frame → volume_map → roles → book_rules → pending_hooks，不允许因为 story_frame 或 volume_map 写长了就不写后 3 段。哪怕 roles 只列 3 个角色、book_rules 只有 YAML 小块、pending_hooks 只有 3 行，也要完整输出。只有写完 pending_hooks 最后一行才算交付。`;
     }
-    // -------------------------------------------------------------------------
-    // Phase 5 段落式 prompt — en
-    // -------------------------------------------------------------------------
     buildEnglishFoundationPrompt(book, gp, genreBody, contextBlock, reviewFeedbackBlock, numericalBlock, powerBlock, eraBlock) {
-        return `You are the architect of this book. Your only job is to produce **prose-density foundation design** — not tables, not schema, not bullet lists. The book's aura comes from your prose density: the Phase 3 planner reads sparse memos out of your volume_map only if it was written to chapter-level prose; the writer only produces living characters because your role sheets carry contrast details; the reviewer only catches hard errors because your story_frame set the tonal anchors.${contextBlock}${reviewFeedbackBlock}
+        return `You are the architect of this book. Your only job is to produce **prose-density foundation design** — not tables, not schema, not bullet lists. The book's aura comes from your prose density: Phase 3 planner reads sparse memos out of your volume_map only if it was written to chapter-level prose; the writer only produces living characters because your role sheets carry contrast details; the reviewer only catches hard errors because your story_frame set the tonal anchors.${contextBlock}${reviewFeedbackBlock}
 
 ## Book metadata
 - Platform: ${book.platform}
@@ -291,7 +303,7 @@ ${eraBlock}
 ## Output contract (5 === SECTION: === blocks)
 
 ## Deduplication rule (MANDATORY)
-Do not duplicate the same fact across sections. The protagonist's full character arc lives only in roles; world hard-rules live only in story_frame; rhythm principles live only in the last paragraph of volume_map; character initial status lives only in roles.Current_State; initial hooks live only in pending_hooks (start_chapter=0 rows). **When the book is period fiction / historical fanfic / urban reincarnation** — anything pinned to a real year, season, or historic marker — weave the environment/era anchor into story_frame's world-tonal-ground paragraph. **For cultivation / high-fantasy / system genres that have no real-world year, skip it entirely** — do not fabricate an era anchor. If a section repeats content that belongs elsewhere, delete it.
+Do not duplicate the same fact across sections. The protagonist's arc lives only in roles; world hard-rules live only in story_frame; rhythm principles live only in the last paragraph of volume_map; character initial status lives only in roles.Current_State; initial hooks live only in pending_hooks (start_chapter=0 rows). **When the book is period fiction / historical fanfic / urban reincarnation** — anything pinned to a real year, season, or historic marker — weave the environment/era anchor into story_frame's world-tonal-ground paragraph (e.g. "July 1985, just after the SARS wave"). **For cultivation / high-fantasy / system genres that have no real-world year, skip it entirely** — do not fabricate an era anchor. If a section repeats content that belongs elsewhere, delete it.
 
 ## Output budget (over-budget means cut)
 - story_frame ≤ 3000 chars
@@ -302,75 +314,88 @@ Do not duplicate the same fact across sections. The protagonist's full character
 
 === SECTION: story_frame ===
 
-Four prose sections, ~600-900 chars each. No tables. No bullet lists. Real paragraphs. **Do NOT write the protagonist's full character arc here** — that is owned by roles/主要角色/<protagonist>.md. Use a single-line pointer inside this block.
+Four prose sections, ~600-900 chars each. No tables. No bullet lists. Real paragraphs. **Do NOT write the protagonist's full arc here** — that is owned by roles/主要角色/<protagonist>.md. Use a single-line pointer inside this block (e.g. "The protagonist is X; full arc lives in roles/主要角色/X.md").
 
 ## 01_Theme_and_Tonal_Ground
 What is this book actually about — not "hero grows from weak to strong" (empty), but a concrete proposition. Then the tonal ground: warm / cold / fierce / severe — which, and why this and not another. End with a one-line pointer to the protagonist role file.
 
-## 02_Core_Conflict_and_Opponent
+## 02_Core_Conflict_and_Foreground_Background_Story_Layers
 The book's main tension — not "good vs evil" but "because A believes X and B believes Y, they will inevitably collide on Z". At least two opponents: one visible, one structural/systemic. Opponents have their own logic.
 
+**This section must explicitly write out the foreground story / background story layers**:
+- **Foreground story**: the surface conflict the reader sees every chapter (cases, combat, leveling up, romance, business moves). Each volume / arc has its own visible goal and closure point.
+- **Background story**: the hidden machine running through the whole book — the puppet master, conspiracy, origin secret, systemic oppression, fated curse. The reader assembles it from fragments; full payoff lands near the finale.
+
+The two layers must be causally linked, not parallel universes — every foreground conflict should trace back to some gear of the background machine turning. **Foreground-only story collapses into a set of disconnected episodes with no forward pull; background-only story is suffocating and never delivers. Write both in prose here, and name how they interlock.**
+
 ## 03_World_Tonal_Ground (hard rules + sensory tone + book-specific rules)
-The world's operating rules. 3-5 unbreakable laws written as prose, not bullets. Sensory texture: wet or dry, fast or slow, noisy or quiet — give the writer an anchor. **This paragraph also absorbs the narrative prose that used to live in book_rules** (narrative perspective, core conflict driver, book-specific rules). Write them all here once. Do not repeat them in book_rules.
+The world's operating rules. 3-5 unbreakable laws written as prose, not bullets. Sensory texture: wet or dry, fast or slow, noisy or quiet — give the writer an anchor. **This paragraph also absorbs the narrative prose that used to live in book_rules (narrative perspective, core conflict driver, book-specific rules).** Write them all here once. Do not repeat them in book_rules.
 
-## 04_Endgame_Direction
+## 04_Endgame_Direction_and_Book_Objective
 What the last chapter roughly feels like. The final shot: where, doing what, around whom, thinking what. A distant target for every planner call downstream.
 
+**End this paragraph with a one-sentence Book Objective** (the root of the recursive OKR outline): when this book is done, the protagonist must reach a **verifiable end-state** (e.g., "rise from errand disciple to sect elder and publicly vindicate the parental case", "go from undocumented migrant worker to running three fur-trade companies and personally putting the ex-husband in prison"). Do NOT use vague words like "grow stronger" or "take revenge" — write a concrete state an outside observer can check "achieved / not achieved". This Book Objective is the root of the full-book OKR outline; volume_map will decompose it per volume below.
+
 === SECTION: volume_map ===
 
-Prose volume map, **5 sections + 1 closing rhythm paragraph**. **Critical requirement: stay at volume-level prose only**. No chapter-level task assignment.
+Prose volume map, **5 sections + 1 closing rhythm paragraph**. **Critical requirement: stay at volume-level prose only** — specify each volume's theme, emotional curve, cross-volume hooks, character stage goals, and volume-end irreversible changes. **Do NOT prescribe chapter-level tasks** (no "chapter 17 sends him home"). Chapter planning is the Phase 3 planner's job; the architect builds the skeleton, not the chapter list.
 
 ## 01_Volume_Themes_and_Emotional_Curves
-How many volumes? Each volume's theme in one sentence; each volume's emotional curve as a paragraph.
+How many volumes? Each volume's theme in one sentence; each volume's emotional curve as a paragraph (where pressured, where rewarding, where cold, where warm). Not mechanical rotation.
 
-## 02_Cross_Volume_Hooks_and_Payoff_Promises
-Volume 1 plants hook A, paid off in volume N; volume 2 plants hook B, paid off in volume M. Prose, not tables. **Stay at volume-level**.
+## 02_Cross_Volume_Hooks_and_Payoff_Promises (cover BOTH foreground and background layers)
+Volume 1 plants hook A, paid off in volume N; volume 2 plants hook B, paid off in volume M. Prose, not tables. **Stay at volume-level** (e.g., "the origin mystery planted in volume 1 pays off in volume 3"); do not specify chapter numbers.
 
-## 03_Character_Stage_Goals
-Protagonist's state at end of vol 1, vol 2, ... Supporting characters' stage changes. Stage goals only — full character arc lives in roles.
+**Hooks must cover BOTH foreground and background layers** (matching the two-layer story established in story_frame.02):
+- Foreground hooks: short-range arc-level hooks (case mystery, opponent identity, resource grab), paid off within 1-2 volumes
+- Background hooks: full-book main-line hooks (ultimate truth, origin, systemic secret), paid off near the finale. The 3-7 load-bearing ones are core_hook=true
+
+**If this paragraph only carries foreground hooks with no background seeds, you have lost the book's forward pull axis. Add them.**
+
+## 03_Per_Volume_OKRs (Objective + 3 Key Results)
+Recursive OKR outline that decomposes the Book Objective (root O set at the end of story_frame.04): every volume must explicitly state:
+- **Objective (volume-level goal)**: a **verifiable state** the protagonist must reach by volume end, one sentence, logically chained to the Book Objective (e.g., if Book O = "become sect elder and vindicate the parental case", then Vol 1 O = "move from errand disciple into the registered disciple roster and recover the first lead pointing to the truth")
+- **Key Results (3 items, quantifiable / observable)**: three concrete sub-achievements whose completion can be checked by an outside observer (e.g., KR1 = "take over the pharmacy garden steward seat", KR2 = "lock in a stable alliance with Lingan Peak", KR3 = "uncover the first half-page fragment of the parental case file"). No vague KRs like "gets stronger" / "matures".
+
+Supporting characters' stage changes (master dies end of vol 2, opponent breaks bad in vol 3) go as notes under the relevant KR. Stage only — full arc lives in roles. **The 3 KRs per volume are the direct input for the planner: once it sees 3 KRs for a volume, it paces chapter tasks at roughly one KR advanced every 3-5 chapters.**
 
 ## 04_Volume_End_Mandatory_Changes
-Each volume's last chapter must contain an irreversible event. Prose, one paragraph per volume.
+Each volume's last chapter must contain an irreversible event. Prose, one paragraph per volume. **Write what must happen, not which chapter**.
 
 ## 05_Rhythm_Principles (concrete + universal)
-**Single home for rhythm principles — no separate rhythm_principles section.** 6 rhythm principles. **At least 3 must be concretized for this book**; the rest may stay as universal rules.
-
-### Golden First Three Chapters Rule
-- Chapter 1: throw the core conflict immediately; no large background dump
-- Chapter 2: show the core edge / ability / leverage that answers Chapter 1's pressure
-- Chapter 3: establish the first concrete short-term goal that gives readers a reason to continue
+**This is the single home for rhythm principles — no separate rhythm_principles section exists.** Output 6 rhythm principles. **At least 3 must be concretized for this book** (e.g., "every 5 chapters in the first 30, hit one small payoff"); the rest may stay as universal rules (e.g., "no deus ex machina", "plant the foreshadow 3-5 chapters before the climax"). A mix of concrete + universal is valid. Bad: "rhythm must balance tension and release". Good: "every 5 chapters in the first 30 carries a small payoff landing in the last 300 chars of the chapter". Cover (order flexible, substitutions of equal weight are allowed): (1) climax spacing, (2) breath frequency, (3) hook density, (4) information release pacing, (5) payoff rhythm, (6) relationship advancement — each 2-3 sentences.
 
 === SECTION: roles ===
 
-One-file-per-character prose. **The protagonist card is the single source of truth for the protagonist's full character arc** — story_frame no longer carries it, and writer/planner both read it here.
+One-file-per-character prose. **The protagonist card is the single source of truth for the protagonist's arc** — story_frame no longer carries it, and writer/planner both read it here.
 
 ---ROLE---
 tier: major
 name: <character name>
 ---CONTENT---
 ## Core_Tags
-(3-5 tags + one sentence on why)
+(3-5 tags + one sentence on why those tags)
 
 ## Contrast_Detail
-(1-2 concrete details that contradict the core tags.)
+(1-2 concrete details that contradict the core tags — "ice-cold killer but leaves fish bones for stray cats". Contrast detail is the formula for character dimensionality.)
 
 ## Back_Story
-(Prose paragraph — how this person became who they are.)
+(Prose paragraph — how this person became who they are. Key past only, keep it lean.)
 
 ## Protagonist_Arc (start → end → cost)
-**Mandatory for the protagonist; optional for other majors with substantial arcs.** Internal displacement, not just growth.
+**Mandatory for the protagonist; optional for other majors with substantial arcs.** Where they start (identity, situation, core flaw, initial desire); where they land (who they become, what they gain or lose); the irreversible cost they pay for that landing. Show internal displacement, not just growth. This section absorbs what used to live in story_frame.02_Protagonist_Arc.
 
 ## Current_State (initial state at chapter 0)
-(Character-only: initial hooks go in pending_hooks start_chapter=0 rows; environment/era anchors weave into story_frame.)
+(Where they are at chapter 0, what's on their mind, most recent worry. **Character-only**: initial hooks go in pending_hooks start_chapter=0 rows; environment / era anchors (when the genre has a real year) are woven into story_frame's world-tonal-ground paragraph. No separate current_state section is produced.)
 
 ## Relationship_Network
-(With protagonist, with other majors. One line each.)
+(With protagonist, with other major characters. One line each. Relationships are dynamic, not labels.)
 
 ## Inner_Driver
 (What they want, why, what they're willing to pay.)
 
 ## Growth_Arc
-(Internal displacement across the book.)
+(Internal displacement across the book. Can be short for non-protagonists.)
 
 ---ROLE---
 tier: major
@@ -378,19 +403,19 @@ name: <next major>
 ---CONTENT---
 ...
 
-(Aim for 2-3 majors + 2-3 supporting majors. Quality over quantity.)
+(Aim for 2-3 majors + 2-3 supporting majors. Quality over quantity — do not pad.)
 
 ---ROLE---
 tier: minor
 name: <minor name>
 ---CONTENT---
-(Simplified: Core_Tags / Contrast_Detail / Current_State / Relationship_to_Protagonist only, 1-2 lines each.)
+(Simplified: only 4 sections — Core_Tags / Contrast_Detail / Current_State / Relationship_to_Protagonist, 1-2 lines each.)
 
 (3-5 minors.)
 
 === SECTION: book_rules ===
 
-**Output ONLY the YAML frontmatter block — zero prose.** All narrative guidance moved into story_frame.03_World_Tonal_Ground.
+**Output ONLY the YAML frontmatter block — zero prose.** All narrative guidance (perspective, book-specific rules, core conflict driver) has moved into story_frame.03_World_Tonal_Ground. Do not repeat it here.
 \`\`\`
 ---
 version: "1.0"
@@ -415,15 +440,19 @@ enableFullCastTracking: false
 
 === SECTION: pending_hooks ===
 
-Initial hook pool (Markdown table, 8-column base):
-| hook_id | start_chapter | type | status | last_advanced_chapter | expected_payoff | payoff_timing | notes |
+Initial hook pool (Markdown table), Phase 7 extended columns:
+| hook_id | start_chapter | type | status | last_advanced_chapter | expected_payoff | payoff_timing | depends_on | pays_off_in_arc | core_hook | half_life | notes |
 
 Rules:
 - Column 5 is a pure chapter number, not narrative description
 - At book creation all planned hooks have last_advanced_chapter = 0
 - Column 7 must be: immediate / near-term / mid-arc / slow-burn / endgame
+- Column 8 (depends_on): upstream hook ids that must be planted / paid off before this one fires, formatted [H003, H007]; write "none" if no upstream
+- Column 9 (pays_off_in_arc): free-form prose on where this hook is scheduled to pay off (e.g. "mid of volume 2", "right before the finale"). NOT parsed into chapter numbers
+- Column 10 (core_hook): true / false. Core hooks are main-line load-bearing (central mystery, identity, key promise). A book typically has 3-7 cores; everything else is false
+- Column 11 (half_life): optional integer chapters. If blank, derived from payoff_timing (immediate/near-term = 10, mid-arc = 30, slow-burn/endgame = 80)
 - Put initial signal text in notes, not column 5
-- **Initial world / alliance state**: any load-bearing initial condition can be seeded as a start_chapter=0 row with a notes tag indicating its initial-state nature
+- **Initial world / alliance state**: any load-bearing initial condition ("protagonist carries the father's notebook", "the regime already watches the harbor") can be seeded as a start_chapter=0 row with a note-column tag indicating its initial-state nature.
 
 ## Final emphasis
 - Fit ${book.platform} platform taste and ${gp.name} genre traits
@@ -431,22 +460,156 @@ Rules:
 - Hooks planted with payoff promises; supporting characters have independent motivation
 - **story_frame / volume_map / roles must be prose density — no bullet-list degradation**
 - **book_rules is YAML only — no prose body**
-- **Do NOT emit rhythm_principles or current_state as separate sections** — rhythm principles live in the last paragraph of volume_map; character initial status goes in roles.Current_State; initial hooks go in pending_hooks (start_chapter=0 rows); environment/era anchors (only when the genre has a real year) are woven into story_frame`;
+- **Do NOT emit rhythm_principles or current_state as separate sections** — rhythm principles live in the last paragraph of volume_map; character initial status goes in roles.Current_State; initial hooks go in pending_hooks (start_chapter=0 rows); environment / era anchors (only when the genre has a real year) are woven into story_frame's world-tonal-ground paragraph
+- **pending_hooks table MUST carry Phase 7 extended columns — depends_on spells out the causal chain, pays_off_in_arc locks the approximate payoff location, core_hook marks main-line load-bearing hooks (3-7 per book), half_life only on priority hooks**
+
+## Hard completeness check (read before generating)
+You MUST emit all **5 SECTION blocks in order**: story_frame → volume_map → roles → book_rules → pending_hooks. Do NOT stop after story_frame or volume_map just because they ran long. Even if roles lists only 3 characters, book_rules is a tiny YAML block, and pending_hooks has only 3 rows, all five must appear. The output is only considered delivered after the last row of pending_hooks is written.`;
+    }
+    // -------------------------------------------------------------------------
+    // Parsing
+    // -------------------------------------------------------------------------
+    parseSections(content, language) {
+        const parsedSections = new Map();
+        const sectionPattern = /^\s*===\s*SECTION\s*[：:]\s*([^\n=]+?)\s*===\s*$/gim;
+        const matches = [...content.matchAll(sectionPattern)];
+        for (let i = 0; i < matches.length; i++) {
+            const match = matches[i];
+            const rawName = match[1] ?? "";
+            const start = (match.index ?? 0) + match[0].length;
+            const end = matches[i + 1]?.index ?? content.length;
+            const normalizedName = this.normalizeSectionName(rawName);
+            parsedSections.set(normalizedName, content.slice(start, end).trim());
+        }
+        // Phase 5 new sections take precedence.
+        const storyFrame = parsedSections.get("story_frame") ?? "";
+        const volumeMap = parsedSections.get("volume_map") ?? "";
+        const rhythmPrinciples = parsedSections.get("rhythm_principles") ?? "";
+        const rolesRaw = parsedSections.get("roles") ?? "";
+        // Legacy sections (still produced for back-compat where needed).
+        // If the model used old section names we still accept them.
+        const legacyStoryBible = parsedSections.get("story_bible") ?? "";
+        const legacyVolumeOutline = parsedSections.get("volume_outline") ?? "";
+        const bookRules = parsedSections.get("book_rules");
+        // Phase 5 consolidation: current_state is no longer a required section.
+        // Legacy books (v12 / Phase 5 initial / pre-revert) and import/fanfic
+        // regenerations may still produce it — accept the value when present,
+        // fall through to empty seed when absent (consolidator will populate at
+        // runtime). Era/setting anchors that used to motivate a separate
+        // current_state block now live naturally inside story_frame.世界观底色
+        // for genres that have a real-world year anchor; other genres (修仙/玄幻/
+        // 系统文) omit them entirely.
+        const currentStateLegacy = parsedSections.get("current_state") ?? "";
+        const pendingHooksRaw = parsedSections.get("pending_hooks");
+        // 5-section required contract: story_frame (or legacy story_bible),
+        // volume_map (or legacy volume_outline), roles, book_rules, pending_hooks.
+        //
+        // Backward compat: v12 outputs used story_bible/volume_outline and
+        // embedded character data inside story_bible — they had no roles block.
+        // When the model uses ONLY legacy section names, we accept an empty roles
+        // list (consolidator/readers fall back to the character_matrix shim).
+        // When the new story_frame / volume_map names are used we require roles.
+        const usingLegacyOutlineNames = !storyFrame && !volumeMap
+            && (legacyStoryBible.length > 0 || legacyVolumeOutline.length > 0);
+        const missing = [];
+        const effectiveStoryFrame = storyFrame || legacyStoryBible;
+        const effectiveVolumeMap = volumeMap || legacyVolumeOutline;
+        if (!effectiveStoryFrame)
+            missing.push("story_frame");
+        if (!effectiveVolumeMap)
+            missing.push("volume_map");
+        if (!rolesRaw.trim() && !usingLegacyOutlineNames)
+            missing.push("roles");
+        if (!bookRules)
+            missing.push("book_rules");
+        if (!pendingHooksRaw)
+            missing.push("pending_hooks");
+        if (missing.length > 0) {
+            throw new Error(`Architect output missing required section${missing.length > 1 ? "s" : ""}: ${missing.join(", ")}`);
+        }
+        const roles = this.parseRoles(rolesRaw);
+        const pendingHooks = this.normalizePendingHooksSection(this.stripTrailingAssistantCoda(pendingHooksRaw), effectiveVolumeMap);
+        // Synthesize legacy-facing content from new prose (so back-compat callers
+        // still receive real content instead of empty strings).
+        const storyBible = legacyStoryBible || this.buildStoryBibleShim(effectiveStoryFrame, language);
+        const volumeOutline = legacyVolumeOutline || effectiveVolumeMap;
+        return {
+            storyBible,
+            volumeOutline,
+            bookRules: bookRules,
+            // currentState: empty string when architect no longer emits the section;
+            // writeFoundationFiles seeds current_state.md with a placeholder so
+            // consolidator / state-bootstrap readers find a valid file on first boot.
+            currentState: currentStateLegacy,
+            pendingHooks,
+            storyFrame: effectiveStoryFrame,
+            volumeMap: effectiveVolumeMap,
+            rhythmPrinciples,
+            roles,
+        };
     }
     /**
-     * Write architect foundation output to disk.
-     *
-     * @param mode
-     *   - "init"（默认）：首次建书。写架构稿 + 初始化所有运行时状态文件
-     *     （current_state / pending_hooks / particle_ledger / subplot_board /
-     *     emotional_arcs）为空模板。
-     *   - "revise"：在已有书上重写架构稿。**只改架构稿相关文件**——outline/ /
-     *     roles/ / 4 个 legacy shim——**完全不动运行时状态文件**。这和
-     *     context-transform 注入给 LLM 的 upgrade hint 承诺"只改架构稿不动已写
-     *     章节"一致；如果在 revise 模式下触动运行时文件，会把 consolidator 累积
-     *     的章节状态、伏笔推进、资源账本等全部重置。
+     * Parse ---ROLE---...---CONTENT---... blocks from the roles section.
+     * Drops malformed entries silently — this is prose the LLM produced,
+     * not machine input.
      */
-    async writeFoundationFiles(bookDir, output, numericalSystem = true, language = "zh", mode = "init") {
+    parseRoles(raw) {
+        if (!raw.trim())
+            return [];
+        const blocks = raw.split(/^---ROLE---$/m).map((chunk) => chunk.trim()).filter(Boolean);
+        const roles = [];
+        for (const block of blocks) {
+            const contentSplit = block.split(/^---CONTENT---$/m);
+            if (contentSplit.length < 2)
+                continue;
+            const headerRaw = contentSplit[0].trim();
+            const content = contentSplit.slice(1).join("\n---CONTENT---\n").trim();
+            const tierMatch = headerRaw.match(/tier\s*[:：]\s*(major|minor|主要|次要)/i);
+            const nameMatch = headerRaw.match(/name\s*[:：]\s*(.+)/i);
+            if (!tierMatch || !nameMatch)
+                continue;
+            const tierValue = tierMatch[1].toLowerCase();
+            const tier = (tierValue === "major" || tierValue === "主要") ? "major" : "minor";
+            const name = nameMatch[1].trim();
+            if (!name || !content)
+                continue;
+            roles.push({ tier, name, content });
+        }
+        return roles;
+    }
+    buildStoryBibleShim(storyFrame, language) {
+        if (language === "en") {
+            return `# Story Bible (compat pointer — deprecated)\n\n> This file is kept for external readers only. The authoritative source is now:\n> - outline/story_frame.md (theme / tonal ground / core conflict / world rules / endgame)\n> - outline/volume_map.md (chapter-granular plot map)\n> - roles/ directory (one-file-per-character sheets)\n\n## Excerpt from story_frame\n\n${storyFrame.slice(0, 2000)}\n`;
+        }
+        return `# 故事圣经（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威来源已迁移至：\n> - outline/story_frame.md（主题 / 基调 / 核心冲突 / 世界铁律 / 终局）\n> - outline/volume_map.md（章级别的分卷地图）\n> - roles/ 文件夹（一人一卡角色档案）\n\n## story_frame 摘录\n\n${storyFrame.slice(0, 2000)}\n`;
+    }
+    buildCharacterMatrixShim(roles, language) {
+        const majorLines = roles.filter((role) => role.tier === "major")
+            .map((role) => `- roles/主要角色/${role.name}.md`);
+        const minorLines = roles.filter((role) => role.tier === "minor")
+            .map((role) => `- roles/次要角色/${role.name}.md`);
+        if (language === "en") {
+            return `# Character Matrix (compat pointer — deprecated)\n\n> This file is kept for external readers only. Authoritative source is now the roles/ directory (one-file-per-character).\n\n## Major characters\n\n${majorLines.join("\n") || "(none)"}\n\n## Minor characters\n\n${minorLines.join("\n") || "(none)"}\n`;
+        }
+        return `# 角色矩阵（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威来源已迁移至 roles/ 文件夹（一人一卡）。\n\n## 主要角色\n\n${majorLines.join("\n") || "（无）"}\n\n## 次要角色\n\n${minorLines.join("\n") || "（无）"}\n`;
+    }
+    buildBookRulesShim(bookRulesBody, language) {
+        const trimmedBody = bookRulesBody.trim();
+        if (language === "en") {
+            const excerpt = trimmedBody
+                ? `\n\n## Narrative guidance excerpt\n\n${trimmedBody}\n`
+                : "";
+            return `# Book Rules (compat pointer — deprecated)\n\n> This file is kept for external readers only. The authoritative YAML frontmatter (protagonist / prohibitions / genreLock / ...) now lives at the top of outline/story_frame.md. readBookRules() prefers that location and only falls back here for books initialized before Phase 5 cleanup #3.${excerpt}`;
+        }
+        const excerpt = trimmedBody
+            ? `\n\n## 叙事指引摘录\n\n${trimmedBody}\n`
+            : "";
+        return `# 本书规则（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威 YAML frontmatter（protagonist / prohibitions / genreLock / ...）已迁移至 outline/story_frame.md 顶部。readBookRules() 优先读那里，只有 Phase 5 cleanup #3 之前的老书才会回退到本文件。${excerpt}`;
+    }
+    // -------------------------------------------------------------------------
+    // File writing
+    // -------------------------------------------------------------------------
+    async writeFoundationFiles(bookDir, output, _numericalSystem = true, language = "zh", mode = "init") {
         const storyDir = join(bookDir, "story");
         const outlineDir = join(storyDir, "outline");
         const rolesDir = join(storyDir, "roles");
@@ -459,84 +622,95 @@ Rules:
             mkdir(rolesMinorDir, { recursive: true }),
         ]);
         const writes = [];
-        const storyFrame = output.storyFrame ?? "";
-        const volumeMap = output.volumeMap ?? "";
+        const storyFrameBody = output.storyFrame ?? output.storyBible;
+        const volumeMap = output.volumeMap ?? output.volumeOutline;
         const rhythmPrinciples = output.rhythmPrinciples ?? "";
         const roles = output.roles ?? [];
-        const isPhase5Output = storyFrame.trim().length > 0;
-        // debug: 让排查时能一眼看出 LLM 按哪套格式输出、落到哪套文件布局。
-        // 如果用户新建书后发现只有 story_bible.md / 没有 outline/，看这行日志能
-        // 确认是 LLM 没按新 prompt 输出（走了 legacy 分支），而不是 writeFoundationFiles
-        // 本身的 bug。
-        this.ctx.logger?.info(`[architect] writeFoundationFiles layout=${isPhase5Output ? "phase5" : "legacy"} ` +
-            `storyFrame=${storyFrame.length}chars volumeMap=${volumeMap.length}chars roles=${roles.length}`);
-        // revise 模式 + LLM 回退 legacy 输出 → 必须抛错，不写任何文件。
-        // 原因：如果走 legacy 分支覆盖 story_bible.md 等 flat 文件，而 outline/
-        // 和 roles/ 保持不变，会让 Phase 5 书进入"outline 新 + shim 老 + roles
-        // 残留"的混乱状态；读取端的 fallback 逻辑会读到互相矛盾的内容。
-        // 抛错让用户立刻感知 LLM 响应异常，而不是默默破坏书的数据完整性。
+        const isPhase5Output = Boolean(output.storyFrame?.trim());
         if (mode === "revise" && !isPhase5Output) {
             throw new Error("Architect revise mode produced legacy-format output (storyFrame empty). " +
-                "This likely means the LLM didn't follow the reviseFrom prompt. " +
-                "The book's architecture files have NOT been modified. " +
-                "Check prompt / model / temperature and try again.");
+                "The book's architecture files have NOT been modified.");
         }
-        // revise 模式下先清空旧 role 文件，再写本次 architect 输出——避免改名 / 删除 /
-        // 合并角色后的旧卡片残留被 readRoleCards 当作有效角色继续注入（见 Bug 3）。
-        // 备份由上游 runner.reviseFoundation 在调用前完成，这里可以安全清空。
-        // init 模式下目录本来就是空的，不需要清。
-        // 放在 if (isPhase5Output) 外面，保证所有 revise 场景都清。
         if (mode === "revise") {
             await rm(rolesMajorDir, { recursive: true, force: true });
             await rm(rolesMinorDir, { recursive: true, force: true });
             await mkdir(rolesMajorDir, { recursive: true });
             await mkdir(rolesMinorDir, { recursive: true });
         }
-        if (isPhase5Output) {
-            // book_rules 的 YAML frontmatter 提取后拼到 story_frame.md 顶部，作为权威位置。
-            const { frontmatter: bookRulesFrontmatter, body: bookRulesBody } = extractYamlFrontmatter(output.bookRules);
-            const storyFrameWithFrontmatter = bookRulesFrontmatter
-                ? `${bookRulesFrontmatter}\n\n${storyFrame.trim()}\n`
-                : storyFrame;
-            // Phase 5 权威文件
-            writes.push(writeFile(join(outlineDir, "story_frame.md"), storyFrameWithFrontmatter, "utf-8"));
-            writes.push(writeFile(join(outlineDir, "volume_map.md"), volumeMap, "utf-8"));
-            if (rhythmPrinciples.trim()) {
-                const rhythmFileName = language === "en" ? "rhythm_principles.md" : "节奏原则.md";
-                writes.push(writeFile(join(outlineDir, rhythmFileName), rhythmPrinciples, "utf-8"));
-            }
-            // 一人一卡
-            for (const role of roles) {
-                const targetDir = role.tier === "major" ? rolesMajorDir : rolesMinorDir;
-                const safeName = role.name.replace(/[/\\:*?"<>|]/g, "_").trim();
-                if (!safeName)
-                    continue;
-                writes.push(writeFile(join(targetDir, `${safeName}.md`), role.content, "utf-8"));
-            }
-            // Legacy shim 文件
-            writes.push(writeFile(join(storyDir, "story_bible.md"), this.buildStoryBibleShim(storyFrameWithFrontmatter, language), "utf-8"));
-            writes.push(writeFile(join(storyDir, "volume_outline.md"), volumeMap, "utf-8"));
-            writes.push(writeFile(join(storyDir, "character_matrix.md"), this.buildCharacterMatrixShim(roles, language), "utf-8"));
-            writes.push(writeFile(join(storyDir, "book_rules.md"), this.buildBookRulesShim(bookRulesBody, language), "utf-8"));
-        }
-        else {
-            // Legacy 输出路径（仅 init 模式——revise + legacy 已在上面抛错）：
-            // LLM 还按老 prompt 输出 story_bible / volume_outline，走 Phase 4 落盘方式。
+        if (!isPhase5Output) {
             writes.push(writeFile(join(storyDir, "story_bible.md"), output.storyBible, "utf-8"));
             writes.push(writeFile(join(storyDir, "volume_outline.md"), output.volumeOutline, "utf-8"));
             writes.push(writeFile(join(storyDir, "book_rules.md"), output.bookRules, "utf-8"));
             writes.push(writeFile(join(storyDir, "character_matrix.md"), language === "en"
                 ? "# Character Matrix\n\n<!-- One ## section per character. Add new characters as new ## blocks. -->\n"
                 : "# 角色矩阵\n\n<!-- 每个角色一个 ## 块，新角色追加新 ## 即可。 -->\n", "utf-8"));
+            if (mode === "init") {
+                const currentStateSeed = output.currentState?.trim()
+                    ? output.currentState
+                    : (language === "en"
+                        ? "# Current State\n\n> Seeded at book creation. Runtime state is appended by the consolidator after each chapter.\n"
+                        : "# 当前状态\n\n> 建书时占位。运行时每章之后由 consolidator 追加最新状态。\n");
+                writes.push(writeFile(join(storyDir, "current_state.md"), currentStateSeed, "utf-8"));
+                writes.push(writeFile(join(storyDir, "pending_hooks.md"), output.pendingHooks, "utf-8"));
+                writes.push(writeFile(join(storyDir, "emotional_arcs.md"), language === "en"
+                    ? "# Emotional Arcs\n\n| Character | Chapter | Emotional State | Trigger Event | Intensity (1-10) | Arc Direction |\n| --- | --- | --- | --- | --- | --- |\n"
+                    : "# 情感弧线\n\n| 角色 | 章节 | 情绪状态 | 触发事件 | 强度(1-10) | 弧线方向 |\n|------|------|----------|----------|------------|----------|\n", "utf-8"));
+            }
+            await Promise.all(writes);
+            return;
+        }
+        // Cleanup #3: book_rules YAML frontmatter is now the authoritative
+        // schema for structured fields (protagonist, prohibitions, …). We prepend
+        // it to story_frame.md so readers have one canonical place to look.
+        // book_rules.md becomes a compat shim.
+        const { frontmatter: bookRulesFrontmatter, body: bookRulesBody } = extractYamlFrontmatter(output.bookRules);
+        const storyFrame = bookRulesFrontmatter
+            ? `${bookRulesFrontmatter}\n\n${storyFrameBody.trim()}\n`
+            : storyFrameBody;
+        // Phase 5 primary prose files
+        writes.push(writeFile(join(outlineDir, "story_frame.md"), storyFrame, "utf-8"));
+        writes.push(writeFile(join(outlineDir, "volume_map.md"), volumeMap, "utf-8"));
+        // Phase 5 consolidation: rhythm principles live inside the last paragraph
+        // of volume_map. A separate 节奏原则.md / rhythm_principles.md file is only
+        // written when the architect happened to produce a standalone block (legacy
+        // 7-section output / foundation-reviewer round-trips that still split it
+        // out). Skipping the empty write avoids 0-byte files that mislead the UI
+        // and fight against the "no duplication" rule — readers who need the rhythm
+        // content already pull it from volume_map's closing paragraph.
+        if (rhythmPrinciples.trim()) {
+            const rhythmFileName = language === "en" ? "rhythm_principles.md" : "节奏原则.md";
+            writes.push(writeFile(join(outlineDir, rhythmFileName), rhythmPrinciples, "utf-8"));
+        }
+        // Roles — one file per character
+        for (const role of roles) {
+            const targetDir = role.tier === "major" ? rolesMajorDir : rolesMinorDir;
+            const safeName = role.name.replace(/[/\\:*?"<>|]/g, "_").trim();
+            if (!safeName)
+                continue;
+            writes.push(writeFile(join(targetDir, `${safeName}.md`), role.content, "utf-8"));
         }
-        // 运行时状态文件——**只在 init 模式写**。revise 模式下这些文件已经存在且
-        // 被 consolidator 累积了章节状态（伏笔进度、角色位置、资源账本、情感曲线
-        // 等），重写会把已写章节的真实状态全部清零，违反 context-transform 里给
-        // LLM 的承诺"升级只改架构稿，不动已写的章节"（见 Bug 1）。
+        // Compat shims — these are pointer files, not authoritative content.
+        writes.push(writeFile(join(storyDir, "story_bible.md"), this.buildStoryBibleShim(storyFrame, language), "utf-8"));
+        writes.push(writeFile(join(storyDir, "character_matrix.md"), this.buildCharacterMatrixShim(roles, language), "utf-8"));
+        // Cleanup #1: volume_outline.md mirror removed. All readers now resolve
+        // through readVolumeMap() in utils/outline-paths.ts, which prefers
+        // outline/volume_map.md and falls back to legacy volume_outline.md for
+        // books initialized before Phase 5.
+        // book_rules.md is now a compat shim — the authoritative YAML
+        // frontmatter lives on story_frame.md (cleanup #3). readBookRules()
+        // prefers story_frame.md but still falls back here for older books.
+        writes.push(writeFile(join(storyDir, "book_rules.md"), this.buildBookRulesShim(bookRulesBody, language), "utf-8"));
+        // Runtime state files.
+        // Phase 5 consolidation: the architect no longer emits a current_state
+        // section (only 3 genres — 港综同人/年代文/都市重生 — benefit from a
+        // separate era anchor, and those fold naturally into story_frame.世界观底色).
+        // We still write current_state.md with a seed placeholder so
+        // isCompleteBookDirectory() sees it on first boot and the runtime
+        // consolidator has a file to append each chapter's state into.
+        // Per-character state lives in roles/*.Current_State; initial hook rows
+        // live in pending_hooks with start_chapter=0. Legacy books / imports that
+        // still produced the section keep their content as-is.
         if (mode === "init") {
-            // current_state.md — 架构师不再产出结构化初始状态，给占位 seed；运行时由
-            // consolidator 每章追加。如果 output 里带了内容（legacy 输出或 reviser
-            // 生成），直接用。
             const currentStateSeed = output.currentState?.trim()
                 ? output.currentState
                 : (language === "en"
@@ -544,25 +718,22 @@ Rules:
                     : "# 当前状态\n\n> 建书时占位。运行时每章之后由 consolidator 追加最新状态。每个角色的初始状态详见 roles/*.当前现状；承重的初始世界设定见 pending_hooks 里 startChapter=0 的行。\n");
             writes.push(writeFile(join(storyDir, "current_state.md"), currentStateSeed, "utf-8"));
             writes.push(writeFile(join(storyDir, "pending_hooks.md"), output.pendingHooks, "utf-8"));
-            // 运行时 append log 文件，下游 state-validator / consolidator 依赖这些存在。
-            if (numericalSystem) {
-                writes.push(writeFile(join(storyDir, "particle_ledger.md"), language === "en"
-                    ? "# Resource Ledger\n\n| Chapter | Opening Value | Source | Integrity | Delta | Closing Value | Evidence |\n| --- | --- | --- | --- | --- | --- | --- |\n| 0 | 0 | Initialization | - | 0 | 0 | Initial book state |\n"
-                    : "# 资源账本\n\n| 章节 | 期初值 | 来源 | 完整度 | 增量 | 期末值 | 依据 |\n|------|--------|------|--------|------|--------|------|\n| 0 | 0 | 初始化 | - | 0 | 0 | 开书初始 |\n", "utf-8"));
-            }
-            writes.push(writeFile(join(storyDir, "subplot_board.md"), language === "en"
-                ? "# Subplot Board\n\n| Subplot ID | Subplot | Related Characters | Start Chapter | Last Active Chapter | Chapters Since | Status | Progress Summary | Payoff ETA |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- |\n"
-                : "# 支线进度板\n\n| 支线ID | 支线名 | 相关角色 | 起始章 | 最近活跃章 | 距今章数 | 状态 | 进度概述 | 回收ETA |\n|--------|--------|----------|--------|------------|----------|------|----------|---------|\n", "utf-8"));
             writes.push(writeFile(join(storyDir, "emotional_arcs.md"), language === "en"
                 ? "# Emotional Arcs\n\n| Character | Chapter | Emotional State | Trigger Event | Intensity (1-10) | Arc Direction |\n| --- | --- | --- | --- | --- | --- |\n"
                 : "# 情感弧线\n\n| 角色 | 章节 | 情绪状态 | 触发事件 | 强度(1-10) | 弧线方向 |\n|------|------|----------|----------|------------|----------|\n", "utf-8"));
         }
+        // Cleanup #2 (Option B): particle_ledger.md / subplot_board.md /
+        // chapter_summaries.md are pure runtime logs appended by the writer's
+        // settlement phase. The architect no longer seeds them here — mixing a
+        // static "setting" seed with a runtime "append log" was the dual-purpose
+        // mess that prompted the cleanup. If they don't exist yet, downstream
+        // readers see the placeholder and the first chapter settlement creates
+        // them naturally. The `_numericalSystem` parameter is kept for API
+        // compatibility with existing callers.
         await Promise.all(writes);
     }
     /**
      * Reverse-engineer foundation from existing chapters.
-     * Reads all chapters as a single text block and asks LLM to extract story_bible,
-     * volume_outline, book_rules, current_state, and pending_hooks.
      */
     async generateFoundationFromImport(book, chaptersText, externalContext, reviewFeedback, options) {
         const { profile: gp, body: genreBody } = await readGenreProfile(this.ctx.projectRoot, book.genre);
@@ -575,306 +746,73 @@ Rules:
             : "";
         const numericalBlock = gp.numericalSystem
             ? (resolvedLanguage === "en"
-                ? `- The story uses a trackable numerical/resource system
-- Define numericalSystemOverrides in book_rules (hardCap, resourceTypes)`
-                : `- 有明确的数值/资源体系可追踪
-- 在 book_rules 中定义 numericalSystemOverrides（hardCap、resourceTypes）`)
+                ? "- The story uses a trackable numerical/resource system"
+                : "- 有明确的数值/资源体系可追踪")
             : (resolvedLanguage === "en"
-                ? "- This genre has no explicit numerical system and does not need a resource ledger"
-                : "- 本题材无数值系统，不需要资源账本");
-        const powerBlock = gp.powerScaling
-            ? (resolvedLanguage === "en" ? "- The story has an explicit power-scaling ladder" : "- 有明确的战力等级体系")
-            : "";
-        const eraBlock = gp.eraResearch
-            ? (resolvedLanguage === "en"
-                ? "- The story needs era/historical grounding (set eraConstraints in book_rules)"
-                : "- 需要年代考据支撑（在 book_rules 中设置 eraConstraints）")
-            : "";
-        const storyBiblePrompt = resolvedLanguage === "en"
-            ? `Extract from the source text and organize with structured second-level headings:
-## 01_Worldview
-Extracted world setting, core rules, and frame
-
-## 02_Protagonist
-Inferred protagonist setup (identity / advantage / personality core / behavioral boundaries)
-
-## 03_Factions_and_Characters
-Factions and important supporting characters that appear in the source text
-
-## 04_Geography_and_Environment
-Locations, environments, and scene traits drawn from the source text
-
-## 05_Title_and_Blurb
-Keep the original title "${book.title}" and generate a matching blurb from the source text`
-            : `从正文中提取，用结构化二级标题组织：
-## 01_世界观
-从正文中提取的世界观设定、核心规则体系
-
-## 02_主角
-从正文中推断的主角设定（身份/金手指/性格底色/行为边界）
-
-## 03_势力与人物
-从正文中出现的势力分布、重要配角（每人：名字、身份、动机、与主角关系、独立目标）
-
-## 04_地理与环境
-从正文中出现的地图/场景设定、环境特色
-
-## 05_书名与简介
-保留原书名"${book.title}"，根据正文内容生成简介`;
-        const volumeOutlinePrompt = resolvedLanguage === "en"
-            ? `Infer the volume plan from existing text:
-- Existing chapters: review the actual structure already present
-- Future projection: predict later directions from active hooks and plot momentum
-For each volume include: title, chapter range, core conflict, and key turning points`
-            : `基于已有正文反推卷纲：
-- 已有章节部分：根据实际内容回顾每卷的结构
-- 后续预测部分：基于已有伏笔和剧情走向预测未来方向
-每卷包含：卷名、章节范围、核心冲突、关键转折`;
-        const bookRulesPrompt = resolvedLanguage === "en"
-            ? `Infer book_rules.md as YAML frontmatter plus narrative guidance from character behavior in the source text:
-\`\`\`
----
-version: "1.0"
-protagonist:
-  name: (extract protagonist name from the text)
-  personalityLock: [(infer 3-5 personality keywords from behavior)]
-  behavioralConstraints: [(infer 3-5 behavioral constraints from behavior)]
-genreLock:
-  primary: ${book.genre}
-  forbidden: [(2-3 forbidden style intrusions)]
-${gp.numericalSystem ? `numericalSystemOverrides:
-  hardCap: (infer from the text)
-  resourceTypes: [(extract core resource types from the text)]` : ""}
-prohibitions:
-  - (infer 3-5 book-specific prohibitions from the text)
-chapterTypesOverride: []
-fatigueWordsOverride: []
-additionalAuditDimensions: []
-enableFullCastTracking: false
----
-
-## Narrative Perspective
-(Infer the narrative perspective and style from the text)
-
-## Core Conflict Driver
-(Infer the book's core conflict and propulsion from the text)
-\`\`\``
-            : `从正文中角色行为反推 book_rules.md 格式的 YAML frontmatter + 叙事指导：
-\`\`\`
----
-version: "1.0"
-protagonist:
-  name: (从正文提取主角名)
-  personalityLock: [(从行为推断3-5个性格关键词)]
-  behavioralConstraints: [(从行为推断3-5条行为约束)]
-genreLock:
-  primary: ${book.genre}
-  forbidden: [(2-3种禁止混入的文风)]
-${gp.numericalSystem ? `numericalSystemOverrides:
-  hardCap: (从正文推断)
-  resourceTypes: [(从正文提取核心资源类型)]` : ""}
-prohibitions:
-  - (从正文推断3-5条本书禁忌)
-chapterTypesOverride: []
-fatigueWordsOverride: []
-additionalAuditDimensions: []
-enableFullCastTracking: false
----
-
-## 叙事视角
-(从正文推断本书叙事视角和风格)
-
-## 核心冲突驱动
-(从正文推断本书的核心矛盾和驱动力)
-\`\`\``;
-        const currentStatePrompt = resolvedLanguage === "en"
-            ? `Reflect the state at the end of the latest chapter:
-| Field | Value |
-| --- | --- |
-| Current Chapter | (latest chapter number) |
-| Current Location | (location at the end of the latest chapter) |
-| Protagonist State | (state at the end of the latest chapter) |
-| Current Goal | (current goal) |
-| Current Constraint | (current constraint) |
-| Current Alliances | (current alliances / opposition) |
-| Current Conflict | (current conflict) |`
-            : `反映最后一章结束时的状态卡：
-| 字段 | 值 |
-|------|-----|
-| 当前章节 | (最后一章章节号) |
-| 当前位置 | (最后一章结束时的位置) |
-| 主角状态 | (最后一章结束时的状态) |
-| 当前目标 | (当前目标) |
-| 当前限制 | (当前限制) |
-| 当前敌我 | (当前敌我关系) |
-| 当前冲突 | (当前冲突) |`;
-        const pendingHooksPrompt = resolvedLanguage === "en"
-            ? `Identify all active hooks from the source text (Markdown table):
-| hook_id | start_chapter | type | status | latest_progress | expected_payoff | payoff_timing | notes |`
-            : `从正文中识别的所有伏笔（Markdown表格）：
-| hook_id | 起始章节 | 类型 | 状态 | 最近推进 | 预期回收 | 回收节奏 | 备注 |`;
-        const keyPrinciplesPrompt = resolvedLanguage === "en"
-            ? `## Key Principles
-
-1. Derive everything from the source text; do not invent unsupported settings
-2. Hook extraction must be complete: unresolved clues, hints, and foreshadowing all count
-3. Character inference must come from dialogue and behavior, not assumption
-4. Accuracy first; detailed is better than missing crucial information
-${numericalBlock}
-${powerBlock}
-${eraBlock}`
-            : `## 关键原则
-
-1. 一切从正文出发，不要臆造正文中没有的设定
-2. 伏笔识别要完整：悬而未决的线索、暗示、预告都算
-3. 角色推断要准确：从对话和行为推断性格，不要想当然
-4. 准确性优先，宁可详细也不要遗漏
-${numericalBlock}
-${powerBlock}
-${eraBlock}`;
+                ? "- No explicit numerical system"
+                : "- 本题材无数值系统");
         const isSeries = options?.importMode === "series";
-        const continuationDirectiveEn = isSeries
-            ? `## Continuation Direction Requirements (Critical)
-The continuation portion (chapters in volume_outline that have not happened yet) must open up **new narrative space**:
-1. **New conflict dimension**: Do not merely stretch the imported conflict longer. Introduce at least one new conflict vector not yet covered by the source text (new character, new faction, new location, or new time horizon)
-2. **Ignite within 5 chapters**: The first continuation volume must establish a fresh suspense engine within 5 chapters. Do not spend 3 chapters recapping known information
-3. **Scene freshness**: At least 50% of key continuation scenes must happen in locations or situations not already used in the imported chapters
-4. **No repeated meeting rooms**: If the imported chapters end on a meeting/discussion beat, the continuation must restart from action instead of opening another meeting`
-            : `## Continuation Direction
-The volume_outline should naturally extend the existing narrative arc. Continue from where the imported chapters left off — advance existing conflicts, pay off planted hooks, and introduce new complications that arise organically from the current situation. Do not recap known information.`;
-        const continuationDirectiveZh = isSeries
-            ? `## 续写方向要求（关键）
-续写部分（volume_outline 中尚未发生的章节）必须设计**新的叙事空间**：
-1. **新冲突维度**：续写不能只是把导入章节的冲突继续拉长。必须引入至少一个原文未涉及的新冲突方向（新角色、新势力、新地点、新时间跨度）
-2. **5章内引爆**：续写的第一卷必须在前5章内建立新悬念，不允许用3章回顾已知信息
-3. **场景新鲜度**：续写部分至少50%的关键场景发生在导入章节未出现的地点或情境中
-4. **不重复会议**：如果导入章节以会议/讨论结束，续写必须从行动开始，不能再开一轮会`
-            : `## 续写方向
-卷纲应自然延续已有故事线。从导入章节的结尾处接续——推进现有冲突、兑现已埋伏笔、引入从当前局势中有机产生的新变数。不要回顾已知信息。`;
-        const workingModeEn = isSeries
-            ? `## Working Mode
-
-This is not a zero-to-one foundation pass. You must extract durable story truth from the imported chapters **and design a continuation path**. You need to:
-1. Extract worldbuilding, factions, characters, and systems from the source text -> generate story_bible
-2. Infer narrative structure and future arc direction -> generate volume_outline (review existing chapters + design a **new continuation direction**)
-3. Infer protagonist lock, prohibitions, and narrative constraints from character behavior -> generate book_rules
-4. Reflect the latest chapter state -> generate current_state
-5. Extract all active hooks already planted in the text -> generate pending_hooks`
-            : `## Working Mode
-
-This is not a zero-to-one foundation pass. You must extract durable story truth from the imported chapters **and preserve a clean continuation path**. You need to:
-1. Extract worldbuilding, factions, characters, and systems from the source text -> generate story_bible
-2. Infer narrative structure and near-future arc direction -> generate volume_outline (review existing chapters + continue naturally from where the imported chapters stop)
-3. Infer protagonist lock, prohibitions, and narrative constraints from character behavior -> generate book_rules
-4. Reflect the latest chapter state -> generate current_state
-5. Extract all active hooks already planted in the text -> generate pending_hooks`;
-        const workingModeZh = isSeries
-            ? `## 工作模式
-
-这不是从零创建，而是从已有正文中提取和推导，**并设计续写方向**。你需要：
-1. 从正文中提取世界观、势力、角色、力量体系 → 生成 story_bible
-2. 从叙事结构推断卷纲 → 生成 volume_outline（已有章节的回顾 + **续写部分的新方向设计**）
-3. 从角色行为推断主角锁定和禁忌 → 生成 book_rules
-4. 从最新章节状态推断 current_state（反映最后一章结束时的状态）
-5. 从正文中识别已埋伏笔 → 生成 pending_hooks`
-            : `## 工作模式
-
-这不是从零创建，而是从已有正文中提取和推导，**并为自然续写保留清晰延续路径**。你需要：
-1. 从正文中提取世界观、势力、角色、力量体系 → 生成 story_bible
-2. 从叙事结构推断卷纲 → 生成 volume_outline（回顾已有章节，并从导入章节结束处自然接续）
-3. 从角色行为推断主角锁定和禁忌 → 生成 book_rules
-4. 从最新章节状态推断 current_state（反映最后一章结束时的状态）
-5. 从正文中识别已埋伏笔 → 生成 pending_hooks`;
+        const continuationDirective = resolvedLanguage === "en"
+            ? (isSeries
+                ? `## Continuation Direction Requirements
+The continuation portion must open up new narrative space — new conflict vector, new location, new time horizon. Ignite within 5 chapters; at least 50% fresh scenes.`
+                : `## Continuation Direction
+Naturally extend the existing arc. Advance existing conflicts, pay off planted hooks, introduce new complications organically.`)
+            : (isSeries
+                ? `## 续写方向要求
+续写必须引入新叙事空间——新冲突、新地点、新时间。5章内引爆，50%以上场景新鲜。`
+                : `## 续写方向
+自然延续已有叙事弧线。推进现有冲突、兑现已埋伏笔、引入有机新变数。`);
         const systemPrompt = resolvedLanguage === "en"
-            ? `You are a professional web-fiction architect. Your task is to reverse-engineer a complete foundation from existing chapters.${contextBlock}
-
-${workingModeEn}
-
-All output sections — story_bible, volume_outline, book_rules, current_state, and pending_hooks — MUST be written in English. Keep the === SECTION: === tags unchanged.
-
-${continuationDirectiveEn}
-${reviewFeedbackBlock}
-## Book Metadata
+            ? `You are a professional novel architect. Reverse-engineer a prose-density foundation from the source chapters and write the continuation path.${contextBlock}${reviewFeedbackBlock}
 
+## Book metadata
 - Title: ${book.title}
 - Platform: ${book.platform}
 - Genre: ${gp.name} (${book.genre})
-- Target Chapters: ${book.targetChapters}
-- Chapter Target Length: ${book.chapterWordCount}
-
-## Genre Profile
+- Target chapters: ${book.targetChapters}
+- Chapter length: ${book.chapterWordCount}
 
+## Genre body
 ${genreBody}
 
-## Output Contract
-
-Generate the following sections. Separate every section with === SECTION: <name> ===:
-
-=== SECTION: story_bible ===
-${storyBiblePrompt}
-
-=== SECTION: volume_outline ===
-${volumeOutlinePrompt}
-
-=== SECTION: book_rules ===
-${bookRulesPrompt}
+${numericalBlock}
 
-=== SECTION: current_state ===
-${currentStatePrompt}
+${continuationDirective}
 
-=== SECTION: pending_hooks ===
-${pendingHooksPrompt}
+## Output contract
+Follow the consolidated 5-section === SECTION: === layout: story_frame, volume_map, roles, book_rules, pending_hooks. Do NOT emit rhythm_principles or current_state — rhythm principles live in the last paragraph of volume_map; character initial status lives in roles.Current_State; initial hooks live in pending_hooks start_chapter=0 rows; era / setting anchors (only when the genre pins to a real year) are woven into story_frame's world-tonal-ground paragraph.
 
-${keyPrinciplesPrompt}`
-            : `你是一个专业的网络小说架构师。你的任务是从已有的小说正文中反向推导完整的基础设定。${contextBlock}
+All prose must be derived from the source package. Do not invent settings. If the package says it is compressed, treat chapter catalog + excerpts as evidence for the foundation; the full chapters will be replayed later for detailed truth files. For volume_map, treat existing chapters as "review" (one paragraph) and continuation as prose chapter-level planning. Hook extraction must be complete for the evidence provided.
 
-${workingModeZh}
-
-${continuationDirectiveZh}
-${reviewFeedbackBlock}
-## 书籍信息
+All output MUST be written in English.`
+            : `你是专业的网络小说架构师。从已有章节中反向推导散文密度的基础设定，同时设计续写路径。${contextBlock}${reviewFeedbackBlock}
 
+## 书籍元信息
 - 标题：${book.title}
 - 平台：${book.platform}
 - 题材：${gp.name}（${book.genre}）
 - 目标章数：${book.targetChapters}章
-- 每章字数：${book.chapterWordCount}字
-
-## 题材特征
 
+## 题材底色
 ${genreBody}
 
-## 生成要求
-
-你需要生成以下内容，每个部分用 === SECTION: <name> === 分隔：
-
-=== SECTION: story_bible ===
-${storyBiblePrompt}
-
-=== SECTION: volume_outline ===
-${volumeOutlinePrompt}
-
-=== SECTION: book_rules ===
-${bookRulesPrompt}
+${numericalBlock}
 
-=== SECTION: current_state ===
-${currentStatePrompt}
+${continuationDirective}
 
-=== SECTION: pending_hooks ===
-${pendingHooksPrompt}
+## 输出契约
+合并后的 5 段 === SECTION: === 结构：story_frame / volume_map / roles / book_rules / pending_hooks。**不要输出 rhythm_principles 或 current_state 两个 section**——节奏原则合并进 volume_map 尾段，角色初始状态合并进 roles.当前现状，初始钩子写在 pending_hooks startChapter=0 行；环境/时代锚（只有年代文 / 历史同人 / 都市重生等真实年份题材需要）织进 story_frame.世界观底色，其他题材直接省略。
 
-${keyPrinciplesPrompt}`;
+所有 prose 必须从资料包中推导，不得臆造。若资料包声明为压缩包，把章节目录和正文摘录当作基础设定证据；完整章节会在后续回放阶段逐章进入 truth files。volume_map 中，已有章节作为"回顾段"（一段散文），续写部分写到章级 prose。伏笔识别以资料包提供的证据为准，尽量完整。`;
         const userMessage = resolvedLanguage === "en"
             ? `Generate the complete foundation for an imported ${gp.name} novel titled "${book.title}". Write everything in English.\n\n${chaptersText}`
-            : `以下是《${book.title}》的全部已有正文，请从中反向推导完整基础设定：\n\n${chaptersText}`;
+            : `以下是《${book.title}》的已有正文资料包，请从中反向推导完整基础设定：\n\n${chaptersText}`;
         const response = await this.chat([
             { role: "system", content: systemPrompt },
-            {
-                role: "user",
-                content: userMessage,
-            },
-        ], { temperature: 0.5, maxTokens: 16384 });
-        return this.parseSections(response.content);
+            { role: "user", content: userMessage },
+        ], { temperature: 0.5 });
+        return this.parseSections(response.content, resolvedLanguage);
     }
     async generateFanficFoundation(book, fanficCanon, fanficMode, reviewFeedback) {
         const { profile: gp, body: genreBody } = await readGenreProfile(this.ctx.projectRoot, book.genre);
@@ -885,75 +823,46 @@ ${keyPrinciplesPrompt}`;
             ooc: "标注角色性格偏离的起点和驱动事件。偏离必须有逻辑驱动。",
             cp: "以配对角色的关系线为主线规划卷纲。每卷必须有关系推进节点。",
         };
-        const systemPrompt = `你是一个专业的同人小说架构师。你的任务是基于原作正典为同人小说生成基础设定。
+        const systemPrompt = `你是专业同人架构师。基于原作正典为同人生成散文密度的基础设定。
 
 ## 同人模式：${fanficMode}
 ${MODE_INSTRUCTIONS[fanficMode]}
 
-## 新时空要求（关键）
-你必须为这本同人设计一个**原创的叙事空间**，而不是复述原作剧情。具体要求：
-1. **明确分岔点**：story_bible 必须标注"本作从原作的哪个节点分岔"，或"本作发生在原作未涉及的什么时空"
-2. **独立核心冲突**：volume_outline 的核心冲突必须是原创的，不是原作情节的翻版。原作角色可以出现，但他们面对的是新问题
-3. **5章内引爆**：volume_outline 的第1卷必须在前5章内建立核心悬念，不允许用3章做铺垫才到引爆点
-4. **场景新鲜度**：至少50%的关键场景发生在原作未出现的地点或情境中
-
+## 新时空要求
+必须为这本同人设计原创叙事空间，不是复述原作剧情：
+1. 明确分岔点——story_frame 必须标注本作从原作的哪个节点分岔
+2. 独立核心冲突——volume_map 的核心冲突必须是原创的
+3. 5章内引爆
+4. 场景新鲜度 ≥ 50%
 ${reviewFeedbackBlock}
 
 ## 原作正典
 ${fanficCanon}
 
-## 题材特征
+## 题材底色
 ${genreBody}
 
-## 关键原则
-1. **不发明主要角色** — 主要角色必须来自原作正典的角色档案
-2. 可以添加原创配角，但必须在 story_bible 中标注为"原创角色"
-3. story_bible 保留原作世界观，标注同人的改动/扩展部分，并明确写出**分岔点**和**新时空设定**
-4. volume_outline 不得复述原作剧情节拍。每卷的核心事件必须是原创的，标注"原创"
-5. book_rules 的 fanficMode 必须设为 "${fanficMode}"
-6. 主角设定来自原作角色档案中的第一个角色（或用户在标题中暗示的角色）
-
-你需要生成以下内容，每个部分用 === SECTION: <name> === 分隔：
-
-=== SECTION: story_bible ===
-世界观（基于原作正典）+ 角色列表（原作角色标注来源，原创角色标注"原创"）
-
-=== SECTION: volume_outline ===
-卷纲规划。每卷标注：卷名、章节范围、核心事件（标注原作/原创）、关系发展节点
+## 输出契约
+严格按合并后的 5 段 === SECTION: === 块输出：story_frame / volume_map / roles / book_rules / pending_hooks。**不要输出 rhythm_principles 或 current_state**：节奏原则合并进 volume_map 尾段；角色初始状态写在 roles.当前现状，初始钩子写在 pending_hooks startChapter=0 行；环境/时代锚（仅当同人的原作/本作锚定真实年份时）织进 story_frame.世界观底色，其他情况省略。
 
-=== SECTION: book_rules ===
-\`\`\`
----
-version: "1.0"
-protagonist:
-  name: (从原作角色中选择)
-  personalityLock: [(从正典角色档案提取)]
-  behavioralConstraints: [(基于原作行为模式)]
-genreLock:
-  primary: ${book.genre}
-  forbidden: []
-fanficMode: "${fanficMode}"
-allowedDeviations: []
-prohibitions:
-  - (3-5条同人特有禁忌)
----
-(叙事视角和风格指导)
-\`\`\`
-
-=== SECTION: current_state ===
-初始状态卡（基于正典起始点）
-
-=== SECTION: pending_hooks ===
-初始伏笔池（从正典关键事件和关系中提取）`;
+- 主要角色必须来自原作正典
+- 可添加原创配角，标注"原创"
+- book_rules 的 fanficMode 必须设为 "${fanficMode}"
+- book_rules 只输出 YAML frontmatter，散文写进 story_frame.世界观底色
+- 主角弧线只写在 roles/主要角色/<主角>.md，不在 story_frame 重复
+- 所有 outline 必须是散文密度`;
         const response = await this.chat([
             { role: "system", content: systemPrompt },
             {
                 role: "user",
                 content: `请为标题为"${book.title}"的${fanficMode}模式同人小说生成基础设定。目标${book.targetChapters}章，每章${book.chapterWordCount}字。`,
             },
-        ], { temperature: 0.7, maxTokens: 16384 });
-        return this.parseSections(response.content);
+        ], { temperature: 0.7 });
+        return this.parseSections(response.content, book.language ?? "zh");
     }
+    // -------------------------------------------------------------------------
+    // Helpers
+    // -------------------------------------------------------------------------
     buildReviewFeedbackBlock(reviewFeedback, language) {
         const trimmed = reviewFeedback?.trim();
         if (!trimmed)
@@ -969,122 +878,6 @@ ${trimmed}\n`;
 
 ${trimmed}\n`;
     }
-    parseSections(content) {
-        const parsedSections = new Map();
-        const sectionPattern = /^\s*===\s*SECTION\s*[：:]\s*([^\n=]+?)\s*===\s*$/gim;
-        const matches = [...content.matchAll(sectionPattern)];
-        for (let i = 0; i < matches.length; i++) {
-            const match = matches[i];
-            const rawName = match[1] ?? "";
-            const start = (match.index ?? 0) + match[0].length;
-            const end = matches[i + 1]?.index ?? content.length;
-            const normalizedName = this.normalizeSectionName(rawName);
-            parsedSections.set(normalizedName, content.slice(start, end).trim());
-        }
-        // Phase 5 新 sections
-        const storyFrame = parsedSections.get("story_frame") ?? "";
-        const volumeMap = parsedSections.get("volume_map") ?? "";
-        const rhythmPrinciples = parsedSections.get("rhythm_principles") ?? "";
-        const rolesRaw = parsedSections.get("roles") ?? "";
-        // Legacy sections — 当 LLM 还按老 prompt 输出时兜底。
-        const legacyStoryBible = parsedSections.get("story_bible") ?? "";
-        const legacyVolumeOutline = parsedSections.get("volume_outline") ?? "";
-        const bookRules = parsedSections.get("book_rules");
-        const currentStateLegacy = parsedSections.get("current_state") ?? "";
-        const pendingHooksRaw = parsedSections.get("pending_hooks");
-        // 用老名字输出且没有 story_frame/volume_map 时，roles 可空（走 legacy shim fallback）。
-        const usingLegacyOutlineNames = !storyFrame && !volumeMap
-            && (legacyStoryBible.length > 0 || legacyVolumeOutline.length > 0);
-        const effectiveStoryFrame = storyFrame || legacyStoryBible;
-        const effectiveVolumeMap = volumeMap || legacyVolumeOutline;
-        const missing = [];
-        if (!effectiveStoryFrame)
-            missing.push("story_frame");
-        if (!effectiveVolumeMap)
-            missing.push("volume_map");
-        if (!rolesRaw.trim() && !usingLegacyOutlineNames)
-            missing.push("roles");
-        if (!bookRules)
-            missing.push("book_rules");
-        if (!pendingHooksRaw)
-            missing.push("pending_hooks");
-        if (missing.length > 0) {
-            throw new Error(`Architect output missing required section${missing.length > 1 ? "s" : ""}: ${missing.join(", ")}`);
-        }
-        const roles = this.parseRoles(rolesRaw);
-        const pendingHooks = this.normalizePendingHooksSection(this.stripTrailingAssistantCoda(pendingHooksRaw));
-        // Shim-facing 老字段：新 prompt 下用 buildStoryBibleShim 生成指针内容；
-        // 老 prompt 下直接用老内容。volumeOutline 也同理。
-        const storyBible = legacyStoryBible || effectiveStoryFrame;
-        const volumeOutline = legacyVolumeOutline || effectiveVolumeMap;
-        return {
-            storyBible,
-            volumeOutline,
-            bookRules: bookRules,
-            // current_state 在 Phase 5 下不是必需 section——writeFoundationFiles 会 seed
-            // 一个占位文件，consolidator 运行时按章追加。
-            currentState: currentStateLegacy,
-            pendingHooks,
-            storyFrame: effectiveStoryFrame,
-            volumeMap: effectiveVolumeMap,
-            rhythmPrinciples,
-            roles,
-        };
-    }
-    /** Parse ---ROLE---...---CONTENT--- 块。畸形块静默丢弃。 */
-    parseRoles(raw) {
-        if (!raw.trim())
-            return [];
-        const blocks = raw.split(/^---ROLE---$/m).map((chunk) => chunk.trim()).filter(Boolean);
-        const roles = [];
-        for (const block of blocks) {
-            const contentSplit = block.split(/^---CONTENT---$/m);
-            if (contentSplit.length < 2)
-                continue;
-            const headerRaw = contentSplit[0].trim();
-            const content = contentSplit.slice(1).join("\n---CONTENT---\n").trim();
-            const tierMatch = headerRaw.match(/tier\s*[:：]\s*(major|minor|主要|次要)/i);
-            const nameMatch = headerRaw.match(/name\s*[:：]\s*(.+)/i);
-            if (!tierMatch || !nameMatch)
-                continue;
-            const tierValue = tierMatch[1].toLowerCase();
-            const tier = (tierValue === "major" || tierValue === "主要") ? "major" : "minor";
-            const name = nameMatch[1].trim();
-            if (!name || !content)
-                continue;
-            roles.push({ tier, name, content });
-        }
-        return roles;
-    }
-    buildStoryBibleShim(storyFrame, language) {
-        if (language === "en") {
-            return `# Story Bible (compat pointer — deprecated)\n\n> This file is kept for external readers only. The authoritative source is now:\n> - outline/story_frame.md (theme / tonal ground / core conflict / world rules / endgame)\n> - outline/volume_map.md (volume-level plot map)\n> - roles/ directory (one-file-per-character sheets)\n\n## Excerpt from story_frame\n\n${storyFrame.slice(0, 2000)}\n`;
-        }
-        return `# 故事圣经（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威来源已迁移至：\n> - outline/story_frame.md（主题 / 基调 / 核心冲突 / 世界铁律 / 终局）\n> - outline/volume_map.md（卷级分卷地图）\n> - roles/ 文件夹（一人一卡角色档案）\n\n## story_frame 摘录\n\n${storyFrame.slice(0, 2000)}\n`;
-    }
-    buildCharacterMatrixShim(roles, language) {
-        const majorLines = roles.filter((role) => role.tier === "major")
-            .map((role) => `- roles/主要角色/${role.name}.md`);
-        const minorLines = roles.filter((role) => role.tier === "minor")
-            .map((role) => `- roles/次要角色/${role.name}.md`);
-        if (language === "en") {
-            return `# Character Matrix (compat pointer — deprecated)\n\n> This file is kept for external readers only. Authoritative source is now the roles/ directory (one-file-per-character).\n\n## Major characters\n\n${majorLines.join("\n") || "(none)"}\n\n## Minor characters\n\n${minorLines.join("\n") || "(none)"}\n`;
-        }
-        return `# 角色矩阵（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威来源已迁移至 roles/ 文件夹（一人一卡）。\n\n## 主要角色\n\n${majorLines.join("\n") || "（无）"}\n\n## 次要角色\n\n${minorLines.join("\n") || "（无）"}\n`;
-    }
-    buildBookRulesShim(bookRulesBody, language) {
-        const trimmedBody = bookRulesBody.trim();
-        if (language === "en") {
-            const excerpt = trimmedBody
-                ? `\n\n## Narrative guidance excerpt\n\n${trimmedBody}\n`
-                : "";
-            return `# Book Rules (compat pointer — deprecated)\n\n> This file is kept for external readers only. The authoritative YAML frontmatter now lives at the top of outline/story_frame.md.${excerpt}`;
-        }
-        const excerpt = trimmedBody
-            ? `\n\n## 叙事指引摘录\n\n${trimmedBody}\n`
-            : "";
-        return `# 本书规则（兼容指针——已废弃）\n\n> 本文件仅为外部读取保留。权威 YAML frontmatter 已迁移至 outline/story_frame.md 顶部。${excerpt}`;
-    }
     normalizeSectionName(name) {
         return name
             .normalize("NFKC")
@@ -1106,7 +899,7 @@ ${trimmed}\n`;
         }
         return lines.slice(0, cutoff).join("\n").trimEnd();
     }
-    normalizePendingHooksSection(section) {
+    normalizePendingHooksSection(section, volumeMapRaw) {
         const rows = section
             .split("\n")
             .map((line) => line.trim())
@@ -1128,19 +921,78 @@ ${trimmed}\n`;
             const seedNote = normalizedProgress === 0 && this.hasNarrativeProgress(rawProgress)
                 ? (language === "zh" ? `初始线索：${rawProgress}` : `initial signal: ${rawProgress}`)
                 : "";
-            const notes = this.mergeHookNotes(row[6] ?? "", seedNote, language);
-            return {
+            const phase7 = row.length >= 12;
+            const phase6 = row.length >= 8;
+            const noteCellIndex = phase7 ? 11 : phase6 ? 7 : 6;
+            const notes = this.mergeHookNotes(row[noteCellIndex] ?? "", seedNote, language);
+            const base = {
                 hookId: row[0] || `hook-${index + 1}`,
                 startChapter: this.parseHookChapterNumber(row[1]),
                 type: row[2] ?? "",
                 status: row[3] ?? "open",
                 lastAdvancedChapter: normalizedProgress,
                 expectedPayoff: row[5] ?? "",
-                payoffTiming: row.length >= 8 ? row[6] ?? "" : "",
-                notes: row.length >= 8 ? this.mergeHookNotes(row[7] ?? "", seedNote, language) : notes,
+                payoffTiming: phase6 ? row[6] ?? "" : "",
+                notes,
             };
+            if (phase7) {
+                base.dependsOn = this.parseDependsOnCell(row[7] ?? "");
+                base.paysOffInArc = (row[8] ?? "").trim();
+                base.coreHook = this.parseBooleanCell(row[9]);
+                const halfLife = this.parseOptionalInt(row[10]);
+                if (halfLife !== undefined)
+                    base.halfLifeChapters = halfLife;
+            }
+            return base;
+        });
+        // Phase 7 hotfix 2: pre-promote seeds based on the three structural rules
+        // that don't need runtime advanced_count (core_hook / depends_on /
+        // cross_volume). advanced_count-based promotion is applied later by the
+        // consolidator at volume boundaries.
+        const volumeBoundaries = this.parseVolumeBoundariesForPromotion(volumeMapRaw);
+        const allSeedStartChapters = new Map(normalizedHooks.map((hook) => [hook.hookId, hook.startChapter]));
+        const promotionContext = {
+            volumeBoundaries,
+            currentChapter: 0,
+            advancedCounts: new Map(),
+            allSeedStartChapters,
+        };
+        const promotedHooks = normalizedHooks.map((hook) => {
+            const decision = shouldPromoteHook(hook, promotionContext);
+            return { ...hook, promoted: decision.promote };
         });
-        return renderHookSnapshot(normalizedHooks, language);
+        return renderHookSnapshot(promotedHooks, language);
+    }
+    /**
+     * Parse `第N卷 (A-B章)` / `Volume N (chapters A-B)` headers from the
+     * architect's volume_map prose. Best-effort: missing / unparseable blocks
+     * return an empty list and cross-volume promotion simply never fires.
+     */
+    parseVolumeBoundariesForPromotion(raw) {
+        if (!raw)
+            return [];
+        const lines = raw.split("\n");
+        const volumeHeader = /^(第[一二三四五六七八九十百千万零〇\d]+卷|Volume\s+\d+)/i;
+        const rangePattern = /[（(]\s*(?:第|[Cc]hapters?\s+)?(\d+)\s*[-–~～—]\s*(\d+)\s*(?:章)?\s*[）)]|(?:第|[Cc]hapters?\s+)(\d+)\s*[-–~～—]\s*(\d+)\s*(?:章)?/i;
+        const volumes = [];
+        for (const rawLine of lines) {
+            const line = rawLine.replace(/^#+\s*/, "").trim();
+            if (!volumeHeader.test(line))
+                continue;
+            const rangeMatch = line.match(rangePattern);
+            if (!rangeMatch)
+                continue;
+            const startCh = parseInt(rangeMatch[1] ?? rangeMatch[3] ?? "0", 10);
+            const endCh = parseInt(rangeMatch[2] ?? rangeMatch[4] ?? "0", 10);
+            if (startCh <= 0 || endCh <= 0)
+                continue;
+            const rangeIndex = rangeMatch.index ?? line.length;
+            const name = line.slice(0, rangeIndex).replace(/[（(]\s*$/, "").trim();
+            if (name.length > 0) {
+                volumes.push({ name, startCh, endCh });
+            }
+        }
+        return volumes;
     }
     parseHookChapterNumber(value) {
         if (!value)
@@ -1148,6 +1000,35 @@ ${trimmed}\n`;
         const match = value.match(/\d+/);
         return match ? parseInt(match[0], 10) : 0;
     }
+    parseDependsOnCell(value) {
+        const trimmed = value.trim();
+        if (!trimmed)
+            return [];
+        const lower = trimmed.toLowerCase();
+        if (lower === "none" || lower === "n/a" || lower === "-" || trimmed === "无")
+            return [];
+        const stripped = trimmed.replace(/^[\[\(]\s*/, "").replace(/\s*[\]\)]$/, "");
+        return stripped
+            .split(/[,，、\/]+/)
+            .map((item) => item.trim().replace(/^\*\*(.+)\*\*$/, "$1").trim())
+            .filter((item) => item.length > 0);
+    }
+    parseBooleanCell(value) {
+        const normalized = (value ?? "").trim().toLowerCase();
+        if (!normalized)
+            return false;
+        return /^(true|yes|y|是|核心|core|1|✓|✔)$/.test(normalized);
+    }
+    parseOptionalInt(value) {
+        const normalized = (value ?? "").trim();
+        if (!normalized)
+            return undefined;
+        const match = normalized.match(/\d+/);
+        if (!match)
+            return undefined;
+        const parsed = parseInt(match[0], 10);
+        return Number.isFinite(parsed) && parsed > 0 ? parsed : undefined;
+    }
     hasNarrativeProgress(value) {
         const normalized = (value ?? "").trim().toLowerCase();
         if (!normalized)