superlab 0.1.51 → 0.1.53

package/README.md

@@ -327,8 +327,10 @@ If `paper_template_root` is configured, `/lab:write` should inspect that templat
 If no template is configured, the first manuscript-writing round should ask once whether to continue with the managed default LaTeX scaffold or attach a template directory first.
 If the user approves the default scaffold, persist that choice in `.lab/config/workflow.json` and stop asking on ordinary rounds.
 Ordinary manuscript drafting rounds should follow `workflow_language`.
-If `workflow_language` and `paper_language` differ, `/lab:write` should preserve a readable workflow-language deliverable first, then the first final-draft or export round should ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, then persist that decision.
-The workflow-language deliverable is a real reading copy, not a review layer, and should stay persisted until it is explicitly refreshed.
+If `workflow_language` and `paper_language` differ, `/lab:write` should preserve a full workflow-language paper layer first, then the first final-draft or export round should ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, then persist that decision.
+The workflow-language paper layer is a real LaTeX mirror of the paper, not a review layer, and should stay persisted until it is explicitly refreshed.
+Paper-facing tables must be locally interpretable: readers should be able to recover row meaning, column meaning, metric direction, and any relevant denominator or unit from the table title, note, and adjacent prose without chasing the Method section. Short headers are allowed, but abbreviations must be expanded locally in the same table.
+If Method or Experiments prose promises a metric family, the main table set must either expose that family directly or explicitly mark missing metrics as appendix-only and explain why.
 At the final export or final-draft boundary, if the project is still on the default scaffold and no attached template exists, ask one final reminder question before finalizing.
 For final-draft or export rounds, `/lab:write` should materialize real LaTeX tables, figure placeholders with figure intent, a non-empty `references.bib`, and pass `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper` before stopping.
 

package/lib/i18n.cjs

