superlab 0.1.33 → 0.1.34

package/lib/i18n.cjs

@@ -403,6 +403,9 @@ const ZH_SKILL_FILES = {
 ## Evidence Discipline
 
 - 明确区分来源事实与生成假设。
+- 显式调用 \`/lab:idea\` 时，默认就是一次完整重跑；即使用户说“根据现有 idea 重组一下”，也不能自动跳过两轮文献检索。
+- 只有当用户明确要求“只重写或重组现有 idea 文档，不重新检索”时，才允许进入 rewrite-only 模式。
+- rewrite-only 模式只能改善结构和可读性，不能改变推荐结论、paper fit 判断、收敛状态或 canonical context；并且必须明确说明这一轮仍未收敛，因为两轮文献检索没有重跑。
 - 在谈 novelty 前先做文献范围梳理。默认目标是约 20 篇来源，覆盖最接近前作、近期强相关论文、benchmark 或评测论文、survey 或 taxonomy，以及必要的相邻领域工作。
 - 必须维护单独的 idea 来源清单，把两轮检索真正使用过的查询、来源分桶和最终来源数记下来。
 - 第一轮脑暴只负责打开空间，不负责直接下 novelty 结论。
@@ -461,6 +464,7 @@ const ZH_SKILL_FILES = {
 - 第一轮脑暴先开方向，不要急着写成最终答案。
 - 第一轮文献检索后再收敛方向，不要跳过中间筛选。
 - 第二轮文献检索前，不要把方向说成已经有 paper fit。
+- 只有用户明确要求 rewrite-only 时，才允许只改已有 idea 文档的结构；否则显式 \`/lab:idea\` 请求一律按完整 stage 重跑。
 - 现有方法对照必须显式写出，不能只说“更创新”。
 - 不要只说“比现有方法更好”；要说清楚现有方法在做什么、为什么不够、我们的方向大致怎么做。
 - 不要在没有文献范围包和最接近前作对照的情况下直接下 novelty 判断。
@@ -468,6 +472,7 @@ const ZH_SKILL_FILES = {
 - 不要把 idea 工件本身当成唯一证据记录；两轮文献检索的查询、来源分桶和最终来源数必须同步记到 \`.lab/writing/idea-source-log.md\`。
 - 三个 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\`。
 `,
   [path.join(".codex", "skills", "lab", "references", "workflow.md")]:
 `# /lab 工作流参考

package/lib/lab_idea_contract.json

@@ -1,8 +1,8 @@
 {
   "stage_prompt": {
-    "codex_en": "This command runs the `/lab:idea` stage. Use `.codex/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.",
-    "claude_en": "This command runs the `idea` stage of the lab workflow. Use `.claude/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.",
-    "codex_zh": "本命令运行 `/lab:idea` 阶段。把 `.codex/skills/lab/stages/idea.md` 当成两轮脑暴、两轮文献检索、最接近前作对照、source-backed proposal memo、评测草图、暂定贡献、用户引导、最小可行实验、收敛状态和 approval gate 的单一来源。先做第一轮脑暴，产出 3-4 个候选方向。每个候选方向都要说明：它是什么、为什么值得研究、大致怎么做、解决了什么问题、主要风险是什么。再做第一轮文献检索，为每个方向补最接近前作；然后用第二轮脑暴把范围收敛到 1-2 个幸存方向，并写清每个幸存方向为什么保留、每个被淘汰方向为什么淘汰、为什么当前 narrowed recommendation 更强；最后做第二轮文献检索，补齐最终来源包，再输出协作者可读的推荐结论。任何 final recommendation、paper fit 判断或 mission 写回之前，都必须先 materialize or update `.lab/writing/idea.md` 和 `.lab/writing/idea-source-log.md`。不要以纯聊天脑暴收尾；如果当前还没收敛，就明确写出还缺什么，并停在未收敛状态。最终 idea memo 必须讲清真实场景、解决了什么问题、现有方法为什么不够、准备怎么做、大致怎么评、暂定贡献是什么、哪些部分已经 source-backed、哪些还只是 hypothesis，以及用户下一步该决定什么。它还必须包含一个用户可见的文献摘要，明确写出：找到的最接近前作、找到的近期强相关论文、以及现有工作仍未解决什么。`.lab/writing/idea-source-log.md` 必须和两轮检索实际用到的查询、来源分桶和最终来源数保持一致。文献来源包默认目标约 20 篇；如果领域确实很窄，必须显式解释为什么合理地低于这个目标。只有在 `.lab/.managed/scripts/validate_idea_artifact.py` 通过之后，才可以把最终推荐当成已收敛结论输出。",
-    "claude_zh": "本命令运行 lab workflow 的 `idea` 阶段。把 `.claude/skills/lab/stages/idea.md` 当成两轮脑暴、两轮文献检索、最接近前作对照、source-backed proposal memo、评测草图、暂定贡献、用户引导、最小可行实验、收敛状态和 approval gate 的单一来源。先做第一轮脑暴，产出 3-4 个候选方向。每个候选方向都要说明：它是什么、为什么值得研究、大致怎么做、解决了什么问题、主要风险是什么。再做第一轮文献检索，为每个方向补最接近前作；然后用第二轮脑暴把范围收敛到 1-2 个幸存方向，并写清每个幸存方向为什么保留、每个被淘汰方向为什么淘汰、为什么当前 narrowed recommendation 更强；最后做第二轮文献检索，补齐最终来源包，再输出协作者可读的推荐结论。任何 final recommendation、paper fit 判断或 mission 写回之前，都必须先 materialize or update `.lab/writing/idea.md` 和 `.lab/writing/idea-source-log.md`。不要以纯聊天脑暴收尾；如果当前还没收敛，就明确写出还缺什么，并停在未收敛状态。最终 idea memo 必须讲清真实场景、解决了什么问题、现有方法为什么不够、准备怎么做、大致怎么评、暂定贡献是什么、哪些部分已经 source-backed、哪些还只是 hypothesis，以及用户下一步该决定什么。它还必须包含一个用户可见的文献摘要，明确写出：找到的最接近前作、找到的近期强相关论文、以及现有工作仍未解决什么。`.lab/writing/idea-source-log.md` 必须和两轮检索实际用到的查询、来源分桶和最终来源数保持一致。文献来源包默认目标约 20 篇；如果领域确实很窄，必须显式解释为什么合理地低于这个目标。只有在 `.lab/.managed/scripts/validate_idea_artifact.py` 通过之后，才可以把最终推荐当成已收敛结论输出。"
+    "codex_en": "This command runs the `/lab:idea` stage. Use `.codex/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo. Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching. Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context; it must say that the stage remains unconverged because the literature sweeps were not rerun. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.",
+    "claude_en": "This command runs the `idea` stage of the lab workflow. Use `.claude/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo. Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching. Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context; it must say that the stage remains unconverged because the literature sweeps were not rerun. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.",
+    "codex_zh": "本命令运行 `/lab:idea` 阶段。把 `.codex/skills/lab/stages/idea.md` 当成两轮脑暴、两轮文献检索、最接近前作对照、source-backed proposal memo、评测草图、暂定贡献、用户引导、最小可行实验、收敛状态和 approval gate 的单一来源。显式调用 `/lab:idea` 时，默认就是一次完整重跑，即使用户说的是“根据现有 idea 重组一下”也一样。只有当用户明确要求“只重写或重组现有 idea 文档，不重新检索”时，才允许进入 rewrite-only 模式。rewrite-only 模式只能改结构和可读性，不能改变推荐结论、paper fit 判断、收敛状态或 canonical context，并且必须明确说明：由于没有重跑文献检索，这一轮仍然处于未收敛状态。先做第一轮脑暴，产出 3-4 个候选方向。每个候选方向都要说明：它是什么、为什么值得研究、大致怎么做、解决了什么问题、主要风险是什么。再做第一轮文献检索，为每个方向补最接近前作；然后用第二轮脑暴把范围收敛到 1-2 个幸存方向，并写清每个幸存方向为什么保留、每个被淘汰方向为什么淘汰、为什么当前 narrowed recommendation 更强；最后做第二轮文献检索，补齐最终来源包，再输出协作者可读的推荐结论。任何 final recommendation、paper fit 判断或 mission 写回之前，都必须先 materialize or update `.lab/writing/idea.md` 和 `.lab/writing/idea-source-log.md`。不要以纯聊天脑暴收尾；如果当前还没收敛，就明确写出还缺什么，并停在未收敛状态。最终 idea memo 必须讲清真实场景、解决了什么问题、现有方法为什么不够、准备怎么做、大致怎么评、暂定贡献是什么、哪些部分已经 source-backed、哪些还只是 hypothesis，以及用户下一步该决定什么。它还必须包含一个用户可见的文献摘要，明确写出：找到的最接近前作、找到的近期强相关论文、以及现有工作仍未解决什么。`.lab/writing/idea-source-log.md` 必须和两轮检索实际用到的查询、来源分桶和最终来源数保持一致。文献来源包默认目标约 20 篇；如果领域确实很窄，必须显式解释为什么合理地低于这个目标。只有在 `.lab/.managed/scripts/validate_idea_artifact.py` 通过之后，才可以把最终推荐当成已收敛结论输出。",
+    "claude_zh": "本命令运行 lab workflow 的 `idea` 阶段。把 `.claude/skills/lab/stages/idea.md` 当成两轮脑暴、两轮文献检索、最接近前作对照、source-backed proposal memo、评测草图、暂定贡献、用户引导、最小可行实验、收敛状态和 approval gate 的单一来源。显式调用 `/lab:idea` 时，默认就是一次完整重跑，即使用户说的是“根据现有 idea 重组一下”也一样。只有当用户明确要求“只重写或重组现有 idea 文档，不重新检索”时，才允许进入 rewrite-only 模式。rewrite-only 模式只能改结构和可读性，不能改变推荐结论、paper fit 判断、收敛状态或 canonical context，并且必须明确说明：由于没有重跑文献检索，这一轮仍然处于未收敛状态。先做第一轮脑暴，产出 3-4 个候选方向。每个候选方向都要说明：它是什么、为什么值得研究、大致怎么做、解决了什么问题、主要风险是什么。再做第一轮文献检索，为每个方向补最接近前作；然后用第二轮脑暴把范围收敛到 1-2 个幸存方向，并写清每个幸存方向为什么保留、每个被淘汰方向为什么淘汰、为什么当前 narrowed recommendation 更强；最后做第二轮文献检索，补齐最终来源包，再输出协作者可读的推荐结论。任何 final recommendation、paper fit 判断或 mission 写回之前，都必须先 materialize or update `.lab/writing/idea.md` 和 `.lab/writing/idea-source-log.md`。不要以纯聊天脑暴收尾；如果当前还没收敛，就明确写出还缺什么，并停在未收敛状态。最终 idea memo 必须讲清真实场景、解决了什么问题、现有方法为什么不够、准备怎么做、大致怎么评、暂定贡献是什么、哪些部分已经 source-backed、哪些还只是 hypothesis，以及用户下一步该决定什么。它还必须包含一个用户可见的文献摘要，明确写出：找到的最接近前作、找到的近期强相关论文、以及现有工作仍未解决什么。`.lab/writing/idea-source-log.md` 必须和两轮检索实际用到的查询、来源分桶和最终来源数保持一致。文献来源包默认目标约 20 篇；如果领域确实很窄，必须显式解释为什么合理地低于这个目标。只有在 `.lab/.managed/scripts/validate_idea_artifact.py` 通过之后，才可以把最终推荐当成已收敛结论输出。"
   }
 }

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

