superlab 0.1.35 → 0.1.37

package/lib/i18n.cjs

@@ -471,6 +471,8 @@ const ZH_SKILL_FILES = {
 - 不要在没有文献范围包和最接近前作对照的情况下直接下 novelty 判断。
 - 不要在只做了一轮脑暴或一轮文献检索的情况下直接下 final recommendation。
 - 不要把 idea 工件本身当成唯一证据记录；两轮文献检索的查询、来源分桶和最终来源数必须同步记到 \`.lab/writing/idea-source-log.md\`。
+- 在 \`idea\` 阶段可以说大致怎么验证、最小实验是什么，但不要在这里冻结 sample size、招募方案、条件数、问卷设计或随机化 protocol。
+- human-subject experiment design 应该留到 \`/lab:spec\`，在那里再把招募、分组、测量和伦理细节写死。
 - 三个 meaningful points 每个都控制在一句直接的话里。
 - 在批准前，必须运行 \`.lab/.managed/scripts/validate_idea_artifact.py --idea <idea-artifact> --source-log .lab/writing/idea-source-log.md --workflow-config .lab/config/workflow.json\`。
 - rewrite-only 模式下不能更新 \`.lab/context/mission.md\`、\`.lab/context/decisions.md\` 或 \`.lab/context/open-questions.md\`。
@@ -1890,6 +1892,7 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "write.md")] = `# \`/l
 - 如果 \`paper_template_decision\` 已经是 \`default-scaffold\`，就使用交付目录下的默认 LaTeX scaffold。
 - 如果当前是最终导出或最终定稿轮次、\`paper_template_root\` 仍为空、\`paper_template_decision\` 是 \`default-scaffold\`，且 \`paper_template_final_reminder_acknowledged\` 是 \`false\`，就在最终定稿前再提醒一次是否切到模板。
 - 如果用户在最终提醒里仍确认继续使用默认 scaffold，就把 \`paper_template_final_reminder_acknowledged\` 持久化为 \`true\`。
+- 普通 manuscript 起草轮次虽然也是 LaTeX，但普通 \`.tex\` section 草稿必须先跟随 \`workflow_language\`，不要把 \`paper_language\` 当成默认草稿语言。
 - 如果当前是最终导出或最终定稿轮次，且 \`workflow_language\` 与 \`paper_language\` 不一致、\`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前 workflow language，还是把 canonical manuscript 转换成 \`paper_language\`。
 - 如果用户选择保持当前 workflow language，就把 \`paper_language_finalization_decision\` 持久化成 \`keep-workflow-language\`。
 - 如果用户选择转换成最终论文语言，就把 \`paper_language_finalization_decision\` 持久化成 \`convert-to-paper-language\`。
@@ -2191,6 +2194,7 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "spec.md")] = `# \`/la
 - 把已批准的 idea 转成显式要求。
 - 把已批准的数据集与 benchmark 方案带进 change。
 - 保留 idea 阶段冻结下来的评估边界。
+- 如果已批准的 idea 包含 human-subject evaluation，就在这里把 rough evaluation sketch 具体化成明确的人类受试实验设计，不要把招募或 protocol 细节继续留空。
 - 尽可能把风险翻译成具体任务。
 - 任务粒度要足够小，便于 \`/lab:run\` 和 \`/lab:iterate\` 可预测执行。
 - 一个被批准的 idea 只对应一个 lab-native change 目录，不要分散。
@@ -2210,6 +2214,13 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "spec.md")] = `# \`/la
 - split verification
 - preprocessing
 - benchmark protocol
+- human-subject experiment design
+- participant recruitment
+- sample-size rationale
+- condition design
+- assignment or randomization protocol
+- measurement or survey plan
+- ethics、consent 和 debrief 方案（如适用）
 - artifact creation
 - validation run
 - evaluation normalization
@@ -2629,6 +2640,7 @@ ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "auto.md")] = `# \`/la
   - 如果当前是最终导出或最终定稿、\`paper_template_decision\` 是 \`default-scaffold\`，且 \`paper_template_final_reminder_acknowledged\` 是 \`false\`，就在最终定稿前再提醒一次
   - 如果用户在最终提醒里仍确认继续使用默认 scaffold，就持久化 \`paper_template_final_reminder_acknowledged: true\`
 - 普通 \`write\` 起草轮次先跟随 \`workflow_language\`。
+- 普通 \`write\` 起草轮次里的 manuscript 仍然是 LaTeX，所以普通 manuscript \`.tex\` sections 也必须先保留在 \`workflow_language\`，还不是 \`paper_language\` 版本。
 - 把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。
 - 如果当前写作目标是最终导出、\`workflow_language\` 与 \`paper_language\` 不一致，且 \`paper_language_finalization_decision\` 还是 \`unconfirmed\`，就在最终定稿前先完成并保留 workflow-language 交付稿，再追问一次：保持当前 workflow language，还是转换成 \`paper_language\`
 - 如果用户选择保持当前语言，就持久化 \`paper_language_finalization_decision: keep-workflow-language\`

package/lib/lab_write_contract.json

@@ -1,8 +1,8 @@
 {
   "stage_prompt": {
-    "codex_en": "This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
-    "claude_en": "This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
-    "codex_zh": "本命令运行 `/lab:write` 阶段。把 `.codex/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。",
-    "claude_zh": "本命令运行 lab workflow 的 `write` 阶段。把 `.claude/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。"
+    "codex_en": "This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
+    "claude_en": "This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.",
+    "codex_zh": "本命令运行 `/lab:write` 阶段。把 `.codex/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。",
+    "claude_zh": "本命令运行 lab workflow 的 `write` 阶段。把 `.claude/skills/lab/stages/write.md` 当成模板选择、paper-plan、section 参考、校验 gate、资产覆盖和最终 manuscript 规则的单一来源。读取与当前 section 对应的 paper-writing reference 和 bundled example-bank 文件，一次只修改一个 section；普通草稿轮次把写作校验当 warning，最终定稿或导出轮次必须满足 write-stage 的接受 gate。普通起草轮次先跟随 `workflow_language`，普通 `.tex` section 草稿也必须先停留在 `workflow_language`，不能把 `paper_language` 当成默认草稿语言，并把可阅读的 workflow-language 交付稿当成正式持久化产物，而不是 review 层。如果当前稿件将从托管默认 scaffold 开始，且还没有模板决定，就先追问一次：继续使用默认 scaffold，还是先接入模板目录。如果进入最终定稿时 `workflow_language` 与 `paper_language` 不一致，就先完成并保留 workflow-language 交付稿，再追问一次：保持当前语言，还是把 canonical manuscript 转成 `paper_language`；先持久化这个决定，再在最新 write iteration 里记录语言决策和 workflow-language 交付稿路径，最后才允许按该语言修改最终稿。"
   }
 }

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