@@ -2026,7 +2026,9 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "write.md")] = `# \`/l
 - 每轮只改一个 section 或一个明确子问题。
 - 最终稿必须是 LaTeX。
 - 普通起草轮次先跟随 \`workflow_language\`。
-- 把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。
+- 把 workflow-language 论文层当成正式持久化产物，而不是 review 层。
+- workflow-language 层必须是一套完整的 LaTeX 镜像，至少包含 \`workflow-language/main.tex\`、\`workflow-language/references.bib\`、\`workflow-language/sections/*.tex\`、\`workflow-language/tables/*.tex\`、\`workflow-language/figures/*.tex\` 和 \`workflow-language/analysis/analysis-asset.tex\`。
+- 不要再把新的 workflow-language 输出写到已经废弃的 review 层路径，例如 \`docs/lab/paper/review_zh/\`。
 - 如果配置了 \`paper_template_root\`，先检查该模板目录，再按其结构起草论文。
 - 已接入的模板目录可能包含用户或上游修改，默认不要改模板文件。
 - 如果没有配置模板且 \`paper_template_decision\` 是 \`unconfirmed\`，在第一次起草 \`.tex\` 之前必须先追问一次：继续使用默认 LaTeX scaffold，还是先接入模板目录。
@@ -2036,12 +2038,12 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "write.md")] = `# \`/l
 - 如果当前是最终导出或最终定稿轮次、\`paper_template_root\` 仍为空、\`paper_template_decision\` 是 \`default-scaffold\`，且 \`paper_template_final_reminder_acknowledged\` 是 \`false\`，就在最终定稿前再提醒一次是否切到模板。
 - 如果用户在最终提醒里仍确认继续使用默认 scaffold，就把 \`paper_template_final_reminder_acknowledged\` 持久化为 \`true\`。
 - 普通 manuscript 起草轮次虽然也是 LaTeX，但普通 \`.tex\` section 草稿必须先跟随 \`workflow_language\`，不要把 \`paper_language\` 当成默认草稿语言。
-- 如果当前是最终导出或最终定稿轮次，且 \`workflow_language\` 与 \`paper_language\` 不一致、\`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前 workflow language，还是把 canonical manuscript 转换成 \`paper_language\`。
+- 如果当前是最终导出或最终定稿轮次，且 \`workflow_language\` 与 \`paper_language\` 不一致、\`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就先完成并保留 workflow-language 论文层，再追问一次：保持当前 workflow language，还是把 canonical manuscript 转换成 \`paper_language\`。
 - 如果用户选择保持当前 workflow language，就把 \`paper_language_finalization_decision\` 持久化成 \`keep-workflow-language\`。
 - 如果用户选择转换成最终论文语言，就把 \`paper_language_finalization_decision\` 持久化成 \`convert-to-paper-language\`。
 - 如果 \`workflow_language\` 与 \`paper_language\` 不一致，就不要在确认前先把最终论文正文改写成 \`paper_language\`；必须先追问、再持久化、再改稿。
-- 如果 \`workflow_language\` 与 \`paper_language\` 不一致，就要在最新 write iteration artifact 里记录工作流语言、论文语言、最终语言决定、为什么这样决定，以及 workflow-language 交付稿路径。
-- 如果 \`paper_language_finalization_decision\` 是 \`convert-to-paper-language\`，在接受最终定稿前必须保留 workflow-language 交付稿，并把 canonical manuscript 转换到 \`paper_language\`。
+- 如果 \`workflow_language\` 与 \`paper_language\` 不一致，就要在最新 write iteration artifact 里记录工作流语言、论文语言、最终语言决定、为什么这样决定，以及 workflow-language 论文层路径。
+- 如果 \`paper_language_finalization_decision\` 是 \`convert-to-paper-language\`，在接受最终定稿前必须保留 workflow-language 论文层，并把 canonical manuscript 转换到 \`paper_language\`。
 - 把 \`.lab/writing/terminology-glossary.md\` 当成写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名；它和 \`.lab/context/terminology-lock.md\` 的职责不同，不能混用。
 - 无论当前语言是什么，都要满足同一套学术可读性标准；如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就在首次出现时顺手说明它是什么、为什么在这里重要。
 - 第一次出现先写全称；如果后面要复用简称或缩写，就在首次出现时定义。
@@ -2868,12 +2870,12 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "auto.md")] = `# \`/la
   - 如果用户在最终提醒里仍确认继续使用默认 scaffold，就持久化 \`paper_template_final_reminder_acknowledged: true\`
 - 普通 \`write\` 起草轮次先跟随 \`workflow_language\`。
 - 普通 \`write\` 起草轮次里的 manuscript 仍然是 LaTeX，所以普通 manuscript \`.tex\` sections 也必须先保留在 \`workflow_language\`，还不是 \`paper_language\` 版本。
-- 把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。
-- 如果当前写作目标是最终导出、\`workflow_language\` 与 \`paper_language\` 不一致，且 \`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就在最终定稿前先完成并保留 workflow-language 交付稿，再追问一次：保持当前 workflow language，还是转换成 \`paper_language\`
+- 把 workflow-language 论文层当成正式持久化产物，而不是 review 层。
+- 如果当前写作目标是最终导出、\`workflow_language\` 与 \`paper_language\` 不一致，且 \`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就在最终定稿前先完成并保留 workflow-language 论文层，再追问一次：保持当前 workflow language，还是转换成 \`paper_language\`
 - 如果用户选择保持当前语言，就持久化 \`paper_language_finalization_decision: keep-workflow-language\`
 - 如果用户选择转换，就持久化 \`paper_language_finalization_decision: convert-to-paper-language\`
 - 如果当前写作目标是最终导出，且语言不一致，就不要在追问前先把最终论文正文改成 \`paper_language\`；先问、先持久化，再改稿
-- 如果当前写作目标是最终导出，且语言不一致，就在最新 write iteration 里记录语言决策审计：工作流语言、论文语言、最终语言决定、为什么这样决定，以及 workflow-language 交付稿路径
+- 如果当前写作目标是最终导出，且语言不一致，就在最新 write iteration 里记录语言决策审计：工作流语言、论文语言、最终语言决定、为什么这样决定，以及 workflow-language 论文层路径
 - 把 \`.lab/writing/terminology-glossary.md\` 当成写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名
 - 当循环推进 \`write\` 时，无论 workflow language 还是 paper language，都要满足同一套学术可读性标准；如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就在首次出现时说明它是什么、为什么在这里重要
 - 当循环推进 \`write\` 时，第一次出现先写全称；如果后面要复用简称或缩写，就在首次出现时定义；一个概念只保留一个 paper-facing 名称，并尽量避免新造的连字符拼接标签

package/lib/lab_write_contract.json

@@ -1,8 +1,8 @@
 {
   "stage_prompt": {
-    "codex_en": "This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
-    "claude_en": "This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
-    "codex_zh": "本命令运行 `/lab:write` 阶段。把 `.codex/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。把 `.lab/writing/terminology-glossary.md` 作为写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名。无论当前语言是什么，都要满足同一套学术可读性标准：如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就先写全称；如果后面要复用短写，就在首次出现时定义；同时说明它是什么、为什么在这里重要，保持一个概念只有一个 paper-facing 名称，并尽量避免新造的连字符拼接标签。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检写进 write iteration artifact。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。",
-    "claude_zh": "本命令运行 lab workflow 的 `write` 阶段。把 `.claude/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。把 `.lab/writing/terminology-glossary.md` 作为写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名。无论当前语言是什么，都要满足同一套学术可读性标准：如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就先写全称；如果后面要复用短写，就在首次出现时定义；同时说明它是什么、为什么在这里重要，保持一个概念只有一个 paper-facing 名称，并尽量避免新造的连字符拼接标签。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检写进 write iteration artifact。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。"
+    "codex_en": "This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
+    "claude_en": "This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
+    "codex_zh": "本命令运行 `/lab:write` 阶段。把 `.codex/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。workflow-language 层必须是一套完整的 LaTeX 镜像，至少包含 `workflow-language/main.tex`、`workflow-language/references.bib`、`workflow-language/sections/*.tex`、`workflow-language/tables/*.tex`、`workflow-language/figures/*.tex` 和 `workflow-language/analysis/analysis-asset.tex`。不要再把新的 workflow-language 输出写到已经废弃的 review 层路径，例如 `docs/lab/paper/review_zh/`。把 `.lab/writing/terminology-glossary.md` 作为写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名。无论当前语言是什么，都要满足同一套学术可读性标准：如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就先写全称；如果后面要复用短写，就在首次出现时定义；同时说明它是什么、为什么在这里重要，保持一个概念只有一个 paper-facing 名称，并尽量避免新造的连字符拼接标签。相同的首次解释规则也适用于表头、caption、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检和 table-semantics 审计一起写进 write iteration artifact。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 论文层，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 论文层路径，最后才允许按该语言修改最终稿。",
+    "claude_zh": "本命令运行 lab workflow 的 `write` 阶段。把 `.claude/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。workflow-language 层必须是一套完整的 LaTeX 镜像，至少包含 `workflow-language/main.tex`、`workflow-language/references.bib`、`workflow-language/sections/*.tex`、`workflow-language/tables/*.tex`、`workflow-language/figures/*.tex` 和 `workflow-language/analysis/analysis-asset.tex`。不要再把新的 workflow-language 输出写到已经废弃的 review 层路径，例如 `docs/lab/paper/review_zh/`。把 `.lab/writing/terminology-glossary.md` 作为写作期 glossary，用来沉淀全称、批准缩写、对外解释和可接受别名。无论当前语言是什么，都要满足同一套学术可读性标准：如果本轮引入或改写了关键术语、缩写、指标名、机制名或系统标签，就先写全称；如果后面要复用短写，就在首次出现时定义；同时说明它是什么、为什么在这里重要，保持一个概念只有一个 paper-facing 名称，并尽量避免新造的连字符拼接标签。相同的首次解释规则也适用于表头、caption、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检和 table-semantics 审计一起写进 write iteration artifact。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 论文层，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 论文层路径，最后才允许按该语言修改最终稿。"
   }
 }

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

