narraeon 0.3.1 → 0.5.0

package/dist/node/shared/default-setting-improvement-prompt.js

@@ -1,73 +1,87 @@
 /**
  * Canonical author-owned guidance for AI-assisted setting improvement.
  *
- * The Runtime tool universe, schemas, descriptions, stage transitions and
- * candidate-settlement protocol deliberately do not live here. This text is
- * an ordinary portable preset asset: users may edit it without gaining any
- * authority over the mechanical setting-improvement boundary.
+ * The Runtime tool universe, schemas, per-call settlement, persistence and
+ * current-tree settlement boundary deliberately do not live here. This text is an ordinary
+ * portable preset asset: users may edit it without gaining authority over the
+ * mechanical setting-improvement boundary.
  */
 export const defaultSettingImprovementPromptPath = "prompts/setting-improvement.md";
-export const defaultSettingImprovementPromptZhCN = `# 系统推荐的设定完善方法
+export const defaultSettingImprovementPromptZhCN = `# 系统推荐的创作方法
 
-把本次目标理解为对已有内容包设定的完善，而不是默认从零重建一个新世界。用户直接注入的当前文件是已经成立的事实和约束；其他文件也应按需读取。保留仍然成立的内容，只修改目标真正涉及的部分。
+以当前编辑目标、已有内容和用户目标为起点。讨论时说明必要判断，落实时定向修改；用户要求审查或重组时，相关结构与重复表达也在范围内。不为填满结构制造内容，无需修改也是合法结果。
 
-## 先理解，再创作
+## 编辑目标与世界起点
 
-需要可见计划时，计划应简洁说明玩家想获得的主要体验、准备保留／调整／建立的内容、语气与边界，以及确实必要的假设。不适用的循环、冲突、多幕结构或次要体验可以省略，不要为了填模板而发明。
+内容包设定完善定义开场结束处的世界起点，可以包含已有历史、当前状态、持续过程和各人的认知。简单起点足以开玩，普通未定义内容可在游玩中生长；不预写未来必然发生的经历或强制剧情阶段。
 
-设定以人类可读的世界文档表达。人物、地点、关键物品、规则和当前情境按自然所有者组织；主持方法、题材边界和本世界特有的创作要求放进世界提示框架。不要把愿望、预测或计划中的未来分支伪装成创建世界时已经发生的事实。
+运行中世界修订维护当前已经演变的世界，按用户要求调整并保留未受影响的事实、经历与认知，不退回初始取值。此分支不读取或修改 opening.md。明确修订不是世界内事件，不需虚构行动解释它。
 
-## 开场白
+涉及结构、材料发现或更新位置时，先列出编辑目标根目录，完整读取 control/frame.yaml、启用的世界提示块、绑定的当前情境及受影响文档。实际操作遵守本轮工具边界。
 
-开场白是这部互动式小说的第一页，玩家读完它就要写下第一个行动。让环境、光线、声音、他人的动作和正在进行的事把场面铺开，用侧写交代气氛与关系，而不是罗列设定或逐条介绍人物。在场的人各自有手头正在做的事——世界在玩家到来之前已经在运转，不要把所有人定格成等待启动的布景。
+## 世界信息怎样组织
 
-最后一句写某个人做的一件具体的事，或说的一句具体的话：他问了什么就把原话写出来，他把东西递过来就写他怎么递的。轮到玩家是他自己从这件事里得出的结论，不需要告诉他，所以结尾只写事件、不写场面的状态——“没人说话”“众人都看着你”“他等着你的回答”都不行。也不要在结尾罗列选项，那是主持人的声音，不属于这段小说。
+世界文档承载事实与语义：当前值归自然所有者；持续过程记录实际进展与条件；意图、承诺、日程保留主体和已知条件，其目标尚未实现。角色声称、猜测与真实发生的事分开。人物的认知和态度属于各自主体，不随事实变化自动同步，也不互相对称；不代填玩家未表达的感情。
 
-不得替玩家决定行动、台词或内心：此刻还没有任何玩家输入可以承接。开场白中会继续约束首次行动的事实，必须同时写入自然承载它的世界文档，不能只存在于开场白。
+重要事件的经过集中承载，需要多人引用、持续追溯或重新解释时安排独立可引用的事件文档。事件记载当时的经过和结果；最新状态、待办与看法留在各自文档，用引用关联，事件不充当滚动状态表。对象保存当前结果，个人保存认知、关系评价与简短依据，引用相关事件而不各抄经过。已经形成的状态和态度也要保存，不能只存事件再让每次游玩重新推算。事件按事情组织，不按回合建档；普通细节可以只留在叙事。
 