@@ -7,4 +7,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-write` command against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
-This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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

@@ -6,4 +6,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
-This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/shared/lab/system/core.md

@@ -30,7 +30,7 @@ For auto-mode orchestration or long-running experiment campaigns, also read:
 - Durable run outputs belong under the configured `results_root`, not inside `.lab/changes/`.
 - Figures and plots belong under the configured `figures_root`, not inside `.lab/changes/`.
 - Deliverables belong under the configured `deliverables_root`, not inside `.lab/context/`.
-- When `workflow_language` and `paper_language` differ, the deliverable set may include both the canonical manuscript and a persisted workflow-language reading deliverable. Review layers remain separate project-owned artifacts and must not substitute for readable deliverables.
+- When `workflow_language` and `paper_language` differ, ordinary manuscript `.tex` drafts still belong in `workflow_language` until finalization explicitly converts the canonical manuscript to `paper_language`. The deliverable set may then include both the canonical manuscript and a persisted workflow-language reading deliverable. Review layers remain separate project-owned artifacts and must not substitute for readable deliverables.
 - Change-local `data/` directories may hold lightweight manifests or batch specs, but not the canonical dataset copy.
 - `.lab/context/state.md` is a derived durable research snapshot; `.lab/context/workflow-state.md` holds live workflow state.
 - `.lab/context/summary.md` is the durable project summary; `.lab/context/session-brief.md` is the next-session startup brief.

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

@@ -61,6 +61,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Produce 2-3 candidate approaches with trade-offs before recommending one.
 - Critique the idea before converging on it.
 - Include a minimum viable experiment before approval.
+- Keep the experiment discussion rough at this stage: say who or what is evaluated, the likely validation route, and the main validity risk, but leave sample size, recruitment, condition count, and full protocol design to `/lab:spec`.
 - Keep an explicit approval gate before `/lab:spec`.
 - Write idea artifacts with the template in `.lab/.managed/templates/idea.md`.
 - Keep `.lab/writing/idea-source-log.md` as the source-backed search manifest for the two literature sweeps.
@@ -124,6 +125,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Read `.lab/context/mission.md`, `.lab/context/decisions.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, and `.lab/context/data-decisions.md` before drafting the change.
 - Use `.lab/changes/<change-id>/` as the canonical lab change directory.
 - Convert the approved idea into lab change artifacts using `.lab/.managed/templates/proposal.md`, `.lab/.managed/templates/design.md`, `.lab/.managed/templates/spec.md`, and `.lab/.managed/templates/tasks.md`.