@@ -7,4 +7,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-write` command 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 `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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

@@ -7,4 +7,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-write` command 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 `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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

@@ -7,4 +7,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-write` command 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 `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/claude/commands/lab/357/274/232write.md

@@ -7,4 +7,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-write` command 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 `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab/357/274/232write.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. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat the workflow-language paper layer as a real persisted artifact rather than a review layer, and preserve it as a full LaTeX mirror with `workflow-language/main.tex`, `workflow-language/references.bib`, `workflow-language/sections/*.tex`, `workflow-language/tables/*.tex`, `workflow-language/figures/*.tex`, and `workflow-language/analysis/analysis-asset.tex`. Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, do not use labels containing `_` or `-` in reader-facing prose, and apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels. Main tables must be locally self-contained: the title, header, note, and adjacent prose should tell the reader what each row and column means, the metric direction, and any relevant unit, denominator, or event condition. Short headers remain allowed, but abbreviations in paper-facing tables must be expanded locally in the same table. If Method or Experiments prose promises a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why. If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that disposition explicitly in the table note instead of silently dropping it. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record both the terminology-clarity self-check and the table-semantics audit in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language paper-layer path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/shared/lab/.managed/scripts/validate_manuscript_delivery.py

@@ -22,6 +22,14 @@ WORKFLOW_LANGUAGE_DELIVERABLE_REVIEW_MARKERS = (
     "Claim-Evidence 映射",
     "Claim-Evidence Map",
 )
+REQUIRED_TABLE_NOTE_MARKERS = (
+    "% Rows:",
+    "% Columns:",
+    "% Metric definitions:",
+    "% Comparison scope:",
+    "% Important caveat:",
+)
+TABLE_ABBREVIATION_EXCEPTIONS = {"TODO", "TBD"}
 
 
 def parse_args():