-## 世界事实与持续状态
+这些区别适用于物品、伤病、地点、组织、交易、调查与人物关系，不要求固定目录、字段或数量。独立引用、自身状态或生命周期需要独立文档；小规模信息可集中在合适载体中。当前情境只承接眼前地点、在场者、进行中的事及待回应事项，不承担全部历史或未来分支。
 
-- 世界文档只写创建世界时已经成立的事实和稳定规则。愿望、意图、尝试、计划、可能性、预测、计划中的转折和未来分支都不是已经发生的事实。
-- 每项持续信息优先写给它的自然所有者。普通临时对象不必独立建档；只有需要独立引用、转移或追踪生命周期时，才升级为独立文档。
-- 当前情境只保留开场动作和即时反应结束后仍然成立的局面：此刻地点、仍在场的人物、仍在进行的事件，以及首次行动若忽略就会立刻冲突的少量限制。它不是背景摘要、事件日志或未来分支清单。
-- catalog 的摘要要写成足以帮助主持者判断“是否需要继续读取正文”的一句话，而不是“某某的资料”。正文改变后，标题和摘要也要继续准确。
+summary 是目录简介：只写识别文档所需的简短身份、主题或稳定线索，不复述具体状态和事件经过。具体事实放在正文，仅在识别信息改变时更新标题与简介。
 
-## 世界提示框架
+## 承载与发现一起安排
 
-主持预设已经提供跨世界通用的文风、玩家代理权、裁决和状态维护判据。内容包的世界提示框架只写本世界特有的部分：题材边界、专属文风、本世界有哪些文档类型、某类结果应该写进哪一份，以及专属规则。不要重复通用判据，也不要描述 Runtime 怎样编排工具。
+每项持续信息确定自然所有者、更新位置及实际的发现或注入路径。常用当前值按需全文或节点注入；较长事件通过目录和引用按需读取。重要事件应有实际可用的集中承载位置，不能只有无法创建的目录设想。查看真实 frame 和写后覆盖，不假定所有正文都已进入游玩请求。
 
