svharness 0.14.13 → 0.14.17

package/dist/wiki/repowikiPrompts.js

@@ -0,0 +1,296 @@
+"use strict";
+/**
+ * Dual-audience LLM prompts for wiki generation.
+ *
+ * - `human`: standalone `svharness wiki` — developer-readable documentation.
+ * - `agent`: `svharness build` / `svharness wiki --harness` — coding-agent knowledge map.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.structurePrompt = structurePrompt;
+exports.structureSystemPrompt = structureSystemPrompt;
+exports.pageMarkdownPrompt = pageMarkdownPrompt;
+exports.pageGenerationSystemPrompt = pageGenerationSystemPrompt;
+const wikiStructureXml_1 = require("./wikiStructureXml");
+function zhOutlineExtra(structureLang) {
+    return structureLang.folder === "zh"
+        ? `
+
+【简体中文硬性要求 — 纲要步骤】凡是给人看的文字（仓库级 <title>/ <description>、每个 <section> 的 <title>、每个 <page> 的 <title> 与 <description>）必须全部是简体中文（zh-CN）。禁止使用英文句子或段落；仅路径、文件名、代码标识符/API 符号可保留英文。`
+        : "";
+}
+function enOutlineExtra(structureLang) {
+    return structureLang.folder === "en"
+        ? `
+
+【English hard requirement — outline step】All human-readable text in this XML (repo-level <title>/<description>, each <section>'s <title>, each <page>'s <title> and <description>) MUST be fluent English. Do not write Chinese, Japanese, or other non-English prose for those fields. Only code identifiers, filenames, paths, API symbols, and unavoidable proper nouns may stay non-English where appropriate.`
+        : "";
+}
+function humanComprehensiveSectionBlock(structureLang) {
+    return `Use **multiple** top-level \`<section>\` blocks under \`<sections>\`: **between 2 and 7** (inclusive). **Never** return only **one** section when the wiki has **two or more** pages — split topics into **distinct** sections (do **not** collapse everything into a single bucket named after the wiki title).
+Use **at most 7** sections total. For very small repos with only **one** page, **one** section is acceptable.
+Each section MUST have a **unique** \`id\` attribute (letters, digits, hyphens only — stable identifier).
+Each section's \`<title>\` MUST be **in the outline language** (${structureLang.label}), **repo-specific**, and suitable as a section heading (this becomes the subdirectory name under each language folder).
+**Filesystem folders** under the language directory are derived from each section \`<title>\` (slugified), **not** from \`id\`.
+Distribute pages across sections: each section's \`<pages>\` lists \`<page_ref>\` ids; use **at most ${wikiStructureXml_1.REPOWIKI_MAX_PAGES}** pages **total** across all sections.
+
+Return ONLY valid XML in this shape:
+
+<wiki_structure>
+  <title>[Overall title]</title>
+  <description>[Brief]</description>
+  <sections>
+    <section id="getting-started">
+      <title>[Section title in outline language]</title>
+      <pages>
+        <page_ref>page-1</page_ref>
+      </pages>
+      <subsections/>
+    </section>
+    <!-- more sections with unique ids -->
+  </sections>
+  <pages>
+    <page id="page-1">
+      <title>[Title]</title>
+      <description>[What this covers]</description>
+      <importance>high</importance>
+      <relevant_files>
+        <file_path>[repo-relative/path]</file_path>
+      </relevant_files>
+      <related_pages/>
+      <parent_section>getting-started</parent_section>
+    </page>
+  </pages>
+</wiki_structure>`;
+}
+function agentComprehensiveSectionBlock(structureLang) {
+    return `Produce an **agent knowledge map** (not a human tutorial). Use **multiple** top-level \`<section>\` blocks under \`<sections>\`: **between 2 and 7** (inclusive).
+Organize sections by **coding workflow**, not marketing names. Prefer repo-specific titles such as (in ${structureLang.label}):
+- module boundaries / navigation
+- architecture & extension points (Module, Config, DI entry)
+- data & state flow (Repository, signals, UseCase)
+- UI & MVI patterns (Screen, ViewModel, Contract)
+- feature-domain slices (one section per major feature area when applicable)
+
+Each section MUST have a **unique** \`id\` (letters, digits, hyphens only).
+Each section's \`<title>\` MUST be in ${structureLang.label}, filesystem-friendly (becomes subdirectory name under each language folder).
+Use **at most ${wikiStructureXml_1.REPOWIKI_MAX_PAGES}** pages **total** across all sections.
+
+Return ONLY valid XML in this shape:
+
+<wiki_structure>
+  <title>[Overall title]</title>
+  <description>[Brief — what this knowledge map helps a coding agent do]</description>
+  <sections>
+    <section id="module-boundaries">
+      <title>[Section title in outline language]</title>
+      <pages>
+        <page_ref>page-1</page_ref>
+      </pages>
+      <subsections/>
+    </section>
+  </sections>
+  <pages>
+    <page id="page-1">
+      <title>[Title]</title>
+      <description>[When a coding agent needs ___, read this page. Keywords: ClassName, path/hint]</description>
+      <importance>high</importance>
+      <relevant_files>
+        <file_path>[entry-point path, read order]</file_path>
+      </relevant_files>
+      <related_pages/>
+      <parent_section>module-boundaries</parent_section>
+    </page>
+  </pages>
+</wiki_structure>`;
+}
+function simpleSectionBlock() {
+    return `<wiki_structure>
+  <title>[Overall title]</title>
+  <description>[Brief]</description>
+  <pages>
+    <page id="page-1">
+      <title>[Title]</title>
+      <description>[What]</description>
+      <importance>high</importance>
+      <relevant_files>
+        <file_path>[path]</file_path>
+      </relevant_files>
+      <related_pages/>
+    </page>
+  </pages>
+</wiki_structure>`;
+}
+function agentSimpleSectionBlock() {
+    return `<wiki_structure>
+  <title>[Overall title]</title>
+  <description>[Brief — agent knowledge map scope]</description>
+  <pages>
+    <page id="page-1">
+      <title>[Title]</title>
+      <description>[When a coding agent needs ___, read this page]</description>
+      <importance>high</importance>
+      <relevant_files>
+        <file_path>[entry-point path]</file_path>
+      </relevant_files>
+      <related_pages/>
+    </page>
+  </pages>
+</wiki_structure>`;
+}
+function comprehensiveRules(comprehensive) {
+    if (comprehensive) {
+        return `- Every \`<page>\` MUST include \`<parent_section>\` with the **exact** \`id\` of the section that owns this page (the section whose \`<page_ref>\` lists this page id).
+- Each page id must appear in exactly one section's \`page_ref\` list.
+- Each section \`<title>\` becomes a subdirectory name (slugified); keep titles concise and filesystem-friendly where possible.
+- CRITICAL: Every tag must be closed. After \`<sections>\`, you MUST include one final \`<pages>...</pages>\` block containing every full \`<page id="...">...</page>\` with title, description, parent_section, and relevant_files. Section-level \`<pages>\` may only list \`<page_ref>\` — never omit the outer \`<page>\` definitions.`;
+    }
+    return `- Without a \`<sections>\` block, every page is stored under **one** folder derived from the wiki \`<title>\`; omit \`<parent_section>\` or ignore it for paths.
+- CRITICAL: Every tag must be closed. Include a \`<pages>\` block listing every full \`<page id="...">...</page>\` with title, description, and relevant_files.`;
+}
+function agentExtraRules(comprehensive) {
+    return `- Every \`<page><description>\` MUST start with a routing sentence: when a **coding agent** needs [specific task], read this page (in ${comprehensive ? "outline" : "wiki"} language).
+- \`<relevant_files>\`: list **3–8 entry-point files** (Module/Config/Contract/Repository/Application) in **recommended read order**; skip generated/vendor dirs.
+- \`<importance>\`: \`high\` = read before any new task; \`medium\` = domain-specific; \`low\` = deep detail.`;
+}
+function structurePrompt(audience, repoName, treeText, readmeChunk, structureLang, comprehensive) {
+    const opening = audience === "agent"
+        ? `Analyze the repository "${repoName}" and produce an **agent knowledge map** (not a human tutorial). Each page must help a **coding AI agent** decide **when to read it**, **which files to open first**, and **what patterns/constraints apply**.`
+        : `Analyze the repository "${repoName}" and propose a concise developer wiki outline.`;
+    const sectionBlock = comprehensive
+        ? audience === "agent"
+            ? agentComprehensiveSectionBlock(structureLang)
+            : humanComprehensiveSectionBlock(structureLang)
+        : audience === "agent"
+            ? agentSimpleSectionBlock()
+            : simpleSectionBlock();
+    const agentRules = audience === "agent" ? `\n${agentExtraRules(comprehensive)}` : "";
+    return `${opening}
+
+<file_tree>
+${treeText}
+</file_tree>
+
+<readme_excerpt>
+${readmeChunk.slice(0, 12_000)}
+</readme_excerpt>
+
+Target language for human-readable titles/descriptions ONLY in this outline step: ${structureLang.label}.${zhOutlineExtra(structureLang)}${enOutlineExtra(structureLang)}
+
+${sectionBlock}
+
+Rules:
+- Produce **at most ${wikiStructureXml_1.REPOWIKI_MAX_PAGES}** wiki pages total with **stable** ids \`page-1\`, \`page-2\`, …, \`page-${wikiStructureXml_1.REPOWIKI_MAX_PAGES}\` (use consecutive ids; fewer pages is OK).
+${comprehensiveRules(comprehensive)}
+- Ensure \`relevant_files\` cite real paths from file_tree where possible (skip generated/vendor dirs).${agentRules}
+- Return ONLY XML. No markdown fences. No HTML. Start with <wiki_structure> end </wiki_structure>.`;
+}
+function structureSystemPrompt(audience, langFolder) {
+    if (audience === "agent") {
+        if (langFolder === "zh") {
+            return "你只输出格式正确的 wiki_structure XML（符合用户给定模板）；不要使用 markdown 代码围栏。本纲要面向编码 Agent：标题与描述须可路由、可执行（何时读、改哪些文件），禁止 onboarding 式空话。凡是给人阅读的标题与描述必须使用简体中文（zh-CN）。";
+        }
+        if (langFolder === "en") {
+            return "You output ONLY well-formed wiki_structure XML matching the user's template. Never use markdown fences. This outline is for coding agents: titles/descriptions must be routable and actionable (when to read, which files to open). No onboarding fluff. Human-readable fields must be fluent English.";
+        }
+        return "You output ONLY well-formed wiki_structure XML for coding agents. Never use markdown fences.";
+    }
+    if (langFolder === "zh") {
+        return "你只输出格式正确的 wiki_structure XML（符合用户给定模板）；不要使用 markdown 代码围栏。纲要中凡是给人阅读的标题与描述必须使用简体中文（zh-CN）。";
+    }
+    if (langFolder === "en") {
+        return "You output ONLY well-formed wiki_structure XML matching the user's template. Never use markdown fences. Every repo title, wiki title/description, section titles, page titles, and page descriptions meant for humans must be fluent English (no Chinese prose in those strings unless it is unavoidable quoted content from the repository).";
+    }
+    return "You output ONLY well-formed wiki_structure XML matching the user's template. Never use markdown fences.";
+}
+function zhBodyExtra(langFolder) {
+    return langFolder === "zh"
+        ? `
+
+【简体中文硬性要求 — 正文】全部正文、各级标题（# / ## / ###）、表格单元格、Mermaid 与其它图中的说明文字一律使用简体中文（zh-CN）。禁止英文句子，除非直接引用代码、路径、标识符或 API 名称。`
+        : "";
+}
+function enBodyExtra(langFolder) {
+    return langFolder === "en"
+        ? `
+
+【English hard requirement — body】All prose, headings (# / ## / ###), table cell text, and explanatory labels inside Mermaid/diagrams MUST be English. Do not write Chinese prose (or mixed-language explanations) unless you are quoting literal content from repo files/strings. Preserve non-English only in fenced code excerpts, paths, identifiers, and API symbols as they appear in the repo.`
+        : "";
+}
+function h1Rule(langFolder, ruleNum) {
+    if (langFolder === "zh") {
+        return `${ruleNum}. Start with '# [title]' (the H1 must match the topic; for a zh-CN wiki, use Simplified Chinese for that title line).`;
+    }
+    if (langFolder === "en") {
+        return `${ruleNum}. Start with '# [title]' (the H1 must match the topic in English prose).`;
+    }
+    return `${ruleNum}. Start with '# [title]' (the H1 must match the topic).`;
+}
+function pageMarkdownPrompt(audience, langFolder, langDescriptor, pageTopic, ctx) {
+    const zhExtra = zhBodyExtra(langFolder);
+    const enExtra = enBodyExtra(langFolder);
+    if (audience === "agent") {
+        return `You produce a **coding-agent knowledge page** (not a human tutorial). Ground every claim in bundled files only.
+
+Output language: ${langDescriptor}.${zhExtra}${enExtra}
+
+Repository context bundled as tagged files:
+
+${ctx}
+
+Write ONE wiki page for topic: "${pageTopic}".
+
+Strict rules:
+1. Ground claims only in supplied files.
+${h1Rule(langFolder, 2)}
+3. Immediately after the H1, add one line: \`Sources: path/to/file:start-end, ...\` (repo-relative paths, comma-separated).
+4. Use **exactly** these ## sections in order (omit none; use "见关键路径" or "暂无" when empty):
+   - \`## 阅读时机\` — 1–3 bullets: when a coding agent should read this page
+   - \`## 关键路径\` — table: 用途 | 路径 | 符号/类
+   - \`## 扩展与修改入口\` — bullets: how to add/change similar functionality
+   - \`## 数据流 / 调用链\` — short text or \`\`\`mermaid graph TD\`\`\` **only** if flow is non-obvious; otherwise "见关键路径"
+   - \`## 约定与禁区\` — must-follow and must-not rules from the code
+   - \`## 关联\` — related pages or modules if inferable from context
+5. Do **not** add a TOC block. Do **not** write long onboarding paragraphs (max 5 lines prose per section excluding code).
+6. Fenced code: ≤40 lines per block; prefer signatures/interfaces over full implementations.
+7. Mermaid is optional — use only when the call chain cannot be expressed as a table or bullets.
+
+If bundled files lack coverage, state gaps briefly — do not invent APIs.`;
+    }
+    return `You write accurate technical Markdown documentation for developers.
+
+Output language: ${langDescriptor}.${zhExtra}${enExtra}
+
+Repository context bundled as tagged files:
+
+${ctx}
+
+Write ONE wiki page for topic: "${pageTopic}".
+
+Strict rules:
+1. Ground claims only in supplied files.
+${h1Rule(langFolder, 2)}
+3. After the introduction (first paragraph or short opener) and **before** the first \`##\`, add a concise **table of contents**: a bullet or numbered list of links to the \`##\` sections that follow (use markdown links with anchors, e.g. \`[Section](#section-slug)\`, matching your real headings). **Omit this TOC** if the page is very short or only has a single \`##\` section (avoid a redundant mini-TOC).
+4. Use '##','###', tables, fenced code from files when helpful.
+5. Prefer Mermaid with \`\`\`mermaid diagrams using TOP-DOWN flow (\`graph TD\`, not LR).
+6. Where useful cite repository files on one line: \`Sources: path/to/file:line-range\` (comma-separated if multiple). Paths are repo-relative with \`/\` separators.
+
+If bundled files lack coverage, acknowledge gaps briefly — do not invent APIs.`;
+}
+function pageGenerationSystemPrompt(audience, langFolder) {
+    if (audience === "agent") {
+        if (langFolder === "zh") {
+            return "你是编码 Agent 的知识索引员，只根据提供的 <file path=…> 摘录产出可执行知识页。Wiki 须含固定章节（阅读时机、关键路径、扩展与修改入口、数据流/调用链、约定与禁区、关联）。除代码摘录、路径与标识符外禁止使用英文 prose。";
+        }
+        if (langFolder === "en") {
+            return "You index knowledge for coding agents. Answer ONLY from bundled <file path=…> excerpts. The page MUST use the fixed section template (When to read, Key paths, Extension entry points, Data flow, Conventions/constraints, Related). English prose throughout except code, paths, identifiers.";
+        }
+        return "You produce agent-oriented Markdown grounded strictly in bundled <file path=…> excerpts.";
+    }
+    if (langFolder === "zh") {
+        return "你是技术文档撰写者，只根据提供的 <file path=…> 摘录作答。Wiki 页的各级标题、正文、表格文字、图中的文字说明必须全部是简体中文（zh-CN）。除代码摘录、仓库路径与标识符/API 英文名外禁止使用英文 prose。";
+    }
+    if (langFolder === "en") {
+        return "You are a technical writer. Answer ONLY from bundled <file path=…> excerpts. The entire Markdown page MUST be English: headings, body, table text, diagram labels/explanations. Use non-English prose only inside literal code fences or when verbatim-quoting user-facing strings from the repository; identifiers, paths, and API symbols follow the codebase.";
+    }
+    return "You write factual Markdown grounded strictly in bundled <file path=…> excerpts.";
+}

package/dist/wiki/repowikiStructureNormalize.js

@@ -187,8 +187,38 @@ function normalizeComprehensiveWikiStructure(opts) {
         groups,
     };
 }
-function structureRepairUserAppendix(previousRaw, langFolder) {
+function structureRepairUserAppendix(previousRaw, langFolder, audience = "human") {
     const preview = previousRaw.slice(0, 8_000);
+    if (audience === "agent") {
+        if (langFolder === "zh") {
+            return `
+
+【修订要求 — 上一条 Agent 知识地图无效】上一次的 wiki_structure **小节数量不足**（少于 2 个顶层 <section>，或缺失 <sections>），但需要 **2 至 7 个** 顶层小节。请重新输出 **完整** 的 wiki_structure XML（不要用"见上文"省略）。
+
+硬性要求：
+- 在 <sections> 下提供 **至少 2 个、至多 7 个** 平级 <section>，每个有唯一 id；按编码工作流划分，非教程式命名。
+- **禁止** 把所有 <page> 放进同一个小节；将 ≤20 页分配到多个小节。
+- 每个 <page><description> 须含「当编码 Agent 需要 ___ 时阅读本页」路由句。
+- 每个 <page> 必须有 <parent_section>，其值必须等于拥有该页的 section 的 id（且该 section 的 <page_ref> 引用此页）。
+- 仍须符合此前的 Agent 知识地图模板（先 <sections>，再完整 <pages> 块等）。
+
+上一次输出摘要（仅供参考，请修正而非照抄）：
+${preview}`;
+        }
+        return `
+
+【Revision required — previous agent knowledge map invalid】The last wiki_structure had **too few** top-level <section> blocks under <sections> (or <sections> was missing). Return a **complete new** wiki_structure XML with **between 2 and 7** sibling <section> elements.
+
+Hard requirements:
+- Provide **at least 2 and at most 7** <section> elements under <sections>, each with a **unique** id; organize by coding workflow, not tutorial naming.
+- **Do not** place every <page> in a single section; distribute up to 20 pages across multiple sections.
+- Every <page><description> MUST include a routing sentence for coding agents (when to read this page).
+- Every <page> MUST include <parent_section> equal to the owning section id (that section MUST list the page via <page_ref>).
+- Follow the same agent knowledge map template as before (<sections> first, then a full <pages> block).
+
+Previous output (for reference only — fix it, do not copy):
+${preview}`;
+    }
     if (langFolder === "zh") {
         return `
 

package/dist/wiki/wikiTasksWriter.js

@@ -1,8 +1,8 @@
 "use strict";
 /**
  * Writes a `TASKS.md` inside `<wikiBase>/` based on an outline computed by
- * `runRepowikiOutlineOnly`. The file is consumed by the downstream
- * harness-build-skill-wiki-writer skill which fills page content iteratively.
+ * `runRepowikiOutlineOnly`. Agent-audience tasks are consumed by
+ * harness-build-skill-wiki-writer; human-audience tasks are for standalone wiki maintenance.
  */
 var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
     if (k2 === undefined) k2 = k;