@@ -99,6 +107,31 @@ def extract_label(text: str) -> str | None:
     return match.group(1) if match else None
 
 
+def extract_caption(text: str) -> str:
+    match = re.search(r"\\caption\{(.+?)\}", text, flags=re.DOTALL)
+    return match.group(1) if match else ""
+
+
+def extract_table_note(text: str) -> str:
+    return "\n".join(line.strip() for line in text.splitlines() if line.strip().startswith("%"))
+
+
+def detect_uppercase_abbreviations(text: str) -> set[str]:
+    return {
+        token
+        for token in re.findall(r"\b[A-Z]{2,6}\b", text)
+        if token not in TABLE_ABBREVIATION_EXCEPTIONS
+    }
+
+
+def has_local_abbreviation_expansion(context: str, token: str) -> bool:
+    patterns = (
+        rf"[A-Za-z\u4e00-\u9fff][^\n]{{0,80}}[\(（]{re.escape(token)}[\)）]",
+        rf"{re.escape(token)}\s*[:=：]",
+    )
+    return any(re.search(pattern, context) for pattern in patterns)
+
+
 def section_references_label(text: str, label: str) -> bool:
     return bool(re.search(REF_PATTERN_TEMPLATE % re.escape(label), text))
 
@@ -146,6 +179,14 @@ def check_table_file(path: Path, issues: list[str], label: str):
         issues.append(f"{label} must contain both caption and label")
     if not all(token in text for token in (r"\toprule", r"\midrule", r"\bottomrule")):
         issues.append(f"{label} must use booktabs structure")
+    if not all(marker in text for marker in REQUIRED_TABLE_NOTE_MARKERS):
+        issues.append(f"{label} must include a local table note scaffold")
+    caption_text = extract_caption(text)
+    note_text = extract_table_note(text)
+    local_context = "\n".join((caption_text, note_text))
+    for token in sorted(detect_uppercase_abbreviations(text)):
+        if not has_local_abbreviation_expansion(local_context, token):
+            issues.append(f"{label} uses abbreviation `{token}` without local expansion")
 
 
 def check_figure_file(path: Path, issues: list[str], label: str):
@@ -271,8 +312,9 @@ def check_asset_consumption(paper_dir: Path, issues: list[str]):
     require_section_reference(experiments_text, analysis_label, issues, "experiments section", "analysis asset")
 
     main_results_text = read_text(tables_dir / "main-results.tex") if (tables_dir / "main-results.tex").exists() else ""
+    main_results_tabular = main_results_text.split(r"\end{tabular}")[0] if main_results_text else ""
     prose_for_ranking_claims = "\n".join((introduction_text, experiments_text))
-    if re.search(r"\bQini\b", prose_for_ranking_claims, flags=re.IGNORECASE) and "Qini" not in main_results_text:
+    if re.search(r"\bQini\b", prose_for_ranking_claims, flags=re.IGNORECASE) and "Qini" not in main_results_tabular:
         issues.append("manuscript prose mentions Qini but tables/main-results.tex does not expose it")
 
 
@@ -372,36 +414,80 @@ def check_language_layers(paper_dir: Path, issues: list[str]):
     if section_text and not text_looks_like_language(section_text, target_language):
         issues.append(
             f"final manuscript sections should follow {target_language} after paper_language_finalization_decision={finalization_decision}"
-        )
+            )
 
     if finalization_decision != "convert-to-paper-language":
         return
 
-    workflow_deliverable_sections = paper_dir / "workflow-language" / "sections"
-    if not workflow_deliverable_sections.exists():
+    workflow_layer_dir = paper_dir / "workflow-language"
+    workflow_deliverable_sections = workflow_layer_dir / "sections"
+    workflow_tables_dir = workflow_layer_dir / "tables"
+    workflow_figures_dir = workflow_layer_dir / "figures"
+    workflow_analysis_dir = workflow_layer_dir / "analysis"
+    if not workflow_layer_dir.exists():
         issues.append(
-            "missing persisted workflow-language deliverable under workflow-language/sections before converting the final manuscript to paper_language"
+            "missing persisted workflow-language paper layer under workflow-language/ before converting the final manuscript to paper_language"
         )
         return