-静态提示材料应尽量稳定；会随游玩持续改写的事实放进当前情境或其他自然承载它的世界文档。只有确实需要固定注入正文的材料才长期占用提示词位置。
+同一时点、同一含义的事实尽量只维护一份；过去取值、当前结果和不同主体的理解不按重复删去。当前情境、叙事及界面只承担各自用途，避免重复强化同一概念。
+
+world/ 或 state/ 承载虚构事实，control/ 安排本世界的取材、规则运用、保存位置与呈现，不复制当前值。未来游玩参考只代表实际启用的作者块；它不是本轮叙事要求，可选政策也未必始终启用。世界指令补充本世界特有约束，不重复通用规则或工具流程，不擅自改写世界外预设。
+
+## 开场与整理
+
+仅在内容包分支检查 opening.md：写玩家当时可感知的具体局面，保留尚待回答的请求与必要原话，不替玩家决定行动、台词或内心。独处、安静和等待也可形成开场。开场与文档停在同一时点，将约束首次行动的结果写给自然所有者，无需复制整篇叙事。
+
+整理结束已完成或失效的进程、约定和限制，保留仍有意义的成果、后遗影响、经历与引用。补录、去重和归档不让事情再发生。长材料按需发现，软体积提示不授权截断；暂时离场不等于退役，退役也不会移除显式全文槽。
+
+检查实际玩家视图选择器。容器会显示子树，隐藏认知不能混进公开节点；重组绑定结构时同步更新选择器。审计先对应概念、时间与主体，再处理重复句子；最后用实际写后覆盖检查发现路径，不默认输出整份内部审计表。
 `;
-export const defaultSettingImprovementPromptEn = `# Recommended setting-improvement method
+export const defaultSettingImprovementPromptEn = `# Recommended authoring method
+
+Start with the editing target, existing content and the user's goal. Discuss necessary judgments when asked to discuss; apply targeted changes when asked to implement. An audit or restructuring request includes relevant structure and duplicated expression. Do not invent content to fill a structure; no change needed is valid.
+
+## Editing target and world starting point
+
+Content-package setting improvement defines the world where the opening ends, including established history, current state, ongoing processes and individual knowledge. A simple starting point can be playable and ordinary undefined content can grow during play. Do not prewrite inevitable future experiences or mandatory plot stages.
+
+Running-world revision maintains the world as it has evolved: apply requested changes while preserving unaffected facts, events and knowledge instead of resetting initial values. This branch does not read or modify opening.md. Explicit revision is not an in-world event and needs no invented action to explain it.
+
+When structure, discovery or update locations are affected, list the editing target's root and completely read control/frame.yaml, enabled world instructions, the bound current situation and affected documents. Follow this request's actual tool boundary.
 
-Treat the current goal as an improvement to an existing content-package setting, not as an instruction to rebuild a new world from scratch. Files injected directly by the user are established facts and constraints; read other files as needed. Preserve anything that still holds and change only what the goal actually affects.
+## Organizing world information
 
-## Understand first, then create
+World documents carry facts and semantics. Current values belong to natural owners; ongoing processes retain actual progress and conditions; intentions, promises and schedules retain subjects and known conditions while their goals remain unrealized. Separate claims and guesses from what actually happened. Knowledge and attitudes belong to their holders, do not automatically follow world changes, and need not be mutual. Do not invent unexpressed player feelings.
 
-When a visible plan is requested, keep it concise: state the main experience the player wants, what will be preserved, adjusted, or established, the tone and boundaries, and only the assumptions that are genuinely necessary. Omit loops, conflicts, multi-act structures, or secondary experiences that do not apply. Do not invent material just to fill a template.
+Keep important event accounts in one place, using independently referenceable event documents for shared reference, continued retrieval or reinterpretation. Events record what happened and the outcomes at that time; latest states, pending work and views stay in their own documents, connected by references rather than copied into a rolling event-state table. Objects retain current outcomes; people retain knowledge, relationship appraisals and a brief basis, linking relevant events instead of copying their accounts. Persist formed states and attitudes too, rather than saving only events and asking each play request to infer everything again. Organize events by what happened, not by turn; ordinary details may remain narrative-only.
 
-Express the setting through human-readable world documents. Organize characters, places, key items, rules, and the current situation around their natural owners. Put hosting methods, genre boundaries, and world-specific creative requirements in the world prompt frame. Do not disguise wishes, predictions, or planned future branches as facts that have already occurred when the world is created.
+These distinctions apply to objects, injuries, places, organizations, trades, investigations and personal relationships without fixed directories, fields or counts. Independent reference, evolving state or lifecycle tracking warrants a separate document; smaller records may share a suitable home. The current situation holds the immediate location, people present, ongoing matters and unanswered requests, not all history or future branches.
 
-## Opening
+summary is a catalog description: include only a brief identity, topic or stable clue needed to identify the document, not detailed state or event accounts. Concrete facts belong in the body. Update titles and descriptions only when identifying information changes.
 
-The opening is the first page of this interactive novel; after reading it, the player will write their first action. Establish the scene through the environment, light, sound, other characters' actions, and events already in progress. Imply mood and relationships through detail instead of listing lore or introducing characters one by one. Everyone present should already be occupied with something: the world was moving before the player arrived, so do not freeze the cast as scenery waiting to be activated.
+## Arrange storage and discovery together
 
-Make the last sentence a specific action someone takes or a specific line they say. If someone asks a question, write the actual question; if they hand something over, show how they do it. The player can infer that it is their turn, so end with an event rather than a statement about the scene. Do not end with “no one speaks,” “everyone looks at you,” or “they wait for your answer.” Do not list choices at the end; that is the host's voice, not part of the novel.
+Give each durable fact a natural owner, update location and actual discovery or injection path. Inject frequently needed current values as bodies or nodes when appropriate; retrieve longer event accounts through catalogs and references. Important events need a usable central home, not merely an imagined directory that play cannot create. Check the real frame and post-write coverage instead of assuming every body enters play requests.
 
-Do not decide the player's action, dialogue, or inner thoughts: there is no player input yet to support them. Any fact in the opening that will constrain the first action must also be written to the world document that naturally owns it; it cannot exist only in the opening.
+Prefer one maintained home for facts with the same meaning at the same time. Past values, current outcomes and different subjects' interpretations are not duplicates. Let the current situation, prose and interface serve their own purposes without repeatedly overweighting one concept.
 
-## World facts and durable state
+world/ or state/ carries fictional facts. control/ arranges world-specific material selection, rule use, save locations and presentation without copying current values. Future-play reference reflects only enabled author blocks: it is not this request's narrative instruction, and optional policies may not stay enabled. World instructions add world-specific constraints without repeating general rules or tool procedures or rewriting an external preset.
 
-- World documents contain only facts and stable rules that already hold when the world is created. Wishes, intentions, attempts, plans, possibilities, predictions, planned turns, and future branches are not established facts.
-- Write each durable piece of information to its natural owner first. Ordinary temporary objects do not need their own documents; promote an object only when it must be independently referenced, transferred, or tracked through its lifecycle.
-- The current situation contains only what remains true after the opening action and immediate reactions finish: the present location, characters still present, events still in progress, and the few constraints whose omission would immediately conflict with the first action. It is not a background summary, event log, or list of future branches.
-- Catalog summaries must be informative enough for the host to decide whether to read the full body, rather than saying only “information about X.” Titles and summaries must remain accurate after the body changes.
+## Opening and consolidation
 
-## World prompt frame
+Inspect opening.md only in the content-package branch. Show a concrete situation the player can perceive, retaining unanswered requests and consequential wording without choosing player action, speech or inner thoughts. Solitude, quiet and waiting can also open a story. Documents and opening stop at the same moment; give outcomes constraining the first action to natural owners without copying the whole narrative.
 
-The host preset already provides cross-world rules for prose, player agency, adjudication, and state maintenance. The content package's world prompt frame contains only world-specific material: genre boundaries, distinctive style, the document types available in this world, where each kind of result belongs, and any special rules. Do not repeat the general criteria or explain how Runtime orchestrates tools.
+Consolidation closes completed or expired processes, commitments and restrictions while retaining meaningful results, lasting effects, events and references. Recording, deduplication and archiving do not perform events again. Keep long material discoverable on demand; advisory size limits do not authorize truncation. Temporary absence is not retirement, and retirement does not remove explicit full-document slots.
 
-Keep static prompt material as stable as possible. Facts that will change repeatedly during play belong in the current situation or another world document that naturally owns them. Reserve permanent prompt space only for material whose full text truly must be injected every time.
+Check actual player-view selectors. Containers display subtrees, so hidden knowledge must not enter public nodes. Update selectors with any restructuring of bound content. Audit concepts, time and subjects before removing repeated sentences; finish by checking discovery against real post-write coverage without printing a full internal audit by default.
 `;
 export const defaultSettingImprovementPrompt = defaultSettingImprovementPromptEn;
 export function defaultSettingImprovementPromptForLocale(locale) {

package/dist/node/shared/display-regex.js

@@ -0,0 +1,114 @@
+import { parseDocument, visit, isAlias, isNode } from "yaml";
+export function parseDisplayRegex(source, path = "regex/inline.yaml") {
+    const document = parseDocument(source, {
+        schema: "core",
+        uniqueKeys: true,
+        strict: true,
+    });
+    if (document.errors.length > 0 || document.warnings.length > 0)
+        invalid("regex_asset_invalid", `Regex-resource YAML is invalid: ${path}`, path);
+    let unsafe = false;
+    visit(document, (_, node) => {
+        if (isAlias(node) ||
+            (isNode(node) &&
+                (node.tag !== undefined || ("anchor" in node && Boolean(node.anchor)))))
+            unsafe = true;
+    });
+    if (unsafe)
+        invalid("regex_asset_invalid", "Regex YAML aliases, tags and anchors are not supported", path);
+    const value = document.toJS({ maxAliasCount: 0 });
+    if (isRecord(value))
+        assertKnownKeys(value, ["rules"], path);
+    const rules = Array.isArray(value)
+        ? value
+        : isRecord(value) && Array.isArray(value.rules)
+            ? value.rules
+            : null;
+    if (rules === null || rules.length > 256)
+        invalid("regex_rules_invalid", `A regex resource may contain at most 256 rules: ${path}`, path);
+    const orders = new Set();
+    const parsed = rules.map((raw, index) => {
+        const location = `${path}#rules[${index}]`;
+        if (!isRecord(raw))
+            invalid("regex_rule_invalid", "A regex rule must be a map", location);
+        assertKnownKeys(raw, [
+            "order",
+            "scope",
+            "pattern",
+            "flags",
+            "replace",
+            "maxMatches",
+            "errorPolicy",
+            "enabled",
+        ], location);
+        if (raw.enabled !== undefined && typeof raw.enabled !== "boolean")
+            invalid("regex_enabled_invalid", "Rule enabled must be a boolean", location);
+        const order = raw.order;
+        if (!Number.isSafeInteger(order) || order < 0)
+            invalid("regex_order_invalid", "A regex rule must declare a non-negative integer order", location);
+        if (orders.has(order))
+            invalid("regex_order_duplicate", "Regex rule order cannot be duplicated", location);
+        orders.add(order);
+        const scope = raw.scope;
+        if (scope !== "raw_text" &&
+            scope !== "markdown_html" &&
+            scope !== "structured_payload")
+            invalid("regex_scope_invalid", "A regex rule must declare raw_text, markdown_html, or structured_payload scope", location);
+        const pattern = raw.pattern;
+        if (typeof pattern !== "string" ||
+            pattern.length === 0 ||
+            pattern.length > 4_096)
+            invalid("regex_pattern_invalid", "Regex pattern must be a bounded non-empty string", location);
+        const flags = raw.flags === undefined ? "" : raw.flags;
+        if (typeof flags !== "string" || flags.length > 16)
+            invalid("regex_flags_invalid", "Regex flags are invalid", location);
+        try {
+            new RegExp(pattern, flags);
+        }
+        catch {
+            invalid("regex_pattern_invalid", "Regex pattern could not be compiled", location);
+        }
+        if (typeof raw.replace !== "string")
+            invalid("regex_replace_invalid", "Regex replace must be text", location);
+        const maxMatches = raw.maxMatches ?? 1;
+        if (!Number.isSafeInteger(maxMatches) ||
+            maxMatches < 1 ||
+            maxMatches > 1_024)
+            invalid("regex_limit_invalid", "Regex replacement count must be a bounded positive integer", location);
+        const errorPolicy = raw.errorPolicy;
+        if (errorPolicy !== "fallback" &&
+            errorPolicy !== "skip" &&
+            errorPolicy !== "fail")
+            invalid("regex_error_policy_invalid", "A regex rule must declare fallback, skip, or fail errorPolicy", location);
+        return {
+            ...(raw.enabled === undefined ? {} : { enabled: raw.enabled }),
+            order: order,
+            scope,
+            pattern,
+            flags,
+            replace: raw.replace,
+            maxMatches: maxMatches,
+            errorPolicy,
+        };
+    });
+    return parsed.sort((left, right) => left.order - right.order);
+}
+export class DisplayRegexError extends Error {
+    code;
+    constructor(code, message) {
+        super(message);
+        this.code = code;
+    }
+}
+function invalid(code, message, _location) {
+    void _location;
+    throw new DisplayRegexError(code, message);
+}
+function isRecord(value) {
+    return value !== null && typeof value === "object" && !Array.isArray(value);
+}
+function assertKnownKeys(value, allowed, location) {
+    const unknown = Object.keys(value).find((key) => !allowed.includes(key));
+    if (unknown !== undefined)
+        invalid("unsupported_field", `The current play format does not support field: ${unknown}`, location);
+}

package/dist/node/shared/first-party-action-choices.js

@@ -100,12 +100,7 @@ Use only information the player can already know, and suggest only actions the p
         "scripts/player-options.js": `(function () {
   var root = document.getElementById("player-options-root");
   var pending = new Map();
-  var styleSource = window.__NARRAEON_ASSETS__ && window.__NARRAEON_ASSETS__["assets/player-options.css"];
-  if (typeof styleSource === "string") {
-    var style = document.createElement("style");
-    style.textContent = styleSource;
-    document.head.append(style);
-  }
+
   function post(command, payload) {
     var requestId = "draft-" + Math.random().toString(36).slice(2);
     parent.postMessage({

package/dist/node/shared/first-party-player-view.js

@@ -60,12 +60,7 @@ followups: []
 `,
         "scripts/player-view-status.js": `(function () {
   var root = document.getElementById("player-view-panel-root");
-  var styleSource = window.__NARRAEON_ASSETS__ && window.__NARRAEON_ASSETS__["assets/player-view-status.css"];
-  if (typeof styleSource === "string") {
-    var style = document.createElement("style");
-    style.textContent = styleSource;
-    document.head.append(style);
-  }
+
   function valueNode(value) {
     if (value === null || value === undefined) return document.createTextNode("—");
     if (typeof value === "object") {

package/dist/node/shared/ordered-author-prompts.js

@@ -0,0 +1,64 @@
+import { defaultSettingImprovementPromptForLocale } from "./default-setting-improvement-prompt.js";
+/** Authoring uses the same permissions as play, with target-specific dynamic references. */
+export function builtinAuthorPrompts(locale) {
+    const zh = locale === "zh-CN";
+    return [
+        {
+            id: "author.mechanics",
+            name: zh
+                ? "创作工具与结算（必选）"
+                : "Authoring tools and settlement (required)",
+            required: true,
+            body: authoringMechanics(locale, "setting"),
+        },
+        {
+            id: "author.guidance",
+            name: zh ? "创作建议" : "Authoring guidance",
+            required: false,
+            body: defaultSettingImprovementPromptForLocale(locale),
+        },
+        {
+            id: "author.target",
+            name: zh
+                ? "创作目标与读取授权（动态必选）"
+                : "Target and read authorization (required, dynamic)",
+            required: true,
+            body: zh
+                ? "实际请求在此显示内容包或修订世界身份及当前树边界。世界修订保留独占 epoch；跨 epoch 继续时在用户消息前显式通知并清空读取授权。文件正文只通过工具按需读取，不预注入整棵树。"
+                : "The actual request shows the content package or revision world identity and current-tree boundary here. World revision retains its exclusive epoch; continuing across epochs announces the transition before the user message and clears read authorization. Files are read on demand through tools, never injected as a whole tree.",
+        },
+        {
+            id: "author.play-reference",
+            name: zh ? "未来游玩参考（动态）" : "Future play reference (dynamic)",
+            required: false,
+            body: zh
+                ? "在此展开当前预设已启用的游玩编排，明确标为未来游玩参考，不是本轮叙事要求。内容包及世界正文仍通过创作工具读取。"
+                : "Expands the current preset's enabled play arrangement as future-play reference, not narrative instructions for this conversation. Actual package and world content remains behind authoring tools.",
+        },
+    ];
+}
+export function authoringMechanics(locale, target) {
+    const zh = locale === "zh-CN";
+    const common = zh
+        ? `只使用请求随附的工具及其参数契约。含工具调用的响应是中间步；收到全部工具结果后继续，非空且无工具调用的响应结束本次发送。完整工具响应按调用顺序结算，失败调用不撤销成功同级调用。修改既有文件前必须完整读取；cursor 只属于产生它的树 revision；本事务自身成功修改后的完整读取授权由 Runtime 承接。外部树变化或跨 epoch 后旧授权失效，需要重新读取。工具返回逻辑路径，不能访问宿主文件。文档引用使用返回的 @ref；YAML 整文档引用为单键 {$ref: "@ref"}，locator 使用 map key 或从零开始的数组下标。成功回执决定当前值，模型文字不构成提交。`
+        : `Use only the attached tools and their parameter contracts. Responses with tool calls are intermediate steps; continue after all results. A nonempty tool-free response ends this send. Complete tool responses settle calls in order; a failed call does not undo successful siblings. Completely read existing files before writing. Cursors belong to their producing tree revision. Runtime carries complete-read authorization through this transaction’s own successful changes. External tree changes or an epoch transition invalidate old authorization and require new reads. Tools expose logical paths, never host files. Use returned @refs for documents; YAML whole-document references are single-key {$ref: "@ref"} maps, and locators use map keys or zero-based array indexes. Actual receipts determine current values; model prose cannot commit changes.`;
+    const boundary = target === "setting"
+        ? zh
+            ? "内容包工具的成功变化在完整响应结算时原子发布到当前树，无需应用。setting_create 建立新文档身份；删除仅在无绑定与引用阻挡时接受。"
+            : "Successful content-package changes publish atomically to the current tree when the complete response settles, with no Apply step. setting_create establishes new document identities; deletion is accepted only without binding or reference blockers."
+        : zh
+            ? "世界修订工具只修改持久独占 epoch 的 state/* 与 control/* 工作树。opening.md 不可读取或修改，既有状态文档不可删除或移动。只有玩家应用或放弃才结束 epoch；应用提交世界，放弃不改变世界。跨 epoch 全部旧读取授权失效。"
+            : "World-revision tools modify only state/* and control/* in the durably locked exclusive epoch. opening.md cannot be read or changed; existing state documents cannot be deleted or moved. Only player Apply or Discard ends the epoch; Apply commits the world, Discard leaves it unchanged. Every old read authorization expires across epochs.";
+    const views = zh
+        ? 'control/player-views.yaml 的 format 为 narraeon.player-views/v1；views 中每项有 id、title 和 items，items 中每项有 id、label、select。精确选择一个 YAML 字段使用 select: {document: "@ref", locator: {yaml: [字段名]}}；Markdown 小节使用 locator: {markdown: [标题]}。document 必须来自实际返回的引用，locator 必须对应已读正文；省略 locator 会展示整份文档，选择容器会递归展示子树。'
+        : 'control/player-views.yaml uses format: narraeon.player-views/v1. Each views entry has id, title and items; each item has id, label and select. Select one YAML field with select: {document: "@ref", locator: {yaml: [field]}}; select a Markdown section with locator: {markdown: [heading]}. Use a returned document reference and a locator from the actual read body. Omitting locator displays the whole document; selecting a container recursively displays its subtree.';
+    return `# ${zh ? "创作工具与结算" : "Authoring tools and settlement"}\n\n${common}\n\n${boundary}\n\n${views}`;
+}
+export function defaultOrderedAuthorPrompts() {
+    return builtinAuthorPrompts("en").map(({ id }) => ({
+        id,
+        kind: "builtin",
+        builtin: id,
+        enabled: true,
+    }));
+}

