superlab 0.1.13 → 0.1.15

package/lib/i18n.cjs

@@ -61,7 +61,7 @@ const ZH_CONTENT = {
   [path.join(".codex", "prompts", "lab-write.md")]: codexPrompt(
     "把验证过的研究工件转成论文 section，并按小步方式修订",
     "section or writing target",
-    "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:write`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:write` 阶段。它必须先有来自 `/lab:framing` 的已批准 framing artifact，再读取 `.codex/skills/lab/references/paper-writing/` 下与当前 section 对应的参考文件，并结合 `paper-review.md` 与 `does-my-writing-flow-source.md`，先写 mini-outline，再只修改一个 section。"
+    "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:write`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:write` 阶段。它必须先有来自 `/lab:framing` 的已批准 framing artifact，再读取 `.codex/skills/lab/references/paper-writing/` 下与当前 section 对应的参考文件；如果当前是 `abstract`、`introduction` 或 `method`，还必须继续读取 `.codex/skills/lab/references/paper-writing/examples/index.md`、对应的 examples index，以及 1-2 个具体 example 文件。然后结合 `paper-review.md` 与 `does-my-writing-flow-source.md`，先写 mini-outline，再只修改一个 section。第一次进入会产出论文 `.tex` 的路径时，如果 `paper_template_root` 为空，必须先问一次：继续使用默认 LaTeX scaffold，还是先接入模板目录。"
   ),
   [path.join(".claude", "commands", "lab", "idea.md")]: claudeCommand(
     "LAB: Idea",
@@ -109,7 +109,7 @@ const ZH_CONTENT = {
     "LAB: Write",
     "把验证过的研究工件转成论文 section，并按小步方式修订",
     "workflow, research, writing",
-    "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:write`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:write` 阶段。它必须先有来自 `/lab:framing` 的已批准 framing artifact，再读取 `.claude/skills/lab/references/paper-writing/` 下与当前 section 对应的参考文件，并结合 `paper-review.md` 与 `does-my-writing-flow-source.md`，先写 mini-outline，再只修改一个 section。"
+    "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:write`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:write` 阶段。它必须先有来自 `/lab:framing` 的已批准 framing artifact，再读取 `.claude/skills/lab/references/paper-writing/` 下与当前 section 对应的参考文件；如果当前是 `abstract`、`introduction` 或 `method`，还必须继续读取 `.claude/skills/lab/references/paper-writing/examples/index.md`、对应的 examples index，以及 1-2 个具体 example 文件。然后结合 `paper-review.md` 与 `does-my-writing-flow-source.md`，先写 mini-outline，再只修改一个 section。第一次进入会产出论文 `.tex` 的路径时，如果 `paper_template_root` 为空，必须先问一次：继续使用默认 LaTeX scaffold，还是先接入模板目录。"
   ),
 };
 
@@ -291,8 +291,10 @@ const ZH_SKILL_FILES = {
 ## 必要输出
 
 - 方法概述
+- 选定指标摘要
 - 实验设置
 - 已验证主结果
+- 位于 \`<deliverables_root>/main-tables.md\` 的受管主表工件
 - 消融
 - 失败尝试
 - 局限性
@@ -317,13 +319,15 @@ const ZH_SKILL_FILES = {
 - 每个主要 claim 都要指向已记录的 summary 或 iteration artifact。
 - 主表结构、gate 和最终结果 framing 必须对齐已批准的评估协议。
 - 不要凭记忆重述指标定义、baseline 行为或对比方法实现；直接引用评估协议里记录的来源。
+- 必须把已批准的主指标、次级指标和必要终局证据明确写进 \`report.md\` 与受管的 \`main-tables.md\`。
 - 如果报告依赖了对原始指标或原始实现的偏差，必须明确写出这个偏差。
+- 如果 workflow language 是中文，\`report.md\` 和 \`<deliverables_root>/main-tables.md\` 也应使用中文，除非文件路径、代码标识符或字面指标名必须保持原样。
 - 解释优先保守，不要写成营销文案。
 - 要给 \`/lab:write\` 留下清晰 handoff，尤其是 section draft 可以直接引用的证据链接。
 
 ## 交互约束
 
-- 开始前先简洁说明：campaign outcome、最强已支撑 claim、最大的报告风险。
+- 开始前先简洁说明：campaign outcome、选定的主指标和次级指标、最强已支撑 claim、最大的报告风险。
 - 如果某个未决前提会改变报告解释，一次只问一个问题。
 - 如果存在多种报告 framing，先给 2-3 个方案、trade-offs 和推荐项，优先最忠于证据的 framing。
 - 如果某种 framing 会实质影响后续论文 claim，要保留 approval gate。
@@ -679,27 +683,78 @@ const ZH_SKILL_FILES = {
 - 方差和显著性问题是否交代清楚？
 `,
   [path.join(".lab", ".managed", "templates", "final-report.md")]:
-`# Final Report
+`# 最终报告
 
 ## 目标
 
 - 本轮研究目标：
 - 是否达标：
 
+## 选定指标
+
+- 主指标：
+- 次级指标：
+- 必要终局证据：
+
+## 主表工件
+
+- 受管主表路径：\`<deliverables_root>/main-tables.md\`
+- 最终表现摘要：
+- 主表覆盖情况：
+
 ## 主要结果
 
-- Main finding 1:
-- Main finding 2:
+- 主要发现 1：
+- 主要发现 2：
 
 ## 失败尝试与局限
 
-- Failed attempt:
-- Limitation:
+- 失败尝试：
+- 局限：
 
 ## 仍需加强的 claims
 
-- Claim:
-- Missing support:
+- Claim：
+- 缺失支持：
+`,
+  [path.join(".lab", ".managed", "templates", "main-tables.md")]:
+`# 主表工件
+
+## 选定指标
+
+- 主指标：
+- 次级指标：
+- 必要终局证据：
+
+## 最终表现摘要
+
+- 主要结果摘要：
+- 最重要数字：
+- 报告边界：
+
+## Table 1
+
+- 作用：
+- 使用指标：
+- 最强支撑 claim：
+
+## Table 2
+
+- 作用：
+- 使用指标：
+- 最强支撑 claim：
+
+## Table 3
+
+- 作用：
+- 使用指标：
+- 最强支撑 claim：
+
+## Table 4
+
+- 作用：
+- 使用指标：
+- 最强支撑 claim：
 `,
   [path.join(".lab", ".managed", "templates", "paper-plan.md")]:
 `# 论文计划
@@ -829,7 +884,9 @@ const ZH_SKILL_FILES = {
   "results_root": "results",
   "figures_root": "figures",
   "deliverables_root": "docs/research",
-  "paper_template_root": ""
+  "paper_template_root": "",
+  "paper_template_decision": "unconfirmed",
+  "paper_template_final_reminder_acknowledged": false
 }`,
   [path.join(".lab", "context", "mission.md")]:
 `# 研究主线
@@ -934,12 +991,16 @@ const ZH_SKILL_FILES = {
 
 - Objective:
 - Autonomy level: L2
+- Autonomy level 只表示执行权限级别，不表示论文 layer 或 table 编号。
+- 如果你想表达论文层、实验 phase 或主表，请明确写成 \`paper layer\`、\`phase\` 或 \`table\`。
 - Approval status: draft
 - Allowed stages: run, iterate, review, report
 - Success criteria:
 - Terminal goal type:
 - Terminal goal target:
 - Required terminal artifact:
+- 如果 workflow language 是中文，摘要、清单条目、任务标签和进度更新都应使用中文。
+- 示例 Objective: 推进 paper layer 3 的 organizer enforcement，完成一轮 bounded protocol、测试、最小实现和一轮小规模结果。
 
 ## 循环预算
 
@@ -950,6 +1011,9 @@ const ZH_SKILL_FILES = {
 
 ## 阶段命令
 
+- Rung 的 \`Command\` 应该绑定真实的长任务命令，由它产出最终实验结果。
+- 短 watcher 只用于查看进度；当真实实验还在运行时，不要把短 watcher 当成 stage 或 rung 的主命令。
+- 当真实实验进程还活着时，只记录进度更新并继续等待。
 - Run command:
 - Iterate command:
 - Review command:
@@ -988,30 +1052,33 @@ const ZH_SKILL_FILES = {
 
 ## 目标
 
-- Objective:
-- Experiment ladder:
-- Metric glossary:
-- Metric source papers:
-- Metric implementation source:
-- Comparison source papers:
-- Comparison implementation source:
-- Deviation from original implementation:
-- Terminal goal type:
-- Terminal goal target:
-- Required terminal artifact:
+- 目标:
+- 主指标:
+- 次级指标:
+- 必要终局证据:
+- 实验阶梯:
+- 指标释义:
+- 指标来源论文:
+- 指标实现来源:
+- 对比方法来源论文:
+- 对比方法实现来源:
+- 与原始实现的偏差:
+- 终止目标类型:
+- 终止目标目标值:
+- 必要终止工件:
 
 ## 结果
 
-- Status: idle
-- Goal reached: no
-- Stop reason:
-- Promotion applied: no
-- Final artifact:
-- Final rung:
-- Executed stages:
-- Iterations completed: 0
-- Started at:
-- Finished at:
+- 状态: idle
+- 目标是否达成: 否
+- 停止原因:
+- 是否已升格: 否
+- 最终工件:
+- 最终 rung:
+- 已执行阶段:
+- 已完成迭代数: 0
+- 开始时间:
+- 结束时间:
 `,
   [path.join(".lab", "context", "auto-status.md")]:
 `# 自动模式状态
@@ -1292,8 +1359,15 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "write.md")] = `# \`/l
 - 最终稿必须是 LaTeX。
 - 如果配置了 \`paper_template_root\`，先检查该模板目录，再按其结构起草论文。
 - 已接入的模板目录可能包含用户或上游修改，默认不要改模板文件。
-- 如果没有配置模板，就使用交付目录下的默认 LaTeX scaffold。
+- 如果没有配置模板且 \`paper_template_decision\` 是 \`unconfirmed\`，在第一次起草 \`.tex\` 之前必须先追问一次：继续使用默认 LaTeX scaffold，还是先接入模板目录。
+- 如果用户选择默认 scaffold，就把该决定持久化到 \`.lab/config/workflow.json\`，写成 \`paper_template_decision: default-scaffold\`。
+- 如果用户选择接入模板，就停止当前写作回合，先转到 \`superlab paper attach-template --path <dir>\`。
+- 如果 \`paper_template_decision\` 已经是 \`default-scaffold\`，就使用交付目录下的默认 LaTeX scaffold。
+- 如果当前是最终导出或最终定稿轮次、\`paper_template_root\` 仍为空、\`paper_template_decision\` 是 \`default-scaffold\`，且 \`paper_template_final_reminder_acknowledged\` 是 \`false\`，就在最终定稿前再提醒一次是否切到模板。
+- 如果用户在最终提醒里仍确认继续使用默认 scaffold，就把 \`paper_template_final_reminder_acknowledged\` 持久化为 \`true\`。
 - 只加载当前 section guide，不要一次加载全部章节参考。
+- 如果当前 section 是 \`abstract\`、\`introduction\` 或 \`method\`，还必须继续读取本地 example bank：\`references/paper-writing/examples/index.md\`、对应的 examples index，以及 1-2 个具体 example 文件。
+- 例子只能复用结构、段落角色和句法逻辑，不能直接复用原句。
 - 先写 mini-outline 再写 prose。
 - 如果缺少 framing artifact，不要继续写作，直接回到 \`/lab:framing\`。
 - 如果某个 claim 没有证据支撑，就削弱或删除。
@@ -1383,7 +1457,7 @@ ZH_CONTENT[path.join(".lab", ".managed", "templates", "framing.md")] = `# 论文
 ZH_CONTENT[path.join(".codex", "prompts", "lab.md")] = codexPrompt(
   "查看 /lab 研究工作流总览并选择合适阶段",
   "workflow question 或 stage choice",
-  "# `/lab` for Codex\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:data`\n  把已批准的 idea 转成数据集与 benchmark 方案，记录数据集年份、使用过该数据集的论文、下载来源、许可或访问限制，以及 classic-public、recent-strong-public、claim-specific 三类 benchmark 的纳入理由，和 canonical baselines、strong historical baselines、recent strong public methods、closest prior work 四类对比方法的纳入理由。\n\n- `/lab:auto`\n  在不改变 mission、framing 和核心 claims 的前提下，读取 eval-protocol 与 auto-mode 契约并自动编排 `run`、`iterate`、`review`、`report`，必要时扩展数据集、benchmark 和 comparison methods，并在满足升格策略时自动升级 primary package。启动前必须选定 autonomy level、声明 terminal goal，并显式批准契约。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:spec` 前应已有经批准的数据集与 benchmark 方案。\n- `/lab:run`、`/lab:iterate`、`/lab:auto`、`/lab:report` 都应遵循 `.lab/context/eval-protocol.md`。\n- `.lab/context/eval-protocol.md` 不只定义主指标和主表，也应定义指标释义、实验阶梯，以及指标和对比实现的来源。\n- `/lab:auto` 只编排已批准边界内的执行阶段，不替代手动的 idea/data/framing/spec 决策。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n"
+  "# `/lab` for Codex\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:data`\n  把已批准的 idea 转成数据集与 benchmark 方案，记录数据集年份、使用过该数据集的论文、下载来源、许可或访问限制，以及 classic-public、recent-strong-public、claim-specific 三类 benchmark 的纳入理由，和 canonical baselines、strong historical baselines、recent strong public methods、closest prior work 四类对比方法的纳入理由。\n\n- `/lab:auto`\n  在不改变 mission、framing 和核心 claims 的前提下，读取 eval-protocol 与 auto-mode 契约并自动编排 `run`、`iterate`、`review`、`report`，必要时扩展数据集、benchmark 和 comparison methods，并在满足升格策略时自动升级 primary package。启动前必须选定 autonomy level、声明 terminal goal，并显式批准契约。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:spec` 前应已有经批准的数据集与 benchmark 方案。\n- `/lab:run`、`/lab:iterate`、`/lab:auto`、`/lab:report` 都应遵循 `.lab/context/eval-protocol.md`。\n- `.lab/context/eval-protocol.md` 不只定义主指标和主表，也应定义指标释义、实验阶梯，以及指标和对比实现的来源。\n- `/lab:auto` 只编排已批准边界内的执行阶段，不替代手动的 idea/data/framing/spec 决策。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n\n## 如何输入 `/lab:auto`\n\n- 把 `Autonomy level L1/L2/L3` 视为执行权限级别，不要和论文里的 layer、phase、table 编号混用。\n- 把 `paper layer`、`phase`、`table` 视为实验目标。例如 `paper layer 3` 或 `Phase 1 reviewer fidelity` 不是 `Autonomy level L3`。\n- 一条好的 `/lab:auto` 输入应至少说清：objective、自治级别、terminal goal、scope、allowed modifications。\n- 如果 workflow language 是中文，摘要、清单条目、任务标签和进度更新都应使用中文，除非文件路径、代码标识符或字面指标名必须保持原样。\n- 示例：`/lab:auto 自治级别 L2。目标：推进 paper layer 3 的 organizer enforcement。终止条件：完成 bounded protocol、测试、最小实现和一轮小规模结果。允许修改：evaluator prompt registry、ingestion、parser。`\n"
 );
 
 ZH_CONTENT[path.join(".codex", "prompts", "lab-data.md")] = codexPrompt(
@@ -1395,14 +1469,14 @@ ZH_CONTENT[path.join(".codex", "prompts", "lab-data.md")] = codexPrompt(
 ZH_CONTENT[path.join(".codex", "prompts", "lab-auto.md")] = codexPrompt(
   "在已批准边界内编排自动实验循环",
   "auto mode objective",
-  "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:auto`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:auto` 阶段。它必须读取 `.lab/context/eval-protocol.md`、`.lab/context/auto-mode.md`、`.lab/context/auto-status.md` 与 `.lab/context/auto-outcome.md`，先确认 autonomy level、approval status 与 terminal goal schema，再把 eval-protocol 里的指标释义、主表计划、来源约束与结构化实验阶梯当作执行依据，在不修改 mission、framing 和核心 claims 的前提下编排已批准的 `run`、`iterate`、`review`、`report`，轮询长任务完成情况；如果声明了 rung，就保持会话活着并按 rung 转移继续推进。"
+  "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:auto`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:auto` 阶段。它必须读取 `.lab/context/eval-protocol.md`、`.lab/context/auto-mode.md`、`.lab/context/auto-status.md` 与 `.lab/context/auto-outcome.md`，先确认 autonomy level、approval status 与 terminal goal schema，再把 eval-protocol 里的指标释义、主表计划、来源约束与结构化实验阶梯当作执行依据，在不修改 mission、framing 和核心 claims 的前提下编排已批准的 `run`、`iterate`、`review`、`report`，轮询长任务完成情况；如果声明了 rung，就保持会话活着并按 rung 转移继续推进。\n如果仓库的 workflow language 是中文，摘要、清单条目、任务标签和进度更新都必须使用中文，除非某个文件路径、代码标识符或字面指标名必须保持原样。\n把 `Layer 3`、`Phase 1`、`Table 2` 这类表达视为论文范围目标；只有显式写成 `Autonomy level L3` 或 `自治级别 L3` 时，才把它当成执行权限级别。\n不要用 `sleep 30`、单次 `pgrep` 或一次性的 `metrics.json` 探针来代替真实长任务命令；当真实实验进程还活着时，只允许发进度更新并继续等待。"
 );
 
 ZH_CONTENT[path.join(".claude", "commands", "lab.md")] = claudeCommand(
   "LAB",
   "查看 /lab 研究工作流总览并选择合适阶段",
   "workflow, research, overview",
-  "# `/lab` for Claude\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:data`\n  把已批准的 idea 转成数据集与 benchmark 方案，记录数据集年份、使用过该数据集的论文、下载来源、许可或访问限制，以及 classic-public、recent-strong-public、claim-specific 三类 benchmark 的纳入理由，和 canonical baselines、strong historical baselines、recent strong public methods、closest prior work 四类对比方法的纳入理由。\n\n- `/lab:auto`\n  在不改变 mission、framing 和核心 claims 的前提下，读取 eval-protocol 与 auto-mode 契约并自动编排 `run`、`iterate`、`review`、`report`，必要时扩展数据集、benchmark 和 comparison methods，并在满足升格策略时自动升级 primary package。启动前必须选定 autonomy level、声明 terminal goal，并显式批准契约。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:spec` 前应已有经批准的数据集与 benchmark 方案。\n- `/lab:run`、`/lab:iterate`、`/lab:auto`、`/lab:report` 都应遵循 `.lab/context/eval-protocol.md`。\n- `.lab/context/eval-protocol.md` 不只定义主指标和主表，也应定义指标释义、实验阶梯，以及指标和对比实现的来源。\n- `/lab:auto` 只编排已批准边界内的执行阶段，不替代手动的 idea/data/framing/spec 决策。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n"
+  "# `/lab` for Claude\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:data`\n  把已批准的 idea 转成数据集与 benchmark 方案，记录数据集年份、使用过该数据集的论文、下载来源、许可或访问限制，以及 classic-public、recent-strong-public、claim-specific 三类 benchmark 的纳入理由，和 canonical baselines、strong historical baselines、recent strong public methods、closest prior work 四类对比方法的纳入理由。\n\n- `/lab:auto`\n  在不改变 mission、framing 和核心 claims 的前提下，读取 eval-protocol 与 auto-mode 契约并自动编排 `run`、`iterate`、`review`、`report`，必要时扩展数据集、benchmark 和 comparison methods，并在满足升格策略时自动升级 primary package。启动前必须选定 autonomy level、声明 terminal goal，并显式批准契约。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:spec` 前应已有经批准的数据集与 benchmark 方案。\n- `/lab:run`、`/lab:iterate`、`/lab:auto`、`/lab:report` 都应遵循 `.lab/context/eval-protocol.md`。\n- `.lab/context/eval-protocol.md` 不只定义主指标和主表，也应定义指标释义、实验阶梯，以及指标和对比实现的来源。\n- `/lab:auto` 只编排已批准边界内的执行阶段，不替代手动的 idea/data/framing/spec 决策。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n\n## 如何输入 `/lab:auto`\n\n- 把 `Autonomy level L1/L2/L3` 视为执行权限级别，不要和论文里的 layer、phase、table 编号混用。\n- 把 `paper layer`、`phase`、`table` 视为实验目标。例如 `paper layer 3` 或 `Phase 1 reviewer fidelity` 不是 `Autonomy level L3`。\n- 一条好的 `/lab:auto` 输入应至少说清：objective、自治级别、terminal goal、scope、allowed modifications。\n- 如果 workflow language 是中文，摘要、清单条目、任务标签和进度更新都应使用中文，除非文件路径、代码标识符或字面指标名必须保持原样。\n- 示例：`/lab:auto 自治级别 L2。目标：推进 paper layer 3 的 organizer enforcement。终止条件：完成 bounded protocol、测试、最小实现和一轮小规模结果。允许修改：evaluator prompt registry、ingestion、parser。`\n"
 );
 
 ZH_CONTENT[path.join(".claude", "commands", "lab", "data.md")] = claudeCommand(
@@ -1416,7 +1490,7 @@ ZH_CONTENT[path.join(".claude", "commands", "lab", "auto.md")] = claudeCommand(
   "LAB: Auto",
   "在已批准边界内编排自动实验循环",
   "workflow, research, auto",
-  "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:auto`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:auto` 阶段。它必须读取 `.lab/context/eval-protocol.md`、`.lab/context/auto-mode.md`、`.lab/context/auto-status.md` 与 `.lab/context/auto-outcome.md`，先确认 autonomy level、approval status 与 terminal goal schema，再把 eval-protocol 里的指标释义、主表计划、来源约束与结构化实验阶梯当作执行依据，在不修改 mission、framing 和核心 claims 的前提下编排已批准的 `run`、`iterate`、`review`、`report`，轮询长任务完成情况；如果声明了 rung，就保持会话活着并按 rung 转移继续推进。"
+  "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:auto`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:auto` 阶段。它必须读取 `.lab/context/eval-protocol.md`、`.lab/context/auto-mode.md`、`.lab/context/auto-status.md` 与 `.lab/context/auto-outcome.md`，先确认 autonomy level、approval status 与 terminal goal schema，再把 eval-protocol 里的指标释义、主表计划、来源约束与结构化实验阶梯当作执行依据，在不修改 mission、framing 和核心 claims 的前提下编排已批准的 `run`、`iterate`、`review`、`report`，轮询长任务完成情况；如果声明了 rung，就保持会话活着并按 rung 转移继续推进。\n如果仓库的 workflow language 是中文，摘要、清单条目、任务标签和进度更新都必须使用中文，除非某个文件路径、代码标识符或字面指标名必须保持原样。\n把 `Layer 3`、`Phase 1`、`Table 2` 这类表达视为论文范围目标；只有显式写成 `Autonomy level L3` 或 `自治级别 L3` 时，才把它当成执行权限级别。\n不要用 `sleep 30`、单次 `pgrep` 或一次性的 `metrics.json` 探针来代替真实长任务命令；当真实实验进程还活着时，只允许发进度更新并继续等待。"
 );
 
 ZH_CONTENT[path.join(".codex", "skills", "lab", "SKILL.md")] = `---
@@ -1939,6 +2013,17 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "auto.md")] = `# \`/la
 - 如果契约本身不完整，一次只追问一个问题。
 - 如果存在多个可信的下一动作，先给 2-3 个 bounded 方案和推荐项，再启动长任务。
 - 只有当下一步会离开已批准的 exploration envelope、超出选定 autonomy level，或实质改变 frozen core 时，才保留人工 approval gate。
+- 先做输入归一化：把 \`Autonomy level L1/L2/L3\` 视为执行权限级别，把 \`Layer 3\`、\`Phase 1\`、\`Table 2\` 视为论文范围目标。
+- 如果用户同时提了论文层、实验 phase 和自治级别，先用一句话重述：objective、自治级别、terminal goal、scope、allowed modifications。
+- 如果 workflow language 是中文，摘要、清单条目、任务标签和进度更新都应使用中文，除非文件路径、代码标识符或字面指标名必须保持原样。
+- 当循环即将进入 \`write\`，且 \`paper_template_root\` 为空时：
+  - 如果 \`paper_template_decision\` 是 \`unconfirmed\`，必须先追问一次：继续使用默认 scaffold，还是先接入模板目录
+  - 如果用户选择默认 scaffold，就持久化 \`paper_template_decision: default-scaffold\`
+  - 如果用户选择模板，就停止当前循环并转到 \`superlab paper attach-template --path <dir>\`
+  - 如果当前是最终导出或最终定稿、\`paper_template_decision\` 是 \`default-scaffold\`，且 \`paper_template_final_reminder_acknowledged\` 是 \`false\`，就在最终定稿前再提醒一次
+  - 如果用户在最终提醒里仍确认继续使用默认 scaffold，就持久化 \`paper_template_final_reminder_acknowledged: true\`
+- 不要把 \`sleep 30\`、单次 \`pgrep\` 或一次性的 \`metrics.json\` 探针当成 rung 主命令；这些只能算进度检查。
+- 当真实实验进程还活着时，只允许发进度更新并继续等待，不能把这一 rung 当作已经完成。
 `;
 
 ZH_CONTENT[path.join(".claude", "skills", "lab", "stages", "auto.md")] =

package/lib/install.cjs

@@ -538,6 +538,7 @@ function localizeInstalledAssets(targetDir, lang, { newlyCreatedProjectOwnedPath
     path.join(".lab", ".managed", "templates", "iteration-report.md"),
     path.join(".lab", ".managed", "templates", "review-checklist.md"),
     path.join(".lab", ".managed", "templates", "final-report.md"),
+    path.join(".lab", ".managed", "templates", "main-tables.md"),
     path.join(".lab", ".managed", "templates", "paper-plan.md"),
     path.join(".lab", ".managed", "templates", "paper-section.md"),
     path.join(".lab", ".managed", "templates", "write-iteration.md"),

package/package-assets/claude/commands/lab/auto.md

@@ -9,3 +9,6 @@ Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:auto` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 This command runs the `/lab:auto` stage. It must read `.lab/context/eval-protocol.md`, `.lab/context/auto-mode.md`, `.lab/context/auto-status.md`, and `.lab/context/auto-outcome.md`, enforce the declared terminal goal schema, orchestrate approved run, iterate, review, and report stages inside that contract, poll long-running work until completion or stop conditions, and write progress plus the final outcome back into `.lab/context/auto-status.md` and `.lab/context/auto-outcome.md`.
+When the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a literal identifier must stay unchanged.
+Treat `Layer 3`, `Phase 1`, or `Table 2` as paper-scope targets. Treat `Autonomy level L3` as the execution permission level.
+Do not replace the real long-running experiment command with a short watcher such as `sleep 30`, `pgrep`, or a one-shot `metrics.json` probe. While the real experiment process is still alive, emit only a progress update and keep waiting.

package/package-assets/claude/commands/lab/write.md

@@ -8,4 +8,4 @@ tags: [workflow, research, writing]
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
-This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.claude/skills/lab/references/paper-writing/`, plus `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, and then revise only one section.
+This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.claude/skills/lab/references/paper-writing/`, and for `abstract`, `introduction`, or `method` it must also read `.claude/skills/lab/references/paper-writing/examples/index.md` plus the matching examples index and 1-2 concrete example files. Then it should run `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, and revise only one section.

package/package-assets/claude/commands/lab.md

@@ -40,6 +40,7 @@ tags: [workflow, research, overview]
 
 - `/lab:write`
   Turn stable report artifacts into paper sections through small, evidence-bound writing rounds using the vendored paper-writing references under the installed `lab` skill.
+  On the first manuscript-writing round, if `paper_template_root` is empty, explicitly ask once whether to stay on the managed default LaTeX scaffold or attach a template directory first; persist the user's default-scaffold choice before continuing.
 
 ## Dispatch Rules
 
@@ -54,3 +55,17 @@ tags: [workflow, research, overview]
 - `/lab:run`, `/lab:iterate`, `/lab:auto`, and `/lab:report` should all follow `.lab/context/eval-protocol.md`, including its recorded sources for metrics and comparison implementations.
 - `/lab:write` requires an approved framing artifact from `/lab:framing`.
 - `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+
+## How to Ask for `/lab:auto`
+
+- Treat `Autonomy level L1/L2/L3` as the execution privilege level, not as a paper layer, phase, or table number.
+- Treat `paper layer`, `phase`, and `table` as experiment targets. For example, `paper layer 3` or `Phase 1 reviewer fidelity` should not be interpreted as `Autonomy level L3`.
+- A good `/lab:auto` request should name:
+  - the objective
+  - the autonomy level
+  - the terminal goal
+  - the scope or phase to advance
+  - the allowed modifications
+- If the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a code identifier or file path must stay literal.
+- Good example:
+  - `/lab:auto Autonomy level L2. Objective: advance paper layer 3 organizer enforcement. Terminal goal: task-completion. Scope: bounded protocol, tests, minimal implementation, and one small run. Allowed modifications: evaluator prompt registry, ingestion, and parser only.`

package/package-assets/codex/prompts/lab-auto.md

@@ -7,3 +7,6 @@ Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:auto` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
 This command runs the `/lab:auto` stage. It must read `.lab/context/eval-protocol.md`, `.lab/context/auto-mode.md`, `.lab/context/auto-status.md`, and `.lab/context/auto-outcome.md`, enforce the declared terminal goal schema, orchestrate approved run, iterate, review, and report stages inside that contract, poll long-running work until completion or stop conditions, and write progress plus the final outcome back into `.lab/context/auto-status.md` and `.lab/context/auto-outcome.md`.
+When the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a literal identifier must stay unchanged.
+Treat `Layer 3`, `Phase 1`, or `Table 2` as paper-scope targets. Treat `Autonomy level L3` as the execution permission level.
+Do not replace the real long-running experiment command with a short watcher such as `sleep 30`, `pgrep`, or a one-shot `metrics.json` probe. While the real experiment process is still alive, emit only a progress update and keep waiting.

package/package-assets/codex/prompts/lab-write.md

@@ -6,4 +6,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
-This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.codex/skills/lab/references/paper-writing/`, plus `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, and then revise only one section.
+This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.codex/skills/lab/references/paper-writing/`, and for `abstract`, `introduction`, or `method` it must also read `.codex/skills/lab/references/paper-writing/examples/index.md` plus the matching examples index and 1-2 concrete example files. Then it should run `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, and revise only one section.

package/package-assets/codex/prompts/lab.md

@@ -38,6 +38,7 @@ argument-hint: workflow question or stage choice
 
 - `/lab:write`
   Turn stable report artifacts into paper sections through small, evidence-bound writing rounds using the vendored paper-writing references under the installed `lab` skill.
+  On the first manuscript-writing round, if `paper_template_root` is empty, explicitly ask once whether to stay on the managed default LaTeX scaffold or attach a template directory first; persist the user's default-scaffold choice before continuing.
 
 ## Dispatch Rules
 
@@ -52,3 +53,17 @@ argument-hint: workflow question or stage choice
 - `/lab:run`, `/lab:iterate`, `/lab:auto`, and `/lab:report` should all follow `.lab/context/eval-protocol.md`, including its recorded sources for metrics and comparison implementations.
 - `/lab:write` requires an approved framing artifact from `/lab:framing`.
 - `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+
+## How to Ask for `/lab:auto`
+
+- Treat `Autonomy level L1/L2/L3` as the execution privilege level, not as a paper layer, phase, or table number.
+- Treat `paper layer`, `phase`, and `table` as experiment targets. For example, `paper layer 3` or `Phase 1 reviewer fidelity` should not be interpreted as `Autonomy level L3`.
+- A good `/lab:auto` request should name:
+  - the objective
+  - the autonomy level
+  - the terminal goal
+  - the scope or phase to advance
+  - the allowed modifications
+- If the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a code identifier or file path must stay literal.
+- Good example:
+  - `/lab:auto Autonomy level L2. Objective: advance paper layer 3 organizer enforcement. Terminal goal: task-completion. Scope: bounded protocol, tests, minimal implementation, and one small run. Allowed modifications: evaluator prompt registry, ingestion, and parser only.`

package/package-assets/shared/lab/.managed/templates/final-report.md

@@ -4,6 +4,12 @@
 
 Summarize the method and overall outcome.
 
+## Selected Metrics
+
+- Primary metrics:
+- Secondary metrics:
+- Required terminal evidence:
+
 ## Experiment Setup
 
 - Datasets:
@@ -11,6 +17,12 @@ Summarize the method and overall outcome.
 - Baselines:
 - Metrics:
 
+## Main Tables
+
+- Managed main tables artifact: `<deliverables_root>/main-tables.md`
+- Final performance summary:
+- Table coverage:
+
 ## Main Results
 
 Summarize validated iteration outcomes.

package/package-assets/shared/lab/.managed/templates/main-tables.md

@@ -0,0 +1,37 @@
+# Main Tables
+
+## Selected Metrics
+
+- Primary metrics:
+- Secondary metrics:
+- Required terminal evidence:
+
+## Final Performance Summary
+
+- Main result summary:
+- Most important numbers:
+- Reporting caveat:
+
+## Table 1
+
+- Purpose:
+- Metrics used:
+- Strongest supported claim:
+
+## Table 2
+
+- Purpose:
+- Metrics used:
+- Strongest supported claim:
+
+## Table 3
+
+- Purpose:
+- Metrics used:
+- Strongest supported claim:
+
+## Table 4
+
+- Purpose:
+- Metrics used:
+- Strongest supported claim:

package/package-assets/shared/lab/config/workflow.json

@@ -5,5 +5,7 @@
   "results_root": "results",
   "figures_root": "figures",
   "deliverables_root": "docs/research",
-  "paper_template_root": ""
+  "paper_template_root": "",
+  "paper_template_decision": "unconfirmed",
+  "paper_template_final_reminder_acknowledged": false
 }

package/package-assets/shared/lab/context/auto-mode.md

@@ -6,14 +6,18 @@ If `eval-protocol.md` declares structured rung entries, auto mode follows those
 
 ## Objective
 
-- Objective:
+- Objective: 
 - Autonomy level: L2
+- Autonomy level controls execution privilege, not paper layer or table number.
+- If you mean a paper layer, phase, or table, spell it explicitly as `paper layer`, `phase`, or `table`.
 - Approval status: draft
 - Allowed stages: run, iterate, review, report
 - Success criteria:
 - Terminal goal type:
 - Terminal goal target:
 - Required terminal artifact:
+- If the workflow language is Chinese, keep summaries, checklist items, task labels, and progress updates in Chinese.
+- Example objective: advance paper layer 3 organizer enforcement through one bounded protocol, tests, minimal implementation, and one small run.
 
 ## Loop Budget
 
@@ -24,6 +28,9 @@ If `eval-protocol.md` declares structured rung entries, auto mode follows those
 
 ## Stage Commands
 
+- Rung `Command` should be the real long-running command that owns the experiment result.
+- A short watcher is only a progress probe. Do not use a short watcher as the stage or rung command when the real experiment is still running.
+- While the real experiment process is still alive, only record a progress update and keep waiting.
 - Run command:
 - Iterate command:
 - Review command:

package/package-assets/shared/lab/context/auto-outcome.md

@@ -3,6 +3,9 @@
 ## Goal
 
 - Objective:
+- Primary metrics:
+- Secondary metrics:
+- Required terminal evidence:
 - Experiment ladder:
 - Metric glossary:
 - Metric source papers:

package/package-assets/shared/skills/lab/SKILL.md

@@ -151,7 +151,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Read `.lab/context/eval-protocol.md` before choosing tables, thresholds, or final result framing.
 - Keep metric definitions, comparison semantics, and implementation references anchored to the approved evaluation protocol instead of re-deriving them during reporting.
 - Aggregate them with `.lab/.managed/scripts/summarize_iterations.py`.
-- Write the final document with `.lab/.managed/templates/final-report.md`.
+- Write the final document with `.lab/.managed/templates/final-report.md` and the managed table summary with `.lab/.managed/templates/main-tables.md`.
 - Keep failed attempts and limitations visible.
 - Update `.lab/context/state.md` and `.lab/context/evidence-index.md` with report-level handoff notes.
 
@@ -160,13 +160,16 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Start only after `report` artifacts are stable enough to support paper claims.
 - Start only after an approved framing artifact exists at `.lab/writing/framing.md`.
 - Read `.lab/config/workflow.json` before drafting and enforce its `paper_language` and `paper_format`.
+- If `paper_template_root` is empty and `paper_template_decision` is `unconfirmed`, ask once whether to continue with the managed default scaffold or attach a template directory first; persist the answer before drafting `.tex`.
+- If the project is still on the default scaffold at a final export or final-draft boundary and `paper_template_final_reminder_acknowledged` is `false`, ask one final reminder question before finalizing.
 - Read `.lab/context/mission.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/data-decisions.md` before drafting.
 - Write one paper section or one explicit subproblem per round.
 - Bind each claim to evidence from `report`, iteration reports, or normalized summaries.
 - Write planning artifacts with `.lab/.managed/templates/paper-plan.md`, `.lab/.managed/templates/paper-section.md`, and `.lab/.managed/templates/write-iteration.md`.
 - Write final manuscript artifacts with `.lab/.managed/templates/paper.tex` and `.lab/.managed/templates/paper-section.tex`.
 - Use the vendored paper-writing references under `skills/lab/references/paper-writing/`.
-- Load only the current section guide, plus `paper-review.md` and `does-my-writing-flow-source.md`.
+- For `abstract`, `introduction`, and `method`, also use the vendored example-bank files under `skills/lab/references/paper-writing/examples/`.
+- Load only the current section guide, the matching examples index when one exists, 1-2 matching concrete example files, plus `paper-review.md` and `does-my-writing-flow-source.md`.
 - Build a compact mini-outline before prose.
 - For each subsection, explicitly cover motivation, design, and technical advantage when applicable.
 - Keep terminology stable across rounds and sections.
@@ -203,6 +206,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Write stage guide: `.codex/skills/lab/stages/write.md` or `.claude/skills/lab/stages/write.md`
 - Paper-writing integration: `.codex/skills/lab/references/paper-writing-integration.md` or `.claude/skills/lab/references/paper-writing-integration.md`
 - Vendored paper-writing references: `.codex/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md` or `.claude/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md`
+- Vendored paper-writing example bank: `.codex/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples}.md` or `.claude/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples}.md`, plus the matching section subdirectories
 - Command adapters: the installed `/lab:*` command assets
 - Shared workflow config: `.lab/config/workflow.json`
 - Shared project context: `.lab/context/{mission,state,decisions,evidence-index,open-questions,data-decisions,eval-protocol,auto-mode,auto-status}.md`

package/package-assets/shared/skills/lab/references/paper-writing/abstract.md

@@ -77,7 +77,13 @@ Version 3: When there are multiple technical contributions, describe each contri
 
 ## Usage Note
 
-This vendored guide is intentionally self-contained. The original example-bank files are not bundled in `superlab`, so use the structures and checklists in this document directly rather than chasing external example paths.
+This vendored guide should be paired with the local abstract example bank:
+
+- `references/examples/index.md`
+- `references/examples/abstract-examples.md`
+- one matching file under `references/examples/abstract/`
+
+Use the structures and checklists here first, then use the example files to choose a concrete abstract shape and sentence logic. Reuse structure, not wording.
 
 ## Abstract Quality Checklist
 

package/package-assets/shared/skills/lab/references/paper-writing/examples/abstract/template-a.md

@@ -0,0 +1,21 @@
+# Abstract Template A Examples (Challenge -> Contribution)
+
+Source scope: your original notes, "Version 1".
+
+```latex
+\section{Abstract}
+% Task
+% Technical challenge for previous methods (discuss around the technical challenge that we solved)
+% Introduce the technical contribution for solving the challenge in one to two sentences (usually mention the technical term/name only, without describing every detailed step. The term should be easy to understand and should not create a jump in reading. This ability is very important for writing a good abstract.)
+% Introduce the benefits of the technical contribution
+% Experiment
+```
+
+## Reusable skeleton
+
+1. `[Task sentence]`
+2. `However, previous methods suffer from [technical challenge].`
+3. `To solve this challenge, we propose [technical contribution name].`
+4. `[One more contribution sentence if needed].`
+5. `This contribution brings [technical benefit].`
+6. `Experiments show [main result].`