+    workflow_main_tex = workflow_layer_dir / "main.tex"
+    workflow_references = workflow_layer_dir / "references.bib"
+    if not workflow_main_tex.exists():
+        issues.append("workflow-language paper layer is missing main.tex")
+    if not workflow_references.exists():
+        issues.append("workflow-language paper layer is missing references.bib")
+    if not workflow_deliverable_sections.exists():
+        issues.append("workflow-language paper layer is missing sections/")
+    if not workflow_tables_dir.exists():
+        issues.append("workflow-language paper layer is missing tables/")
+    if not workflow_figures_dir.exists():
+        issues.append("workflow-language paper layer is missing figures/")
+    if not workflow_analysis_dir.exists():
+        issues.append("workflow-language paper layer is missing analysis/")
 
     manuscript_section_files = sorted(path for path in sections_dir.glob("*.tex") if path.is_file())
     for manuscript_section in manuscript_section_files:
-        companion_path = workflow_deliverable_sections / f"{manuscript_section.stem}.md"
+        companion_path = workflow_deliverable_sections / f"{manuscript_section.stem}.tex"
         if not companion_path.exists():
             issues.append(
-                f"workflow-language deliverable is missing section companion: workflow-language/sections/{manuscript_section.stem}.md"
+                f"workflow-language paper layer is missing section companion: workflow-language/sections/{manuscript_section.stem}.tex"
             )
             continue
         companion_text = read_text(companion_path)
         if not text_looks_like_language(companion_text, workflow_language):
             issues.append(
-                f"workflow-language deliverable section {companion_path.name} should follow workflow_language={workflow_language}"
+                f"workflow-language paper-layer section {companion_path.name} should follow workflow_language={workflow_language}"
             )
         if any(marker in companion_text for marker in WORKFLOW_LANGUAGE_DELIVERABLE_REVIEW_MARKERS):
             issues.append(
-                f"workflow-language deliverable section {companion_path.name} contains review-only scaffolding and cannot substitute for a readable deliverable"
+                f"workflow-language paper-layer section {companion_path.name} contains review-only scaffolding and cannot substitute for a readable deliverable"
             )
 
+    mirror_asset_dirs = [
+        (paper_dir / "tables", workflow_tables_dir, REQUIRED_TABLE_FILES, "table asset"),
+        (paper_dir / "figures", workflow_figures_dir, REQUIRED_FIGURE_FILES, "figure asset"),
+        (paper_dir / "analysis", workflow_analysis_dir, ("analysis-asset.tex",), "analysis asset"),
+    ]
+    for manuscript_dir, workflow_dir, filenames, asset_label in mirror_asset_dirs:
+        for filename in filenames:
+            manuscript_path = manuscript_dir / filename
+            if not manuscript_path.exists():
+                continue
+            workflow_path = workflow_dir / filename
+            if not workflow_path.exists():
+                issues.append(
+                    f"workflow-language paper layer is missing mirrored {asset_label}: workflow-language/{workflow_dir.name}/{filename}"
+                )
+                continue
+            workflow_text = read_text(workflow_path)
+            if not text_looks_like_language(workflow_text, workflow_language):
+                issues.append(
+                    f"workflow-language paper-layer asset {workflow_path.name} should follow workflow_language={workflow_language}"
+                )
+            if any(marker in workflow_text for marker in WORKFLOW_LANGUAGE_DELIVERABLE_REVIEW_MARKERS):
+                issues.append(
+                    f"workflow-language paper-layer asset {workflow_path.name} contains review-only scaffolding and cannot substitute for a readable deliverable"
+                )
+
 
 def main():
     args = parse_args()

package/package-assets/shared/lab/.managed/templates/paper-table.tex

@@ -10,4 +10,9 @@ Ours & 0.0000 & 0.0000 \\
 Baseline & 0.0000 & 0.0000 \\
 \bottomrule
 \end{tabular}
+% Rows: explain what each row represents.
+% Columns: explain what each column represents and its direction.
+% Metric definitions: expand local abbreviations, units, denominators, or event conditions.
+% Comparison scope: explain which setting, split, attack family, or benchmark scope this table covers.
+% Important caveat: state any omitted metrics, zero-valued metrics, or appendix-only reporting decision.
 \end{table}

package/package-assets/shared/lab/.managed/templates/write-iteration.md

@@ -40,6 +40,15 @@
 - Did any alias drift remain unresolved:
 - Remaining reader-facing jargon risk:
 
+## Table Semantics
+
+- Metrics promised in Method:
+- Metrics shown in main tables:
+- Any omitted metric and why:
+- Were all abbreviations expanded at local first mention:
+- Did each main table include a local table note:
+- Can a reader interpret rows and columns without chasing Method:
+
 ## Language Decision
 
 - Workflow language:

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