package/dist/node/shared/ordered-followups.js

@@ -0,0 +1,42 @@
+export function defaultFollowupItems(definitions) {
+    return [
+        ...definitions.map(({ id }) => ({
+            id,
+            kind: "user",
+            enabled: true,
+        })),
+        { id: "builtin:summary", kind: "builtin", enabled: false },
+        { id: "package:followups", kind: "content-package", enabled: true },
+    ];
+}
+/** A current application example; snapshots freeze the compiled text, never this reference. */
+export function builtinFollowupExample(locale) {
+    const zh = locale === "zh-CN";
+    return {
+        body: zh
+            ? "主叙事已完成。仅根据已向玩家呈现的叙事与明确可见事实整理简短场景回顾，通过 artifact_emit 输出 recap。不要从工具材料、未表露认知或场外状态补全幕后原因，不补写剧情或引入新事实。回顾只是显示产物，不替代状态维护、检查点或历史恢复。"
+            : "The main narrative has settled. Emit a brief scene recap as recap using artifact_emit, using only narrative already shown to the player and explicitly visible facts. Do not fill in backstage causes from tool material, unexpressed knowledge or offstage state. Do not continue the story or introduce new facts. This display artifact does not replace state maintenance, checkpoints or history recovery.",
+        definition: {
+            id: "builtin:summary",
+            displayName: zh ? "场景回顾（系统示例）" : "Scene recap (system example)",
+            prompt: {
+                role: "author_instruction",
+                path: "builtin:followup-summary",
+            },
+            artifacts: [
+                {
+                    name: "recap",
+                    channel: "builtin:summary",
+                    strategy: "replace",
+                    contentType: "text/markdown",
+                    rendererMode: "document",
+                    save: "commit",
+                    invalidation: "explicit_clear",
+                    required: true,
+                    maxEmits: 1,
+                },
+            ],
+            maxArtifactBytes: 32_768,
+        },
+    };
+}

