superlab 0.1.60 → 0.1.62

package/README.md

@@ -329,8 +329,9 @@ If the user approves the default scaffold, persist that choice in `.lab/config/w
 Ordinary manuscript drafting rounds should follow `workflow_language`.
 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.
-Ordinary `/lab:write` rounds should edit one target paper layer by default. Do not silently refresh both the canonical manuscript and the workflow-language paper layer on the same round unless the user explicitly asked for cross-language synchronization or the final-draft/export language-finalization step requires it.
-If `paper_language_finalization_decision=convert-to-paper-language`, canonical manuscript work may proceed in `paper_language`, but that does not make workflow-language companion refresh the default next step.
+When `workflow_language` and `paper_language` differ, ordinary `/lab:write` rounds should treat the workflow-language paper layer as the default working layer. Do not silently refresh both the canonical manuscript and the workflow-language paper layer on the same round unless the user explicitly asked for cross-language synchronization or the final-draft/export language-finalization step requires it.
+Canonical-manuscript drafting is still allowed, but if workflow-language is active then canonical-only writing should record why that exception was acceptable in the latest write iteration artifact.
+If `paper_language_finalization_decision=convert-to-paper-language`, canonical manuscript work may proceed in `paper_language` during explicit canonical or finalization rounds, but that does not make canonical the default next step while workflow-language remains active.
 For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, the exported or pushed bundle should include the persisted workflow-language paper layer by default.
 Canonical-only export is acceptable only when the user explicitly asked for it or when the remote target forbids extra files, and that justification should be recorded in the latest write iteration artifact.
 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.

package/lib/auto_runner.cjs

@@ -40,6 +40,7 @@ const {
   writeAutoOutcome,
   writeAutoStatus,
 } = require("./auto_state.cjs");
+const { buildRulePreflight } = require("./rule_preflight.cjs");
 
 function normalizeTransition(value) {
   return (value || "").trim();
@@ -220,7 +221,7 @@ function buildRolledOverAutoMode(mode, requested, now) {
   };
 }
 
-function rolloverAutoCampaign({ targetDir, mode, status, ledger, requested, lang, now }) {
+function rolloverAutoCampaign({ targetDir, mode, status, ledger, requested, lang, now, rulePreflight = null }) {
   const newMode = buildRolledOverAutoMode(mode, requested, now);
   const archivedPaths = [
     archiveAutoArtifact(targetDir, path.join(".lab", "context", "auto-mode.md"), mode.campaignId || "auto-campaign", now),
@@ -250,6 +251,7 @@ function rolloverAutoCampaign({ targetDir, mode, status, ledger, requested, lang
   writeAutoStatus(
     targetDir,
     {
+      ...(rulePreflight || {}),
       status: "idle",
       currentStage: "",
       currentCommand: "",
@@ -488,6 +490,12 @@ async function startAutoMode({ targetDir, now = new Date(), requestedContract =
   const mode = parseAutoMode(targetDir);
   const existingStatus = parseAutoStatus(targetDir);
   const existingLedger = parseAutoLedger(targetDir);
+  const autoRulePreflight = buildRulePreflight({
+    targetDir,
+    stage: "auto",
+    mode: "execution",
+    target: "bounded auto campaign runtime",
+  });
   const evalProtocol = parseEvalProtocol(targetDir);
   const lang = readWorkflowLanguage(targetDir);
   const missingSchemaFields = listMissingCurrentAutoModeFields(mode);
@@ -522,6 +530,7 @@ async function startAutoMode({ targetDir, now = new Date(), requestedContract =
         requested: normalizedRequest,
         lang,
         now,
+        rulePreflight: autoRulePreflight,
       });
       throw new Error(
         `current auto contract does not fit the requested campaign and was rolled over to a new draft (${newMode.campaignId}); archived old campaign files: ${archivedPaths.join(", ")}; fill the new contract fields and approve it before starting auto mode`
@@ -557,6 +566,7 @@ async function startAutoMode({ targetDir, now = new Date(), requestedContract =
 
   const timestamp = now.toISOString();
   const status = {
+    ...autoRulePreflight,
     status: "running",
     currentStage: resumePlan?.stage || mode.allowedStages[0] || "run",
     currentCommand: "",

package/lib/auto_state.cjs

@@ -93,6 +93,13 @@ function parseAutoStatus(targetDir) {
   return {
     path: contextFile(targetDir, "auto-status.md"),
     text,
+    ruleSourceFile: extractValue(text, ["Rule source file", "规则来源文件"]),
+    ruleSourceRevision: extractValue(text, ["Rule source revision", "规则来源修订"]),
+    projectVersion: extractValue(text, ["Project version", "项目版本"]),
+    resolvedStage: extractValue(text, ["Resolved stage", "解析后的阶段"]),
+    resolvedMode: extractValue(text, ["Resolved mode", "解析后的模式"]),
+    resolvedTarget: extractValue(text, ["Resolved target", "解析后的目标"]),
+    overrideReason: extractValue(text, ["Override reason, if any", "如有覆盖理由"]),
     status: extractValue(text, ["Status", "状态"]),
     currentStage: extractValue(text, ["Current stage", "当前阶段"]),
     currentCommand: extractValue(text, ["Current command", "当前命令"]),
@@ -140,6 +147,16 @@ function renderAutoStatus(status, { lang = "en" } = {}) {
   if (lang === "zh") {
     return `# 自动模式状态
 