@@ -213,15 +213,20 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Write one paper section or one explicit subproblem per round.
 - Ordinary manuscript drafting rounds should follow `workflow_language`.
 - In those ordinary rounds, the manuscript is still LaTeX, so the initial `.tex` section drafts must stay in `workflow_language` rather than jumping straight to `paper_language`.
-- Treat the readable workflow-language paper as a real persisted deliverable, not as a review layer.
-- If `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then the first final-draft or export round must ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`.
+- Treat the workflow-language paper as a real persisted paper layer, not as a review layer.
+- If `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then the first final-draft or export round must ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`.
 - When the languages differ, do not rewrite final manuscript sections in `paper_language` before that question has been answered; ask first, persist the choice, then edit the final manuscript in the chosen language.
-- When the languages differ, record the workflow language, paper language, finalization decision, why the decision was chosen, and the workflow-language deliverable path in the latest write iteration artifact.
+- When the languages differ, record the workflow language, paper language, finalization decision, why the decision was chosen, and the workflow-language paper-layer path in the latest write iteration artifact.
 - Apply the same reader-facing standard in both languages: when a round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, explain them at first mention by saying what they are and why they matter here.
 - First mention should use the full form. If a short form or acronym will be reused, define it at first mention and then keep usage stable.
+- Apply the same first-mention rule to table headers, captions, notes, and figure captions or labels; if a term first appears in a table, explain it locally in that table.
 - Keep one canonical natural-language paper-facing name per concept.
 - Use natural-language full names in prose, and define any approved short form once before reusing it.
 - Do not use labels containing `_` or `-` in reader-facing prose.
+- Main tables must be locally self-contained: a reader should be able to understand row meaning, column meaning, metric direction, and any relevant unit or denominator from the table title, table note, and adjacent prose without chasing the Method section.
+- If Method or Experiments prose promises a metric family, the main table set must either expose that metric family directly or mark the missing items as appendix-only and explain why.
+- Short table headers are allowed, but any abbreviation in a paper-facing table must be expanded locally in the same table.
+- If a metric is measured but omitted because it is zero everywhere, redundant, or appendix-only, state that decision explicitly in the table note instead of silently dropping it.
 - Keep internal identifiers out of prose unless they are mapped once for the reader and then moved back out of prose.
 - Do not rely on unexplained jargon density as a substitute for academic tone.
 - Bind each claim to evidence from `report`, iteration reports, or normalized summaries.
@@ -252,7 +257,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - No final report without validated normalized results.
 - No paper-writing round without stable report artifacts, an approved framing artifact, evidence links, and LaTeX manuscript output.
 - No final-draft or export round without passing section-quality, claim-safety, and manuscript-delivery validation.
-- No final-draft or export round with mismatched `workflow_language` and `paper_language` unless the latest write iteration records the language decision audit that justified the final manuscript language and the persisted workflow-language deliverable path.
+- No final-draft or export round with mismatched `workflow_language` and `paper_language` unless the latest write iteration records the language decision audit that justified the final manuscript language and the persisted workflow-language paper-layer path.
 
 ## References
 

package/package-assets/shared/skills/lab/stages/write.md

@@ -65,9 +65,11 @@ Run these on every round:
 - LaTeX is the required manuscript output format.
 - Ordinary manuscript drafting rounds should follow `workflow_language`.
 - During ordinary rounds, ordinary `.tex` section drafts must stay in `workflow_language`; do not treat `paper_language` as the default draft language.
-- Treat the workflow-language manuscript as a real deliverable layer, not just an internal review note.
-- If the user asks to read the paper in `workflow_language`, materialize or refresh a readable workflow-language deliverable under `<deliverables_root>/paper/workflow-language/sections/<section>.md` instead of pointing to a review layer.
-- The workflow-language deliverable should mirror the current manuscript logic in reader-facing prose and must not contain review-only scaffolding such as paragraph outlines, self-check blocks, or claim-evidence maps.
+- Treat the workflow-language manuscript as a real persisted paper layer, not just an internal review note.
+- If the user asks to read the paper in `workflow_language`, materialize or refresh a full workflow-language paper layer under `<deliverables_root>/paper/workflow-language/` instead of pointing to a review layer.
+- The workflow-language paper layer must stay in LaTeX and mirror the canonical paper structure with its own `main.tex`, `references.bib`, `sections/*.tex`, `tables/*.tex`, `figures/*.tex`, and `analysis/analysis-asset.tex`.
+- The workflow-language paper layer must mirror the current manuscript logic in reader-facing prose and must not contain review-only scaffolding such as paragraph outlines, self-check blocks, or claim-evidence maps.
+- Do not write new workflow-language output to deprecated review-layer paths such as `docs/lab/paper/review_zh/`.
 - If `paper_template_root` is configured, inspect that template directory before drafting and align the manuscript structure to it.
 - Treat attached template directories as user-owned and potentially modified. Do not rewrite template files unless the user explicitly asks.
 - If no paper template is configured and `paper_template_decision` is `unconfirmed`, ask one explicit question before the first `.tex` drafting round: continue with the default LaTeX scaffold, or attach a template directory first.