@@ -55,10 +55,9 @@ function groupBySection(pages) {
     }
     return [...buckets.entries()].map(([folder, list]) => ({ folder, pages: list }));
 }
-function renderTasksMarkdown(input) {
-    const { outline } = input;
+function renderHeaderBlock(input, audience) {
     const lines = [];
-    const groups = groupBySection(outline.pages);
+    const { outline } = input;
     lines.push(`# Baseline Wiki Tasks — ${input.projectName}`);
     lines.push("");
     lines.push(`Generated by svharness v${input.cliVersion} on ${input.generatedAtIso}`);
@@ -66,18 +65,59 @@ function renderTasksMarkdown(input) {
     lines.push(`Outline model: \`${input.model}\``);
     lines.push(`Outline XML: \`./structure.xml\``);
     lines.push(`Primary language: \`${outline.primaryLang}\``);
+    lines.push(`Wiki audience: \`${audience}\``);
     lines.push("");
-    lines.push("> 下游 agent（harness-build-skill-wiki-writer）按本清单逐页生成 wiki：");
-    lines.push("> 逐条完成 Pages 列表中的任务，每完成一页把 `[ ]` 改为 `[x]`。");
-    lines.push("> 每页应产出 Markdown 文件到对应 `Output` 路径，内容严格基于基线源码。");
-    lines.push("");
-    lines.push("> **源码引用规范（强制，与 --generate-wiki 产出口径保持一致）**：");
-    lines.push("> 所有源码链接必须指向 `baseline/code/` 下的路径，允许两种写法（可混用）：");
-    lines.push("> 1. 行内链接：`[Foo.java:10-30](../../baseline/code/<repo-relative>/Foo.java#L10-L30)`");
-    lines.push("> 2. Sources 行：`Sources: <repo-relative>/Foo.java:10-30, <repo-relative>/Bar.kt:5-8`");
-    lines.push("> `<repo-relative>` 指**相对 `baseline/code/` 的路径**，既非仓库原始绝对路径，");
-    lines.push("> 也非 wiki md 文件的相对路径。行号使用 `start-end`（闭区间）。");
+    if (audience === "agent") {
+        lines.push("> 本 wiki 面向**编码 Agent**消费：每页是知识路由卡片，不是人类 onboarding 文档。");
+        lines.push("> 下游 agent（harness-build-skill-wiki-writer）按本清单逐页生成 wiki：");
+        lines.push("> 逐条完成 Pages 列表中的任务，每完成一页把 `[ ]` 改为 `[x]`。");
+        lines.push("> 每页应产出 Markdown 文件到对应 `Output` 路径，内容严格基于基线源码。");
+        lines.push("");
+        lines.push("> **源码引用规范（强制，与 --generate-wiki 产出口径保持一致）**：");
+        lines.push("> 所有源码链接必须指向 `baseline/code/` 下的路径，允许两种写法（可混用）：");
+        lines.push("> 1. 行内链接：`[Foo.java:10-30](../../baseline/code/<repo-relative>/Foo.java#L10-L30)`");
+        lines.push("> 2. Sources 行：`Sources: <repo-relative>/Foo.java:10-30, <repo-relative>/Bar.kt:5-8`");
+        lines.push("> `<repo-relative>` 指**相对 `baseline/code/` 的路径**，既非仓库原始绝对路径，");
+        lines.push("> 也非 wiki md 文件的相对路径。行号使用 `start-end`（闭区间）。");
+    }
+    else {
+        lines.push("> 本 wiki 面向**人类开发者**阅读与维护。");
+        lines.push("> 按 Pages 列表逐页撰写或完善 Markdown，每完成一页把 `[ ]` 改为 `[x]`。");
+        lines.push("> 每页应产出到对应 `Output` 路径，内容严格基于源码目录。");
+        lines.push("");
+        lines.push("> **源码引用规范**：");
+        lines.push("> 使用 `Sources: <repo-relative>/path:line-range` 或行内链接指向源码树中的真实文件。");
+        lines.push("> `<repo-relative>` 相对 Source tree（见上文）。");
+    }
     lines.push("");
+    return lines;
+}
+function renderAcceptance(audience, sourceRootRel) {
+    const lines = [];
+    lines.push(`- Acceptance:`);
+    lines.push(`  - 文件存在且非空`);
+    lines.push(`  - 首段含页面标题（H1 与 title 一致）`);
+    lines.push(`  - 至少引用 1 个 Relevant files 中的源码片段或路径`);
+    if (audience === "agent") {
+        lines.push(`  - Sources 行或行内链接的路径必须定位到 \`baseline/code/\` 下的真实文件`);
+        lines.push(`  - 含 \`## 阅读时机\` 且至少 1 条可执行 bullet`);
+        lines.push(`  - 含 \`## 关键路径\` 表格，且覆盖 Relevant files 中 ≥1 个路径`);
+        lines.push(`  - 含 \`## 约定与禁区\`（可为「暂无额外禁区」但章节必须存在）`);
+        lines.push(`  - H1 下须有 \`Sources:\` 行`);
+        lines.push(`  - 正文以表格/bullet 为主，单段 prose 不超过 5 行（除代码块外）`);
+    }
+    else {
+        const srcHint = sourceRootRel === "." ? "源码树" : `\`${sourceRootRel}\``;
+        lines.push(`  - Sources 行或行内链接的路径必须定位到 ${srcHint} 下的真实文件`);
+        lines.push(`  - 简介段后若有 2 个及以上 \`##\` 章节，插入锚点式 TOC`);
+    }
+    return lines;
+}
+function renderTasksMarkdown(input) {
+    const { outline } = input;
+    const audience = input.wikiAudience ?? "human";
+    const lines = [...renderHeaderBlock(input, audience)];
+    const groups = groupBySection(outline.pages);
     lines.push("## Sections");
     for (const g of groups) {
         const ids = g.pages.map((p) => p.id).join(", ");
@@ -103,15 +143,12 @@ function renderTasksMarkdown(input) {
             }
         }
         else {
-            lines.push(`- Relevant files: _(none declared — agent should infer from tree)_`);
+            lines.push(`- Relevant files: _(none declared — ${audience === "agent" ? "agent" : "author"} should infer from tree)_`);
         }
-        lines.push(`- Acceptance:`);
-        lines.push(`  - 文件存在且非空`);
-        lines.push(`  - 首段含页面标题（H1 与 title 一致）`);
-        lines.push(`  - 至少引用 1 个 Relevant files 中的源码片段或路径`);
-        lines.push(`  - Sources 行或行内链接的路径必须定位到 \`baseline/code/\` 下的真实文件`);
+        lines.push(...renderAcceptance(audience, input.sourceRootRel));
+        lines.push("");
     }
-    return lines.join("\n");
+    return lines.join("\n").trimEnd() + "\n";
 }
 /**
  * Write `TASKS.md` under the wiki base directory and return the absolute path.