@@ -7,4 +7,4 @@ argument-hint: idea or research problem
 Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
 
 Execute the requested `/lab-idea` 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 `idea` stage of the lab workflow. Use `.claude/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.
+This command runs the `idea` stage of the lab workflow. Use `.claude/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo. Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching. Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context; it must say that the stage remains unconverged because the literature sweeps were not rerun. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.

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

@@ -6,4 +6,4 @@ argument-hint: idea or research problem
 Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:idea` 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:idea` stage. Use `.codex/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.
+This command runs the `/lab:idea` stage. Use `.codex/skills/lab/stages/idea.md` as the single source of truth for the two brainstorm passes, two literature sweeps, closest-prior comparison, source-backed proposal memo, evaluation sketch, tentative contributions, user guidance, minimum viable experiment, convergence status, and approval gate. An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo. Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching. Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context; it must say that the stage remains unconverged because the literature sweeps were not rerun. Start with brainstorm pass 1 over 3-4 candidate directions. For each candidate direction, explain what it is, why it matters, roughly how it would work, what problem it solves, and its main risk. Run literature sweep 1 with real closest-prior references for each direction, narrow the field with brainstorm pass 2 to 1-2 surviving directions, explain why each survivor remains, why each rejected direction was dropped, and why the narrowed recommendation is stronger now, then run literature sweep 2 to build the final source bundle before producing a collaborator-readable recommendation. Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before any final recommendation, paper-fit judgment, or mission writeback. Do not end the stage with a chat-only brainstorm; if the work is still unconverged, say so explicitly, list what is still missing, and stop there. The final idea memo must explain the real-world scenario, the problem solved, why current methods fall short, roughly how the idea would work, how it would be evaluated, what the tentative contributions are, what is already source-backed, what is still hypothesis-only, and what the user should decide next. It must also include a user-visible literature summary naming the closest prior found, the recent strong papers found, and what existing work still does not solve. Keep `.lab/writing/idea-source-log.md` synchronized with the actual search queries, bucketed sources, and final source count used in both sweeps. The literature bundle should default to about 20 sources unless the field is genuinely narrow and that smaller bundle is explicitly justified. Only after `.lab/.managed/scripts/validate_idea_artifact.py` passes may the stage present a final recommendation as converged.

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

@@ -45,6 +45,9 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Include a user-visible literature summary that names the closest prior found, the recent strong papers found, and what existing work still does not solve before giving the final recommendation.
 - Build a literature-scoping bundle before claiming novelty. The default target is 20 relevant sources unless the field is genuinely too narrow and that exception is written down.
 - Materialize or update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before giving any final recommendation, paper-fit judgment, or mission writeback.
+- An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo.
+- Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching.
+- Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context.
 - Read `.lab/context/mission.md` and `.lab/context/open-questions.md` before drafting.
 - Read `.lab/config/workflow.json` before drafting and follow its `workflow_language` for idea artifacts.
 - Ask one clarifying question at a time when critical ambiguity remains.

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

@@ -42,6 +42,9 @@
 - Mark sourced facts clearly.
 - Mark generated hypotheses clearly.
 - Do not merge them into one undifferentiated summary.
+- An explicit `/lab:idea` request defaults to a full-stage rerun, even if the user asks to reorganize or rewrite an existing idea memo.
+- Only switch to rewrite-only mode when the user explicitly asks to only reorganize or rewrite the existing idea artifact without new searching.
+- Rewrite-only mode may improve structure or readability, but it must not change the recommendation, paper-fit judgment, convergence status, or canonical context. It must also say that the stage remains unconverged and that the literature sweeps were not rerun.
 - Ask one clarifying question at a time when a missing assumption would materially change the proposal.
 - Build a source bundle before claiming novelty. The default target is 20 relevant sources split across closest prior work, recent strong papers, benchmark or evaluation papers, surveys or taxonomies, and adjacent-field work when useful.
 - Treat closest prior work, recent strong papers, benchmark or evaluation papers, and survey or taxonomy papers as mandatory coverage buckets. Do not leave those buckets empty in the final source bundle.
@@ -130,6 +133,7 @@
 - Do not treat the idea artifact itself as the only evidence record; keep `.lab/writing/idea-source-log.md` synchronized with the actual searches and source buckets used in both literature sweeps.
 - Do not leave the working result only in chat. Update `.lab/writing/idea.md` and `.lab/writing/idea-source-log.md` before returning a stage conclusion.
 - Do not present a final recommendation, paper fit, or next-stage approval unless the working idea artifact is validator-clean and its convergence status says the stage is ready for that recommendation.
+- Do not update `.lab/context/mission.md`, `.lab/context/decisions.md`, or `.lab/context/open-questions.md` from rewrite-only mode.
 - 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.

package/package.json

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