superlab 0.1.8 → 0.1.9

package/lib/i18n.cjs

@@ -23,6 +23,11 @@ ${body}
 }
 
 const ZH_CONTENT = {
+  [path.join(".codex", "prompts", "lab.md")]: codexPrompt(
+    "查看 /lab 研究工作流总览并选择合适阶段",
+    "workflow question 或 stage choice",
+    "# `/lab` for Codex\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n"
+  ),
   [path.join(".codex", "prompts", "lab-idea.md")]: codexPrompt(
     "在进入规格前调研并打磨论文或实验想法",
     "idea 或 research problem",
@@ -31,7 +36,7 @@ const ZH_CONTENT = {
   [path.join(".codex", "prompts", "lab-framing.md")]: codexPrompt(
     "在写作前收紧方法名、模块名、论文题目和 contribution framing",
     "naming、title 或 contribution framing target",
-    "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:framing`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:framing` 阶段。它必须围绕 paper-facing framing，收紧方法名、模块名、题目和 contribution bullets，审查术语是否 canonical、对象是否明确，并在进入 `/lab:write` 前保留 approval gate。"
+    "使用已安装的 `lab` 技能：`.codex/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:framing`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:framing` 阶段。它必须围绕 paper-facing framing，收紧方法名、模块名、题目和 contribution bullets，审查当前领域与相邻领域的术语是否 canonical、对象是否明确，并在进入 `/lab:write` 前保留 approval gate。"
   ),
   [path.join(".codex", "prompts", "lab-spec.md")]: codexPrompt(
     "把已批准的 idea 转成统一的 lab change 目录",
@@ -69,11 +74,17 @@ const ZH_CONTENT = {
     "workflow, research, idea",
     "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:idea`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:idea` 阶段。它必须先用清晰简洁的话定义问题与失败场景，说明现有方法哪里不够、我们的想法为何更好，再做 idea classification、contribution category、breakthrough level 的归类，并收束出至少三个一眼就有意义的点，最后保留进入 `/lab:spec` 前的 approval gate。"
   ),
+  [path.join(".claude", "commands", "lab.md")]: claudeCommand(
+    "LAB",
+    "查看 /lab 研究工作流总览并选择合适阶段",
+    "workflow, research, overview",
+    "# `/lab` for Claude\n\n`/lab` 是严格的研究工作流命令族。每次都使用同一套仓库工件和阶段边界。\n\n## 子命令\n\n- `/lab:idea`\n  调研 idea，定义问题与 failure case，归类 contribution 与 breakthrough level，对比现有方法，收束三个一眼就有意义的点，并在实现前保留 approval gate。\n\n- `/lab:framing`\n  通过审计当前领域与相邻领域的术语，锁定 paper-facing 的方法名、模块名、论文题目和 contribution bullets，并在 section 起草前保留 approval gate。\n\n- `/lab:spec`\n  把已批准的 idea 转成 `.lab/changes/<change-id>/` 下的一个 lab change 目录，并在其中写出 `proposal`、`design`、`spec`、`tasks`。\n\n- `/lab:run`\n  执行最小有意义验证运行，登记 run，并生成第一版标准化评估摘要。\n\n- `/lab:iterate`\n  在冻结 mission、阈值、verification commands 与 `completion_promise` 的前提下执行有边界的实验迭代。\n\n- `/lab:review`\n  以 reviewer mode 审查文档或结果，先给短摘要，再输出 findings、fatal flaws、fix priority 和 residual risks。\n\n- `/lab:report`\n  从 runs 和 iterations 工件生成最终研究报告。\n\n- `/lab:write`\n  使用已安装 `lab` skill 下 vendored 的 paper-writing references，把稳定 report 工件转成论文 section。\n\n## 调度规则\n\n- 始终使用 `skills/lab/SKILL.md` 作为工作流合同。\n- 用户显式调用 `/lab:<stage>` 时，要立刻执行该 stage，而不是只推荐别的 `/lab` stage。\n- 先给简洁摘要，再决定是否写工件，最后回报输出路径和下一步。\n- 如果歧义会影响结论，一次只问一个问题；如果有多条可行路径，先给 2-3 个方案再收敛。\n- `/lab:write` 前必须已有经批准的 `/lab:framing` 工件。\n"
+  ),
   [path.join(".claude", "commands", "lab", "framing.md")]: claudeCommand(
     "LAB: Framing",
     "在写作前收紧方法名、模块名、论文题目和 contribution framing",
     "workflow, research, framing",
-    "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:framing`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:framing` 阶段。它必须围绕 paper-facing framing，收紧方法名、模块名、题目和 contribution bullets，审查术语是否 canonical、对象是否明确，并在进入 `/lab:write` 前保留 approval gate。"
+    "使用已安装的 `lab` 技能：`.claude/skills/lab/SKILL.md`。\n\n立刻针对用户当前给出的参数执行 `/lab:framing`，不要只推荐别的 `/lab` 阶段。只有在缺少阻塞性前提时，才明确指出缺什么，并且一次最多追问一个问题。\n\n本命令运行 `/lab:framing` 阶段。它必须围绕 paper-facing framing，收紧方法名、模块名、题目和 contribution bullets，审查当前领域与相邻领域的术语是否 canonical、对象是否明确，并在进入 `/lab:write` 前保留 approval gate。"
   ),
   [path.join(".claude", "commands", "lab", "spec.md")]: claudeCommand(
     "LAB: Spec",
@@ -1189,7 +1200,8 @@ ZH_CONTENT[path.join(".lab", "context", "terminology-lock.md")] = `# 已批准
 
 ## Source Audit
 
-- 查阅过的近期学术论文：
+- 查阅过的当前领域来源：
+- 查阅过的相邻领域来源：
 - 查阅过的 primary sources：
 - 为什么当前 wording 可以接受：
 `;
@@ -1247,18 +1259,24 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "framing.md")] = `# \`
 - \`.lab/context/mission.md\`
 - \`.lab/context/decisions.md\`
 - \`.lab/context/evidence-index.md\`
+- \`.lab/context/terminology-lock.md\`
 
 ## 上下文写回
 
 - \`.lab/context/state.md\`
 - \`.lab/context/decisions.md\`
+- \`.lab/context/terminology-lock.md\`
 
 ## 必要工件
 
 - \`.lab/writing/framing.md\`
+- \`.lab/context/terminology-lock.md\`
 
 ## 命名审计规则
 
+- 锁定不熟悉术语前，先查当前领域近期论文和其他 primary sources。
+- 如果当前领域没有稳定 canonical term，或相邻领域有可平移的表达，再查相邻领域。
+- 记录术语来源日志，说明看过哪些当前领域来源、哪些相邻领域来源，以及为何接受最终 wording。
 - 术语要说明是 canonical、adapted 还是 newly coined。
 - 尽量把对象说清楚：到底在 calibrate、rank、estimate 什么。
 - 不要用 acronym-first 命名。
@@ -1333,11 +1351,13 @@ ZH_CONTENT[path.join(".lab", ".managed", "templates", "framing.md")] = `# 论文
 
 ## Canonical Terminology Audit
 
-- 应复用的标准术语：
+- 当前领域应优先复用的术语：
+- 相邻领域可借用的术语：
 - 可接受的改写术语：
 - 需要谨慎的新造术语：
 - 必须说清楚的对象：
 - 应避免的术语：
+- 术语来源日志：
 
 ## Candidate Framing Packs
 

package/lib/install.cjs

@@ -22,8 +22,8 @@ const ASSET_GROUPS = {
   ],
   claude: [
     {
-      from: path.join(REPO_ROOT, "package-assets", "claude", "commands", "lab"),
-      to: path.join(".claude", "commands", "lab"),
+      from: path.join(REPO_ROOT, "package-assets", "claude", "commands"),
+      to: path.join(".claude", "commands"),
     },
     {
       from: path.join(REPO_ROOT, "package-assets", "shared", "skills", "lab"),
@@ -439,6 +439,7 @@ function localizeInstalledAssets(targetDir, lang, { newlyCreatedProjectOwnedPath
   }
 
   const relativePaths = [
+    path.join(".codex", "prompts", "lab.md"),
     path.join(".codex", "prompts", "lab-idea.md"),
     path.join(".codex", "prompts", "lab-framing.md"),
     path.join(".codex", "prompts", "lab-spec.md"),
@@ -447,6 +448,7 @@ function localizeInstalledAssets(targetDir, lang, { newlyCreatedProjectOwnedPath
     path.join(".codex", "prompts", "lab-review.md"),
     path.join(".codex", "prompts", "lab-report.md"),
     path.join(".codex", "prompts", "lab-write.md"),
+    path.join(".claude", "commands", "lab.md"),
     path.join(".claude", "commands", "lab", "idea.md"),
     path.join(".claude", "commands", "lab", "framing.md"),
     path.join(".claude", "commands", "lab", "spec.md"),

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

@@ -0,0 +1,48 @@
+---
+name: "LAB"
+description: Overview of the /lab research workflow and stage selection
+category: Workflow
+tags: [workflow, research, overview]
+---
+
+# `/lab` for Claude
+
+`/lab` is a strict research workflow command family. Use the same repository artifacts and stage boundaries every time.
+
+## Subcommands
+
+- `/lab:idea`
+  Research the idea, define the problem and failure case, classify the contribution and breakthrough level, compare against existing methods, end with three meaningful points, and keep an explicit approval gate before any implementation.
+
+- `/lab:framing`
+  Lock paper-facing method name, module names, paper title, and contribution bullets by auditing current-field and adjacent-field terminology, then keep an approval gate before any section drafting.
+
+- `/lab:spec`
+  Convert the approved idea into one lab change directory under `.lab/changes/<change-id>/`, then draft `proposal`, `design`, `spec`, and `tasks` inside that directory.
+
+- `/lab:run`
+  Execute the smallest useful validation run, register it, and produce the first normalized evaluation summary.
+
+- `/lab:iterate`
+  Run bounded Ralph Wiggum style experiment loops with a frozen mission, explicit thresholds, deterministic verification commands, `completion_promise`, and per-round reports.
+
+- `/lab:review`
+  Audit documents or results in reviewer mode. Start with a short summary, then output findings, fatal flaws, fix priority, and residual risks.
+
+- `/lab:report`
+  Generate the final research report from accumulated runs and iteration artifacts.
+
+- `/lab:write`
+  Turn stable report artifacts into paper sections through small, evidence-bound writing rounds using the vendored paper-writing references under the installed `lab` skill.
+
+## Dispatch Rules
+
+- Always use `skills/lab/SKILL.md` as the workflow contract.
+- When the user explicitly invokes `/lab:<stage>`, execute that stage now against the provided argument instead of only recommending another `/lab` stage.
+- Start by giving the user a concise summary, then decide whether to write artifacts, then report the output path and next step.
+- When ambiguity matters, ask one clarifying question at a time; when multiple paths are viable, present 2-3 approaches before converging.
+- `/lab:spec` is not complete until the approved change is frozen under `.lab/changes/<change-id>/`.
+- Never skip directly from `/lab:idea` to code.
+- `/lab:iterate` requires a normalized summary from `scripts/eval_report.py`.
+- `/lab:write` requires an approved framing artifact from `/lab:framing`.
+- `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.

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

@@ -0,0 +1,46 @@
+---
+description: Overview of the /lab research workflow and stage selection
+argument-hint: workflow question or stage choice
+---
+
+# `/lab` for Codex
+
+`/lab` is a strict research workflow command family. Use the same repository artifacts and stage boundaries every time.
+
+## Subcommands
+
+- `/lab:idea`
+  Research the idea, define the problem and failure case, classify the contribution and breakthrough level, compare against existing methods, end with three meaningful points, and keep an explicit approval gate before any implementation.
+
+- `/lab:framing`
+  Lock paper-facing method name, module names, paper title, and contribution bullets by auditing current-field and adjacent-field terminology, then keep an approval gate before any section drafting.
+
+- `/lab:spec`
+  Convert the approved idea into one lab change directory under `.lab/changes/<change-id>/`, then draft `proposal`, `design`, `spec`, and `tasks` inside that directory.
+
+- `/lab:run`
+  Execute the smallest useful validation run, register it, and produce the first normalized evaluation summary.
+
+- `/lab:iterate`
+  Run bounded Ralph Wiggum style experiment loops with a frozen mission, explicit thresholds, deterministic verification commands, `completion_promise`, and per-round reports.
+
+- `/lab:review`
+  Audit documents or results in reviewer mode. Start with a short summary, then output findings, fatal flaws, fix priority, and residual risks.
+
+- `/lab:report`
+  Generate the final research report from accumulated runs and iteration artifacts.
+
+- `/lab:write`
+  Turn stable report artifacts into paper sections through small, evidence-bound writing rounds using the vendored paper-writing references under the installed `lab` skill.
+
+## Dispatch Rules
+
+- Always use `skills/lab/SKILL.md` as the workflow contract.
+- When the user explicitly invokes `/lab:<stage>`, execute that stage now against the provided argument instead of only recommending another `/lab` stage.
+- Start by giving the user a concise summary, then decide whether to write artifacts, then report the output path and next step.
+- When ambiguity matters, ask one clarifying question at a time; when multiple paths are viable, present 2-3 approaches before converging.
+- `/lab:spec` is not complete until the approved change is frozen under `.lab/changes/<change-id>/`.
+- Never skip directly from `/lab:idea` to code.
+- `/lab:iterate` requires a normalized summary from `scripts/eval_report.py`.
+- `/lab:write` requires an approved framing artifact from `/lab:framing`.
+- `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.

package/package-assets/shared/lab/.managed/templates/framing.md

@@ -8,11 +8,13 @@
 
 ## Canonical Terminology Audit
 
-- Standard terms we should reuse:
+- Current field terms we should prefer:
+- Adjacent-field terms worth borrowing:
 - Adapted terms we can justify:
 - Newly coined terms that need caution:
 - Objects that must be explicit:
 - Terms to avoid:
+- Terminology source log:
 
 ## Candidate Framing Packs
 

package/package-assets/shared/lab/context/terminology-lock.md

@@ -22,6 +22,7 @@ Record the currently approved naming and wording that later stages should reuse
 
 ## Source Audit
 
-- Recent academic papers reviewed:
+- Current-field sources reviewed:
+- Adjacent-field sources reviewed:
 - Primary sources reviewed:
 - Why the approved wording is acceptable:

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

@@ -37,7 +37,9 @@
 
 - Keep framing decisions tied to supported claims, not to speculative novelty.
 - Audit method name, module names, paper title, and contribution bullets as one package.
-- Review recent academic papers and other primary sources before locking unfamiliar terminology.
+- Review recent academic papers and other primary sources from the current field before locking unfamiliar terminology.
+- Review adjacent fields when the current field lacks a stable canonical term or when a neighboring term may transfer cleanly.
+- Record a source log for terminology decisions, including which current-field and adjacent-field sources were checked.
 - State whether each important term is canonical, adapted, or newly coined.
 - Prefer names that make the object explicit.
 - Avoid names that read like AI-packaged branding, unexplained acronyms, or implementation patch labels.
@@ -63,7 +65,7 @@
 
 1. Framing target
 2. Current naming and wording risks
-3. Canonical terminology audit
+3. Canonical terminology audit across current and adjacent fields
 4. Candidate framing packs
 5. Recommended framing pack
 6. Forbidden claims and wording

package/package.json

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