+- When the approved idea involves human-subject evaluation, use this stage to freeze the human-subject experiment design: participant recruitment, sample-size rationale, condition design, assignment, measurement, and ethics or debrief details.
 - Update `.lab/context/decisions.md` after freezing the spec, then refresh derived views.
 - Do not skip task definition.
 
@@ -191,6 +193,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Read `.lab/context/mission.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/data-decisions.md` before drafting.
 - Write one paper section or one explicit subproblem per round.
 - Ordinary manuscript drafting rounds should follow `workflow_language`.
+- In those ordinary rounds, the manuscript is still LaTeX, so the initial `.tex` section drafts must stay in `workflow_language` rather than jumping straight to `paper_language`.
 - Treat the readable workflow-language paper as a real persisted deliverable, not as a review layer.
 - If `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then the first final-draft or export round must ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`.
 - When the languages differ, do not rewrite final manuscript sections in `paper_language` before that question has been answered; ask first, persist the choice, then edit the final manuscript in the chosen language.

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

@@ -141,6 +141,7 @@
   - if the current write target is a final manuscript export, `paper_template_decision` is `default-scaffold`, and `paper_template_final_reminder_acknowledged` is `false`, ask one final reminder question before finalizing
   - if the user confirms staying on the default scaffold at that final reminder, persist `paper_template_final_reminder_acknowledged: true`
 - During ordinary `write` drafting rounds, draft manuscript text in `workflow_language`.
+- During ordinary `write` drafting rounds, the manuscript output is still LaTeX, so ordinary manuscript `.tex` sections should stay in `workflow_language`, not the `paper_language` version yet.
 - If the current write target is a final manuscript export, `workflow_language` and `paper_language` differ, and `paper_language_finalization_decision` is `unconfirmed`, ask one explicit question before finalizing: keep the manuscript in `workflow_language`, or convert the final manuscript to `paper_language`
 - If the user chooses to keep the draft language, persist `paper_language_finalization_decision: keep-workflow-language`
 - If the user chooses to convert, persist `paper_language_finalization_decision: convert-to-paper-language`

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

@@ -138,6 +138,8 @@
 - Explain what current methods do, why they fall short, and roughly how the proposed idea would work in plain language.
 - Explain what problem the idea actually solves before describing tentative contributions.
 - Keep the evaluation sketch high-level: who or what is evaluated, what proxy or simulator is used if any, what outcome matters, and what the main validity risk is. Leave full protocol design to later stages.
+- Use the idea stage to say roughly how the idea would be validated and what the minimum viable experiment looks like, but do not freeze sample size, recruitment plan, condition count, questionnaire design, or randomization protocol here.
+- Human-subject experiment design belongs to `/lab:spec`, where recruitment, assignment, measurement, and ethics details can be made explicit.
 - Keep contributions tentative and high-level. The goal here is to explain what the paper might contribute, not to freeze paper-facing wording.
 - The three meaningful points should each fit in one direct sentence.
 - The final output must guide the user. Tell them what decision matters now, what information would sharpen the idea, and which `/lab` stage should come next.

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

@@ -37,6 +37,7 @@
 - Convert the chosen idea into explicit requirements.
 - Carry the approved dataset package, source choices, and benchmark mix into the change.
 - Preserve evaluation boundaries from the idea stage.
+- If the approved idea includes human-subject evaluation, convert the rough evaluation sketch into an explicit human-subject experiment design instead of leaving recruitment or protocol details implicit.
 - Translate risks into concrete tasks when possible.
 - Make task granularity small enough that `/lab:run` and `/lab:iterate` can execute predictably.
 - Use one lab-native change directory per approved idea instead of scattering spec artifacts.
@@ -56,6 +57,13 @@
 - split verification
 - preprocessing
 - benchmark protocol
+- human-subject experiment design
+- participant recruitment
+- sample-size rationale
+- condition design
+- assignment or randomization protocol
+- measurement or survey plan
+- ethics, consent, and debrief plan when applicable
 - artifact creation
 - validation run
 - evaluation normalization

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

@@ -62,6 +62,7 @@ Run these on every round:
 - Change one section or one clearly bounded subsection per round.
 - LaTeX is the required manuscript output format.
 - Ordinary manuscript drafting rounds should follow `workflow_language`.
+- During ordinary rounds, ordinary `.tex` section drafts must stay in `workflow_language`; do not treat `paper_language` as the default draft language.
 - Treat the workflow-language manuscript as a real deliverable layer, not just an internal review note.
 - If the user asks to read the paper in `workflow_language`, materialize or refresh a readable workflow-language deliverable under `<deliverables_root>/paper/workflow-language/sections/<section>.md` instead of pointing to a review layer.
 - The workflow-language deliverable should mirror the current manuscript logic in reader-facing prose and must not contain review-only scaffolding such as paragraph outlines, self-check blocks, or claim-evidence maps.

package/package.json

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