@@ -83,11 +85,11 @@ Run these on every round:
 - If the current round is a final manuscript export or final-draft pass, `paper_template_root` is still empty, `paper_template_decision` is `default-scaffold`, and `paper_template_final_reminder_acknowledged` is `false`, ask one final reminder question about switching to a template before finalizing.
 - If the user confirms staying on the default scaffold at that final reminder, persist `paper_template_final_reminder_acknowledged: true`.
 - If the current round is a final manuscript export or final-draft pass, `workflow_language` and `paper_language` differ, and `paper_language_finalization_decision` is `unconfirmed`, ask one explicit question before finalizing: keep the manuscript in `workflow_language`, or convert the final manuscript to `paper_language`.
-- When `workflow_language` and `paper_language` differ, finish and preserve the readable workflow-language deliverable first, then ask whether the canonical manuscript should be converted to `paper_language`.
+- When `workflow_language` and `paper_language` differ, finish and preserve the workflow-language paper layer first, then ask whether the canonical manuscript should be converted to `paper_language`.
 - Do not rewrite final manuscript sections in `paper_language` before that question has been answered. Ask first, persist the answer, then edit the final manuscript.
 - If the user chooses to keep the draft language, persist `paper_language_finalization_decision: keep-workflow-language`.
 - If the user chooses to convert, persist `paper_language_finalization_decision: convert-to-paper-language`.
-- If `paper_language_finalization_decision` is `convert-to-paper-language`, preserve the workflow-language deliverable under `<deliverables_root>/paper/workflow-language/sections/` and convert only the canonical manuscript output to `paper_language` before accepting the final round.
+- If `paper_language_finalization_decision` is `convert-to-paper-language`, preserve the workflow-language paper layer under `<deliverables_root>/paper/workflow-language/` and convert only the canonical manuscript output to `paper_language` before accepting the final round.
 - Load only the current section guide. Do not load every section guide at once.
 - Reuse example-bank structure, paragraph roles, sentence logic, and paper-facing LaTeX asset patterns when examples are bundled, but never copy wording verbatim.
 - Treat example cites and example file names as writing references, not as evidence for the current paper.
@@ -95,11 +97,17 @@ Run these on every round:
 - Academic readability standards are the same in `workflow_language` and `paper_language`; changing languages must not lower external-reader clarity.
 - If the current round introduces or revises key terms, abbreviations, metric names, mechanism names, or system labels, explain them at first mention by briefly stating what they are and why they matter here.
 - First mention should use the full form. If a short form or acronym will be reused later, define it at first mention as `Full Form (Short Form)` before switching to the short form.
+- Apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels; if a term or abbreviation first appears in a table, expand it locally in that table.
 - Keep one canonical natural-language paper-facing name per concept. Do not let one concept drift across paper-facing names, experiment labels, and internal identifiers.
 - Use natural-language full names in prose. If an approved short form is needed later, define it once and reuse it consistently.
 - Do not use labels containing `_` or `-` in reader-facing prose.
 - Keep internal identifiers, config keys, and experiment package labels out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose.
 - Do not use unexplained terminology density as a substitute for academic tone.
+- Main tables must be locally self-contained: a reader looking at the table title, header, note, and adjacent introduction or interpretation should be able to determine what each row represents, what each column measures, the metric direction, and any relevant unit, denominator, or event condition.
+- Short headers remain allowed, but they must be resolved locally through the same table's caption or table note instead of forcing the reader to chase the Method section.
+- If the Method or Experiments prose says the paper reports a metric family, the main table set must either expose those metrics directly or explicitly mark the missing ones as appendix-only and explain why.
+- If a metric is measured but omitted because it is uniformly zero, redundant, or appendix-only, state that disposition explicitly in the caption or table note instead of silently dropping it.
+- Every main table should have a short table-introduction sentence before it and a short interpretation sentence after it so the reader knows what question the table answers and how to read the result.
 - Build the paper asset plan before prose when the section carries introduction, experimental, method, related-work, or conclusion claims:
   - record the asset coverage targets and gaps for the current paper
   - record which table asset files the section needs, what each table should show, and which evidence supports it