+## 规则预检
+
+- 规则来源文件: ${status.ruleSourceFile || ""}
+- 规则来源修订: ${status.ruleSourceRevision || ""}
+- 项目版本: ${status.projectVersion || ""}
+- 解析后的阶段: ${status.resolvedStage || ""}
+- 解析后的模式: ${status.resolvedMode || ""}
+- 解析后的目标: ${status.resolvedTarget || ""}
+- 如有覆盖理由: ${status.overrideReason || ""}
+
 ## 运行状态
 
 - 状态: ${status.status || "idle"}
@@ -169,6 +186,16 @@ function renderAutoStatus(status, { lang = "en" } = {}) {
 
   return `# Auto Mode Status
 
+## Rule Preflight
+
+- Rule source file: ${status.ruleSourceFile || ""}
+- Rule source revision: ${status.ruleSourceRevision || ""}
+- Project version: ${status.projectVersion || ""}
+- Resolved stage: ${status.resolvedStage || ""}
+- Resolved mode: ${status.resolvedMode || ""}
+- Resolved target: ${status.resolvedTarget || ""}
+- Override reason, if any: ${status.overrideReason || ""}
+
 ## Runtime State
 
 - Status: ${status.status || "idle"}

package/lib/i18n.cjs

@@ -260,6 +260,7 @@ const ZH_SKILL_FILES = {
 - \`.lab/context/mission.md\`
 - \`.lab/context/decisions.md\`
 - \`.lab/context/evidence-index.md\`
+- \`.lab/.managed/rule-manifest.json\`
 
 ## 上下文写回
 
@@ -890,6 +891,16 @@ const ZH_SKILL_FILES = {
   [path.join(".lab", ".managed", "templates", "iteration-report.md")]:
 `# 迭代报告
 
+## 规则预检
+
+- Rule source file:
+- Rule source revision:
+- Project version:
+- Resolved stage:
+- Resolved mode:
+- Resolved target:
+- Override reason, if any:
+
 ## 轮次
 
 - 迭代编号:
@@ -1336,6 +1347,16 @@ const ZH_SKILL_FILES = {
   [path.join(".lab", ".managed", "templates", "write-iteration.md")]:
 `# 写作迭代
 
+## 规则预检
+
+- Rule source file:
+- Rule source revision:
+- Project version:
+- Resolved stage:
+- Resolved mode:
+- Resolved target:
+- Override reason, if any:
+
 ## 轮次
 
 - Iteration number:
@@ -1375,6 +1396,33 @@ const ZH_SKILL_FILES = {
 - Did any alias drift remain unresolved:
 - Remaining reader-facing jargon risk:
 
+## Section Acceptance Gate
+
+- Canonical naming consistency passed:
+- Adjacent-section consistency passed:
+- Claim / metric / ranking consistency with evidence passed:
+- Section-style compliance passed:
+- Local clarity passed:
+- Local concision passed:
+- If any item failed, what blocks further prose polish:
+
+## Section Style Policy
+
+- Section-style policy checked:
+- Any discouraged move kept and why:
+- Any banned move found:
+
+## 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:
+- If this section used canonical short names before their defining section, was a local naming bridge added:
+- Did model and ablation labels stay canonical instead of drifting into narrative aliases:
+
 ## Language Decision
 
 - Workflow language:
@@ -1729,6 +1777,16 @@ const ZH_SKILL_FILES = {
   [path.join(".lab", "context", "auto-status.md")]:
 `# 自动模式状态
 
+## 规则预检
+
+- Rule source file:
+- Rule source revision:
+- Project version:
+- Resolved stage:
+- Resolved mode:
+- Resolved target:
+- Override reason, if any:
+
 ## 运行状态
 
 - Status: idle
@@ -2021,14 +2079,23 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "write.md")] = `# \`/l
 - \`.lab/context/workflow-state.md\`
 - \`.lab/context/evidence-index.md\`
 
+## 规则预检
+
+- 起草前先读取 \`.lab/.managed/rule-manifest.json\`。
+- 在 write iteration artifact 里先写 \`Rule Preflight\`，再改 prose。
+- \`Rule Preflight\` 至少记录：Rule source file、Rule source revision、Project version、Resolved stage、Resolved mode、Resolved target，以及任何 override reason。
+- 如果已安装的 write 规则和当前轮次行为不一致，就先修正目标层或补充有效 override 理由，再继续编辑。
+
 ## 小步写作规则
 
 - 每轮只改一个 section 或一个明确子问题。
 - 最终稿必须是 LaTeX。
 - 普通起草轮次先跟随 \`workflow_language\`。
-- 普通写作轮次默认只改一个目标层，不要静默同时刷新两种语言层。
+- 当 \`workflow_language\` 与 \`paper_language\` 不一致时，把 workflow-language 论文层当成普通写作轮次的默认工作层。
+- 普通写作轮次仍然只改一个目标层，不要静默同时刷新两种语言层。
 - 如果用户明确点名了某个文件或层级，就把它当成当前轮次唯一目标，除非用户另外明确要求同步。
-- 如果 \`paper_language_finalization_decision=convert-to-paper-language\`，普通 canonical manuscript 工作可以直接落在 \`paper_language\`，但不要在同一轮里默认刷新 workflow-language 论文层。
+- 如果 workflow-language 论文层现役而本轮仍然写 canonical manuscript，必须在 write iteration artifact 里说明为什么这次 canonical-only 写作是合理的。
+- 如果 \`paper_language_finalization_decision=convert-to-paper-language\`，显式的 canonical manuscript 工作可以直接落在 \`paper_language\`，但这并不意味着只要 workflow-language 仍然现役，canonical 就变成普通轮次的默认工作层。
 - 把 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/\`。
@@ -2323,6 +2390,10 @@ description: 严格研究工作流，覆盖 idea、data、auto、framing、spec
 - 如果某个 stage 会决定后续方向，就要保留明确的 approval gate。
 - 使用 \`.lab/config/workflow.json\` 作为全局约束，统一管理 workflow language、paper language、paper format、results_root、figures_root、deliverables_root、paper_template_root 和 paper-language 的最终定稿决定。
 - 工作流中间工件默认跟随安装语言。
+- 每个 \`/lab:*\` stage 开始前，都要先读取 \`.lab/.managed/rule-manifest.json\` 并完成一段 \`Rule Preflight\`。
+- 每个 stage round 的受管工件都要先记录：Rule source file、Rule source revision、Project version、Resolved stage、Resolved mode、Resolved target，以及任何 override reason。
+- 如果 \`Rule Preflight\` 缺失、过期或和实际行为冲突，就把它视为 stage-contract failure，而不是继续润色或继续推进。
+- 项目里已安装的规则优先于模型记忆；如果记忆里的旧做法和 \`.lab/.managed/rule-manifest.json\` 记录的规则冲突，以项目里安装的规则为准。
 - 最终论文默认输出为 LaTeX，论文语言与工作流语言分开决定。
 - 区分“来源事实”和“模型假设”。
 - 保留失败实验、失败想法和局限性。
@@ -2800,6 +2871,14 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "auto.md")] = `# \`/la
 - \`.lab/context/auto-mode.md\`
 - \`.lab/context/auto-status.md\`
 - \`.lab/context/auto-outcome.md\`
+- \`.lab/.managed/rule-manifest.json\`
+
+## 规则预检
+
+- 启动 auto 前先读取 \`.lab/.managed/rule-manifest.json\`。
+- 可见的 \`Auto preflight\` 块里除了契约字段外，还要写明：Rule source file、Rule source revision、Project version、Resolved stage、Resolved mode、Resolved target，以及任何 override reason。
+- 这些 \`Rule Preflight\` 字段也要保存在 \`.lab/context/auto-status.md\`。
+- 如果已安装的 auto 规则和当前 campaign 行为不一致，就先修正契约或补充有效 override 理由，再启动 loop。
 
 ## 上下文写回
 
@@ -2899,8 +2978,10 @@ 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\` 版本。
-- 普通写作轮次默认只改一个目标层，不要在没有明确要求的情况下同时刷新 canonical manuscript 和 workflow-language 论文层。
+- 当 \`workflow_language\` 与 \`paper_language\` 不一致时，把 workflow-language 论文层当成普通写作轮次的默认工作层。
+- 普通写作轮次仍然只改一个目标层，不要在没有明确要求的情况下同时刷新 canonical manuscript 和 workflow-language 论文层。
 - 把 workflow-language 论文层当成正式持久化产物，而不是 review 层。
+- 如果 workflow-language 论文层现役而本轮仍然写 canonical manuscript，必须在最新 write iteration 里说明为什么这次 canonical-only 写作是合理的。
 - 如果当前写作目标是最终导出、\`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\`

package/lib/install.cjs

@@ -1,6 +1,7 @@
 const fs = require("node:fs");
 const os = require("node:os");
 const path = require("node:path");
+const crypto = require("node:crypto");
 const { CURRENT_AUTO_MODE_MIGRATION_FIELDS } = require("./auto_state.cjs");
 const { getLocalizedContent } = require("./i18n.cjs");
 
@@ -307,6 +308,10 @@ function installMetadataPath(targetDir) {
   return path.join(targetDir, ".lab", ".managed", "install.json");
 }
 
+function ruleManifestPath(targetDir) {
+  return path.join(targetDir, ".lab", ".managed", "rule-manifest.json");
+}
+
 function ensureParentDir(filePath) {
   fs.mkdirSync(path.dirname(filePath), { recursive: true });
 }
@@ -317,6 +322,44 @@ function writeProjectInstallMetadata(targetDir, metadata) {
   fs.writeFileSync(filePath, JSON.stringify(metadata, null, 2) + "\n");
 }
 
+function sha256(content) {
+  return crypto.createHash("sha256").update(content).digest("hex");
+}
+
+function buildRuleManifest(targetDir, metadata) {
+  const stages = Object.fromEntries(
+    LAB_STAGE_NAMES.map((stage) => {
+      const ruleSourceFile = path.join(".codex", "skills", "lab", "stages", `${stage}.md`);
+      const absoluteRuleSourceFile = path.join(targetDir, ruleSourceFile);
+      let ruleSourceRevision = "";
+      if (fs.existsSync(absoluteRuleSourceFile)) {
+        ruleSourceRevision = sha256(fs.readFileSync(absoluteRuleSourceFile, "utf8"));
+      }
+      return [
+        stage,
+        {
+          rule_source_file: ruleSourceFile.replace(/\\/g, "/"),
+          rule_source_revision: ruleSourceRevision,
+        },
+      ];
+    })
+  );
+
+  return {
+    package_version: metadata.package_version,
+    layout_version: metadata.layout_version,
+    generated_at: metadata.updated_at,
+    lab_skill_source_file: ".codex/skills/lab/SKILL.md",
+    stages,
+  };
+}
+
+function writeRuleManifest(targetDir, metadata) {
+  const filePath = ruleManifestPath(targetDir);
+  ensureParentDir(filePath);
+  fs.writeFileSync(filePath, JSON.stringify(buildRuleManifest(targetDir, metadata), null, 2) + "\n");
+}
+
 function readProjectInstallMetadata(targetDir) {
   const filePath = installMetadataPath(targetDir);
   if (!fs.existsSync(filePath)) {
@@ -732,6 +775,7 @@ function installSuperlab({
     updated_at: new Date().toISOString(),
   };
   writeProjectInstallMetadata(targetDir, metadata);
+  writeRuleManifest(targetDir, metadata);
   if (registerProject) {
     registerProjectInstall(targetDir, metadata, { env });
   }

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, the current section block in `section-style-policies.md`, 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. Ordinary write rounds should edit one target paper layer by default rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If `paper_language_finalization_decision=convert-to-paper-language`, ordinary canonical-manuscript work may target the canonical `paper_language` manuscript, but do not automatically refresh the workflow-language paper layer on the same round. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any cross-language sync justification, 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, the current section block in `section-style-policies.md`, 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. Ordinary write rounds should edit one target paper layer by default rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If `paper_language_finalization_decision=convert-to-paper-language`, ordinary canonical-manuscript work may target the canonical `paper_language` manuscript, but do not automatically refresh the workflow-language paper layer on the same round. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any cross-language sync justification, 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、`section-style-policies.md` 里与当前 section 对应的风格块，以及 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。普通写作轮次默认只改一个目标层，不要静默同时刷新两种语言层。如果用户明确点名了某个文件或层级，就把它当成当前轮次唯一目标，除非用户另外明确要求同步。如果 `paper_language_finalization_decision=convert-to-paper-language`，普通 canonical manuscript 工作可以直接落在 `paper_language`，但不要在同一轮里默认刷新 workflow-language 论文层。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、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。不要假定当前 section 可以无限继续压句子；在同一个 section 上做新的 tighten、compress 或 polish 之前，先过一遍 section-level acceptance gate。这个 gate 至少要显式确认命名一致性、前后文一致性、claim / metric / ranking 与当前证据的一致性、局部清晰度、局部简洁度，以及 section-style compliance。当前 section 的写作表达必须先遵守 `section-style-policies.md` 里的鼓励表达、谨慎表达和禁用表达；只要还有禁用表达或禁用写法残留，本轮就不能算通过 section-level acceptance gate。如果本轮改动的是论文当前的 canonical 实验或评测协议（例如 split 比例、训练/测试规模、seed 或 split 数量、benchmark 集合、主表评测口径），默认把它当成主协议替换，而不是补充实验；除非用户明确说这是 supplementary 或 appendix-only。遇到这种协议替换时，先做全文影响审计（paper-wide impact audit），列出哪些 section 和资产已经过期，优先更新影响最大的 canonical section / asset，再继续润色；不要默认去做 translation/workflow-layer 同步，除非用户明确要求，或者语言最终定稿流程要求这样做。只有在用户明确要求跨语言同步，或者 final-draft/export 的语言最终定稿步骤确实要求两层一起刷新时，才允许同一轮同时修改 canonical manuscript 和 workflow-language 论文层。不要把普通 tighten/compress/polish 请求理解成“顺手同步 companion”。如果当前是导出或远程发布轮次，且 `paper_language_finalization_decision=convert-to-paper-language`，默认把 workflow-language 论文层一起带进导出的或推送的 bundle。只有在用户明确要求只导出 canonical，或者远程目标明确不允许附带额外文件时，才允许 canonical-only export。如果任何一项还没过，就先解决这个 blocker，不要默认继续 prose polish，也不要把下一步建议自动写成“再收紧一轮”。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。不要把 `\\resizebox{\\linewidth}{!}{...}` 当成主表默认的宽度解决方案。主表如果超宽，先重构表：缩短表头但保留局部解释，把次要指标移到 appendix-only，减少或拆分列，最后才保守调整 `\\tabcolsep`；只有这些都做过仍然超宽时，才允许把 `\\resizebox` 当成最后手段，而且必须在同一张表的表注里解释宽度处理理由。不要把 `\\scriptsize` 或 `\\tiny` 当成主表默认的适配策略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检、section-level acceptance gate、section-style policy 合规检查、protocol/scope impact audit、export 或 remote bundle 审计、当前轮次目标层、任何跨语言同步理由，以及 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、`section-style-policies.md` 里与当前 section 对应的风格块，以及 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。普通写作轮次默认只改一个目标层，不要静默同时刷新两种语言层。如果用户明确点名了某个文件或层级，就把它当成当前轮次唯一目标，除非用户另外明确要求同步。如果 `paper_language_finalization_decision=convert-to-paper-language`，普通 canonical manuscript 工作可以直接落在 `paper_language`，但不要在同一轮里默认刷新 workflow-language 论文层。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、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。不要假定当前 section 可以无限继续压句子；在同一个 section 上做新的 tighten、compress 或 polish 之前，先过一遍 section-level acceptance gate。这个 gate 至少要显式确认命名一致性、前后文一致性、claim / metric / ranking 与当前证据的一致性、局部清晰度、局部简洁度，以及 section-style compliance。当前 section 的写作表达必须先遵守 `section-style-policies.md` 里的鼓励表达、谨慎表达和禁用表达；只要还有禁用表达或禁用写法残留，本轮就不能算通过 section-level acceptance gate。如果本轮改动的是论文当前的 canonical 实验或评测协议（例如 split 比例、训练/测试规模、seed 或 split 数量、benchmark 集合、主表评测口径），默认把它当成主协议替换，而不是补充实验；除非用户明确说这是 supplementary 或 appendix-only。遇到这种协议替换时，先做全文影响审计（paper-wide impact audit），列出哪些 section 和资产已经过期，优先更新影响最大的 canonical section / asset，再继续润色；不要默认去做 translation/workflow-layer 同步，除非用户明确要求，或者语言最终定稿流程要求这样做。只有在用户明确要求跨语言同步，或者 final-draft/export 的语言最终定稿步骤确实要求两层一起刷新时，才允许同一轮同时修改 canonical manuscript 和 workflow-language 论文层。不要把普通 tighten/compress/polish 请求理解成“顺手同步 companion”。如果当前是导出或远程发布轮次，且 `paper_language_finalization_decision=convert-to-paper-language`，默认把 workflow-language 论文层一起带进导出的或推送的 bundle。只有在用户明确要求只导出 canonical，或者远程目标明确不允许附带额外文件时，才允许 canonical-only export。如果任何一项还没过，就先解决这个 blocker，不要默认继续 prose polish，也不要把下一步建议自动写成“再收紧一轮”。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。不要把 `\\resizebox{\\linewidth}{!}{...}` 当成主表默认的宽度解决方案。主表如果超宽，先重构表：缩短表头但保留局部解释，把次要指标移到 appendix-only，减少或拆分列，最后才保守调整 `\\tabcolsep`；只有这些都做过仍然超宽时，才允许把 `\\resizebox` 当成最后手段，而且必须在同一张表的表注里解释宽度处理理由。不要把 `\\scriptsize` 或 `\\tiny` 当成主表默认的适配策略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检、section-level acceptance gate、section-style policy 合规检查、protocol/scope impact audit、export 或 remote bundle 审计、当前轮次目标层、任何跨语言同步理由，以及 table-semantics 审计一起写进 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, the current section block in `section-style-policies.md`, 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. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, 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, the current section block in `section-style-policies.md`, 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. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\\resizebox{\\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\\tabcolsep` conservatively; only use `\\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\\scriptsize` or `\\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, 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、`section-style-policies.md` 里与当前 section 对应的风格块，以及 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。当 `workflow_language` 与 `paper_language` 不一致时，把 workflow-language 论文层当成普通写作轮次的默认工作层。普通写作轮次仍然只改一个目标层，不要静默同时刷新两种语言层。如果用户明确点名了某个文件或层级，就把它当成当前轮次唯一目标，除非用户另外明确要求同步。如果 workflow-language 论文层现役而本轮仍然写 canonical manuscript，必须在 write iteration artifact 里说明为什么这次 canonical-only 写作是合理的。如果 `paper_language_finalization_decision=convert-to-paper-language`，显式的 canonical manuscript 工作可以直接落在 `paper_language`，但这并不意味着只要 workflow-language 仍然现役，canonical 就变成普通轮次的默认工作层。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、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。不要假定当前 section 可以无限继续压句子；在同一个 section 上做新的 tighten、compress 或 polish 之前，先过一遍 section-level acceptance gate。这个 gate 至少要显式确认命名一致性、前后文一致性、claim / metric / ranking 与当前证据的一致性、局部清晰度、局部简洁度，以及 section-style compliance。当前 section 的写作表达必须先遵守 `section-style-policies.md` 里的鼓励表达、谨慎表达和禁用表达；只要还有禁用表达或禁用写法残留，本轮就不能算通过 section-level acceptance gate。如果本轮改动的是论文当前的 canonical 实验或评测协议（例如 split 比例、训练/测试规模、seed 或 split 数量、benchmark 集合、主表评测口径），默认把它当成主协议替换，而不是补充实验；除非用户明确说这是 supplementary 或 appendix-only。遇到这种协议替换时，先做全文影响审计（paper-wide impact audit），列出哪些 section 和资产已经过期，优先更新影响最大的 canonical section / asset，再继续润色；不要默认去做 translation/workflow-layer 同步，除非用户明确要求，或者语言最终定稿流程要求这样做。只有在用户明确要求跨语言同步，或者 final-draft/export 的语言最终定稿步骤确实要求两层一起刷新时，才允许同一轮同时修改 canonical manuscript 和 workflow-language 论文层。不要把普通 tighten/compress/polish 请求理解成“顺手同步 companion”。如果当前是导出或远程发布轮次，且 `paper_language_finalization_decision=convert-to-paper-language`，默认把 workflow-language 论文层一起带进导出的或推送的 bundle。只有在用户明确要求只导出 canonical，或者远程目标明确不允许附带额外文件时，才允许 canonical-only export。如果任何一项还没过，就先解决这个 blocker，不要默认继续 prose polish，也不要把下一步建议自动写成“再收紧一轮”。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。不要把 `\\resizebox{\\linewidth}{!}{...}` 当成主表默认的宽度解决方案。主表如果超宽，先重构表：缩短表头但保留局部解释，把次要指标移到 appendix-only，减少或拆分列，最后才保守调整 `\\tabcolsep`；只有这些都做过仍然超宽时，才允许把 `\\resizebox` 当成最后手段，而且必须在同一张表的表注里解释宽度处理理由。不要把 `\\scriptsize` 或 `\\tiny` 当成主表默认的适配策略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检、section-level acceptance gate、section-style policy 合规检查、protocol/scope impact audit、export 或 remote bundle 审计、当前轮次目标层、workflow-language 现役时的 canonical-only 理由、任何跨语言同步理由，以及 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、`section-style-policies.md` 里与当前 section 对应的风格块，以及 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把 workflow-language 论文层当成正式持久化产物，而不是 review 层。当 `workflow_language` 与 `paper_language` 不一致时，把 workflow-language 论文层当成普通写作轮次的默认工作层。普通写作轮次仍然只改一个目标层，不要静默同时刷新两种语言层。如果用户明确点名了某个文件或层级，就把它当成当前轮次唯一目标，除非用户另外明确要求同步。如果 workflow-language 论文层现役而本轮仍然写 canonical manuscript，必须在 write iteration artifact 里说明为什么这次 canonical-only 写作是合理的。如果 `paper_language_finalization_decision=convert-to-paper-language`，显式的 canonical manuscript 工作可以直接落在 `paper_language`，但这并不意味着只要 workflow-language 仍然现役，canonical 就变成普通轮次的默认工作层。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、表注和图注；如果术语第一次出现在表里，就必须在同一张表里局部解释。不要假定当前 section 可以无限继续压句子；在同一个 section 上做新的 tighten、compress 或 polish 之前，先过一遍 section-level acceptance gate。这个 gate 至少要显式确认命名一致性、前后文一致性、claim / metric / ranking 与当前证据的一致性、局部清晰度、局部简洁度，以及 section-style compliance。当前 section 的写作表达必须先遵守 `section-style-policies.md` 里的鼓励表达、谨慎表达和禁用表达；只要还有禁用表达或禁用写法残留，本轮就不能算通过 section-level acceptance gate。如果本轮改动的是论文当前的 canonical 实验或评测协议（例如 split 比例、训练/测试规模、seed 或 split 数量、benchmark 集合、主表评测口径），默认把它当成主协议替换，而不是补充实验；除非用户明确说这是 supplementary 或 appendix-only。遇到这种协议替换时，先做全文影响审计（paper-wide impact audit），列出哪些 section 和资产已经过期，优先更新影响最大的 canonical section / asset，再继续润色；不要默认去做 translation/workflow-layer 同步，除非用户明确要求，或者语言最终定稿流程要求这样做。只有在用户明确要求跨语言同步，或者 final-draft/export 的语言最终定稿步骤确实要求两层一起刷新时，才允许同一轮同时修改 canonical manuscript 和 workflow-language 论文层。不要把普通 tighten/compress/polish 请求理解成“顺手同步 companion”。如果当前是导出或远程发布轮次，且 `paper_language_finalization_decision=convert-to-paper-language`，默认把 workflow-language 论文层一起带进导出的或推送的 bundle。只有在用户明确要求只导出 canonical，或者远程目标明确不允许附带额外文件时，才允许 canonical-only export。如果任何一项还没过，就先解决这个 blocker，不要默认继续 prose polish，也不要把下一步建议自动写成“再收紧一轮”。主表必须局部自足：读者只看表题、表头、表注和邻近引入或解读，就应当知道每行是什么、每列是什么、指标方向是什么，以及需要的单位、分母或触发条件。表头可以短，但表里的缩写必须在同表局部展开。如果 Method 或 Experiments 承诺了一组指标，主表就必须直接展示这些指标，或者明确标成 appendix-only 并解释原因；如果某个指标因为恒为零、冗余或只放附录而不单列，也必须在表注里显式说明，不能静默省略。不要把 `\\resizebox{\\linewidth}{!}{...}` 当成主表默认的宽度解决方案。主表如果超宽，先重构表：缩短表头但保留局部解释，把次要指标移到 appendix-only，减少或拆分列，最后才保守调整 `\\tabcolsep`；只有这些都做过仍然超宽时，才允许把 `\\resizebox` 当成最后手段，而且必须在同一张表的表注里解释宽度处理理由。不要把 `\\scriptsize` 或 `\\tiny` 当成主表默认的适配策略。内部标识符默认不要进入 reader-facing prose；若必须出现，只能在完成一次读者映射后使用，并把 terminology-clarity 自检、section-level acceptance gate、section-style policy 合规检查、protocol/scope impact audit、export 或 remote bundle 审计、当前轮次目标层、workflow-language 现役时的 canonical-only 理由、任何跨语言同步理由，以及 table-semantics 审计一起写进 write iteration artifact。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 论文层，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 论文层路径，最后才允许按该语言修改最终稿。"
   }
 }

package/lib/rule_preflight.cjs

@@ -0,0 +1,52 @@
+const fs = require("node:fs");
+const path = require("node:path");
+
+function ruleManifestPath(targetDir) {
+  return path.join(targetDir, ".lab", ".managed", "rule-manifest.json");
+}
+
+function readRuleManifest(targetDir) {
+  const manifestPath = ruleManifestPath(targetDir);
+  if (!fs.existsSync(manifestPath)) {
+    return null;
+  }
+  return JSON.parse(fs.readFileSync(manifestPath, "utf8"));
+}
+
+function resolveStageRuleEntry(targetDir, stage) {
+  const manifest = readRuleManifest(targetDir);
+  if (!manifest || !manifest.stages || !manifest.stages[stage]) {
+    return null;
+  }
+  return {
+    packageVersion: manifest.package_version || "",
+    ruleSourceFile: manifest.stages[stage].rule_source_file || "",
+    ruleSourceRevision: manifest.stages[stage].rule_source_revision || "",
+  };
+}
+
+function buildRulePreflight({
+  targetDir,
+  stage,
+  mode = "",
+  target = "",
+  overrideReason = "",
+} = {}) {
+  const entry = resolveStageRuleEntry(targetDir, stage) || {};
+  return {
+    ruleSourceFile: entry.ruleSourceFile || "",
+    ruleSourceRevision: entry.ruleSourceRevision || "",
+    projectVersion: entry.packageVersion || "",
+    resolvedStage: stage || "",
+    resolvedMode: mode || "",
+    resolvedTarget: target || "",
+    overrideReason: overrideReason || "",
+  };
+}
+
+module.exports = {
+  buildRulePreflight,
+  readRuleManifest,
+  resolveStageRuleEntry,
+  ruleManifestPath,
+};

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, the current section block in `section-style-policies.md`, 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. Ordinary write rounds should edit one target paper layer by default rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If `paper_language_finalization_decision=convert-to-paper-language`, ordinary canonical-manuscript work may target the canonical `paper_language` manuscript, but do not automatically refresh the workflow-language paper layer on the same round. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any cross-language sync justification, 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.
+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, the current section block in `section-style-policies.md`, 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. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, 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, the current section block in `section-style-policies.md`, 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. Ordinary write rounds should edit one target paper layer by default rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If `paper_language_finalization_decision=convert-to-paper-language`, ordinary canonical-manuscript work may target the canonical `paper_language` manuscript, but do not automatically refresh the workflow-language paper layer on the same round. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any cross-language sync justification, 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.
+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, the current section block in `section-style-policies.md`, 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. When `workflow_language` and `paper_language` differ, treat the workflow-language paper layer as the default ordinary working layer. Ordinary write rounds should still edit one target paper layer at a time rather than silently refreshing both language layers. If the user names a concrete file or layer, treat that as the only target for the round unless they also explicitly request synchronization. If a workflow-language paper layer is active and the round still targets the canonical manuscript, record why canonical-only writing was acceptable in the write iteration artifact. If `paper_language_finalization_decision=convert-to-paper-language`, explicit canonical-manuscript work may target the canonical `paper_language` manuscript, but that does not make canonical the default ordinary working layer while workflow-language remains active. 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, apply the same first-mention rule to table headers, table captions, table notes, and figure captions or labels, do not assume a fixed drafting order such as Method before Experiments, add a local naming bridge when a section uses canonical short names before their defining section has been drafted, and reuse the canonical label instead of replacing it with a narrative alias. Follow the current section's encouraged, discouraged, and banned expression lists from `section-style-policies.md`; section-specific banned expressions take priority over prose-polish goals. Before any additional tighten, compress, or polish pass on the same section, run a section-level acceptance gate first. That gate must explicitly confirm naming consistency, adjacent-section consistency, claim, metric, and ranking consistency with the current evidence, local clarity, local concision, and section-style compliance. If the round changes the paper's canonical experiment or evaluation protocol, treat that change as a canonical replacement unless the user explicitly scoped it as supplementary or appendix-only, run a paper-wide impact audit before more polishing, update the highest-impact stale sections and assets first, and do not default to translation/workflow-layer sync work unless the user explicitly asked for it or the language-finalization workflow requires it. Only edit both the canonical manuscript and the workflow-language paper layer in the same round when the user explicitly asks for cross-language synchronization or when a final-draft/export language-finalization step requires both layers to be refreshed together. Do not treat a routine tighten/compress/polish request as an instruction to sync the workflow-language companion. For export or remote-publication rounds, if `paper_language_finalization_decision=convert-to-paper-language`, include the workflow-language paper layer in the exported or pushed bundle by default. Allow canonical-only export or remote publication only when the user explicitly asked for it or when the remote target forbids extra files. If any gate item is unresolved, or if a banned expression or move from the current section policy remains, spend the round fixing that blocker instead of polishing sentences further, and do not default the next-step recommendation to another polish pass. 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. Do not treat `\resizebox{\linewidth}{!}{...}` as the default way to fit a main table. Fit main tables by redesign first: shorten headers, move secondary metrics out of the main table, reduce or split columns, then adjust `\tabcolsep` conservatively; only use `\resizebox` as a last resort, keep width changes readable, and explain the width-control rationale locally in the same table note. Do not use `\scriptsize` or `\tiny` as the default main-table fit strategy. 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, the section-level acceptance gate, section-style policy compliance, the protocol/scope impact audit, the export or remote bundle audit, the round target layer, any canonical-only justification while workflow-language was active, any cross-language sync justification, 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.