package/dist/node/shared/ordered-play-prompts.js

@@ -0,0 +1,73 @@
+import { defaultNarrationPromptForLocale } from "./default-play-prompts.js";
+import { defaultPresetHostFilesForLocale } from "./default-preset-host.js";
+/** Application-owned references. Persist references; freeze resolved text in requests. */
+export function builtinPlayPrompts(locale) {
+    const zh = locale === "zh-CN";
+    const host = defaultPresetHostFilesForLocale(locale);
+    return [
+        {
+            id: "play.mechanics",
+            name: zh
+                ? "工具与响应结算（必选）"
+                : "Tools and response settlement (required)",
+            required: true,
+            body: zh
+                ? `# 工具与响应结算
+
+只可调用请求随附的工具。目录使用 Runtime 返回的 @dir-*；文档和历史使用返回的 @句柄。工具结果标明读取范围、完整性及 cursor；目录摘要不等于正文。材料覆盖中完整正文与精确读取授予对应范围的写入资格，界面绑定标注不授予额外权限。同一原生对话刷新提示时，仅在当前状态与旧读取凭据完全匹配时承接原精确范围，并合并本次注入授权；全新上下文不继承旧对话授权。
+
+world_patch 的 YAML locator 可以包含 map key 和从零开始的数组下标；remove 删除一个精确位置。未提供的元数据保持原值。world_retire 从目录注入中退役文档，文档仍可读取、引用和恢复。工具响应的成功状态变化与后续最终叙事分别提交，后续失败不回滚已提交变化。成功写入回执表示当前值已改变；以真实回执的结算状态为准，模型文字不能提交世界。
+
+包含工具调用的响应属于中间步，正文不作为最终叙事提交。收到全部工具结果后继续；没有工具调用的非空正文结束本次循环并由 Runtime 提交叙事。world_checkpoint 登记在随后最终叙事成功提交后生效，边界包含该叙事；登记后仍可继续工具调用。全新上下文的历史补充只包含检查点后的已提交玩家原文与最终叙事，排除开场白、工具和推理。`
+                : `# Tools and response settlement
+
+Use only attached tools. Directories use returned @dir-* handles; documents and history use returned @handles. Results identify read scope, completeness and cursor; directory summaries are not document bodies. Complete injected bodies and exact reads authorize writes within their corresponding scopes; player-view annotations grant no additional authority. Refreshing the same native conversation retains prior exact scopes only when the current state matches their proof, merging them with current injected authorization. A fresh context does not inherit old conversation authorization.
+
+YAML world_patch locators accept map keys and zero-based array indexes; remove deletes one exact location. Omitted metadata remains unchanged. world_retire removes a document from catalog injection while keeping it readable, referenceable and restorable. Successful tool-response state changes and later final narrative commit separately; later failure does not roll back committed changes. Successful write receipts change current values; the actual receipt determines settlement, not model prose.
+
+Responses containing tool calls are intermediate steps; their text is not committed as final narrative. Continue after all tool results. A nonempty tool-free response ends this loop and Runtime commits its narrative. world_checkpoint takes effect after the subsequent final narrative commits, including that narrative in its boundary; further tool calls may follow registration. Fresh-context replay contains committed player originals and final narratives after the checkpoint, excluding the opening, tools and reasoning.`,
+        },
+        {
+            id: "play.style",
+            name: zh ? "通用文风" : "General style",
+            body: host["blocks/style.md"],
+            required: false,
+        },
+        ...["adjudication", "state"].map((id) => ({
+            id: `play.${id}`,
+            name: zh
+                ? id === "state"
+                    ? "状态维护建议"
+                    : "裁判与玩家代理权"
+                : id === "state"
+                    ? "State maintenance"
+                    : "Adjudication and player agency",
+            body: host[`blocks/${id}.md`],
+            required: false,
+        })),
+        {
+            id: "play.narrative",
+            name: zh ? "叙事建议" : "Narrative guidance",
+            body: defaultNarrationPromptForLocale(locale),
+            required: false,
+        },
+        ...Object.entries(host)
+            .filter(([path]) => path.startsWith("blocks/style-"))
+            .map(([path, body]) => ({
+            id: `play.${path.slice(7, -3)}`,
+            name: /^#\s+(.+)$/mu.exec(body)?.[1] ?? path,
+            body,
+            required: false,
+        })),
+    ];
+}
+export function defaultOrderedPlayPrompts() {
+    return builtinPlayPrompts("en")
+        .map(({ id }) => ({
+        id,
+        kind: "builtin",
+        builtin: id,
+        enabled: !id.startsWith("play.style-"),
+    }))
+        .concat([{ id: "world", kind: "world" }]);
+}