@@ -131,6 +139,7 @@ Run these on every round:
 - If the current paper contains experimental claims, materialize one additional paper-facing analysis asset with caption, label, and explicit asset intent:
   - `<deliverables_root>/paper/analysis/analysis-asset.tex`
 - Table assets must use paper-facing LaTeX structure with `booktabs`, caption, label, and consistent precision.
+- Table assets must also include a local table note that explains row meaning, column meaning, metric definitions, comparison scope, and any important caveat.
 - Figure placeholders must explain what the final figure should show and why the reader needs it.
 - Core asset coverage for a paper-facing final draft should include a problem-setting or teaser figure, a method overview figure, a results overview figure, a main-results table, an ablation table, and one additional analysis asset.
 - Keep `.lab/writing/plan.md` synchronized with the current table plan, figure plan, citation plan, and section-to-asset map whenever manuscript assets change.
@@ -138,14 +147,14 @@ Run these on every round:
 - If the final-round section or claim validators fail, keep editing the affected section until it passes; do not stop at asset-complete but rhetorically weak or unsafe prose.
 - Run `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper` before accepting a final-draft or export round.
 - The manuscript-delivery validator should fail if the core figures and tables are only inserted but never cited from section prose, if final manuscript acceptance tries to bypass the one-time `paper_language_finalization_decision` gate when `workflow_language` and `paper_language` differ, or if the latest write iteration does not audit that language decision.
-- The manuscript-delivery validator should also fail if `paper_language_finalization_decision=convert-to-paper-language` but the persisted workflow-language deliverable is missing, missing section coverage, written in the wrong language, or still contains review-only scaffolding.
+- The manuscript-delivery validator should also fail if `paper_language_finalization_decision=convert-to-paper-language` but the persisted workflow-language paper layer is missing, missing `main.tex` or `references.bib`, missing mirrored section or asset coverage, written in the wrong language, or still contains review-only scaffolding.
 - If the manuscript validator fails, keep editing and asset generation until it passes; do not stop at prose-only completion.
 - Run a LaTeX compile smoke test when a local LaTeX toolchain is available; if not available, record the missing verification in the write iteration artifact.
 - Record what changed and why in a write-iteration artifact.
 - Maintain `.lab/writing/terminology-glossary.md` as the write-stage source for full forms, approved short forms, reader-facing explanations, and aliases whenever terminology changes.
 - When a round introduces or revises key terms, include a compact terminology note in the user-facing round summary and record the terminology-clarity self-check in the write-iteration artifact.
 - When `workflow_language` and `paper_language` differ, record the final manuscript language choice in the write-iteration artifact with the workflow language, paper language, finalization decision, and why that decision was chosen.
-- When `workflow_language` and `paper_language` differ, also record the persisted workflow-language deliverable path in the write-iteration artifact.
+- When `workflow_language` and `paper_language` differ, also record the persisted workflow-language paper-layer path in the write-iteration artifact.
 - Keep the handoff wording in the write-iteration artifact explicit and stable: say what is completed, what scope is frozen for the next round, what the next owner is allowed to do, what they must read first, and what counts as accept, revise, or reject.
 - Return paragraph-level roles for the revised prose when drafting.
 - Run the five-dimension self-review checklist before accepting a round.
@@ -168,7 +177,15 @@ Run these on every round:
 - `<deliverables_root>/paper/figures/method-overview.tex`
 - `<deliverables_root>/paper/figures/results-overview.tex`
 - `<deliverables_root>/paper/analysis/analysis-asset.tex`
-- `<deliverables_root>/paper/workflow-language/sections/<section>.md` when the user requests a readable workflow-language deliverable or when `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/main.tex` when the user requests a workflow-language paper layer or when `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/references.bib` when the user requests a workflow-language paper layer or when `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/sections/<section>.tex` when the user requests a workflow-language paper layer or when `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/tables/main-results.tex` when the current paper contains experimental claims and `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/tables/ablations.tex` when the current paper contains experimental claims and `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/figures/problem-setting.tex` when the current paper contains method or experiments claims and `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/figures/method-overview.tex` when the current paper contains method or experiments claims and `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/figures/results-overview.tex` when the current paper contains experimental claims and `paper_language_finalization_decision=convert-to-paper-language`
+- `<deliverables_root>/paper/workflow-language/analysis/analysis-asset.tex` when the current paper contains experimental claims and `paper_language_finalization_decision=convert-to-paper-language`
 
 ## Stop Conditions
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superlab",
-  "version": "0.1.51",
+  "version": "0.1.53",
   "description": "Strict /lab research workflow installer for Codex and Claude",
   "keywords": [
     "codex",