superlab 0.1.43 → 0.1.45

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

@@ -0,0 +1,10 @@
+---
+name: "lab-iterate"
+description: Run bounded Ralph-style experiment iterations with fixed success criteria
+argument-hint: iteration mission
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-iterate` 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 `iterate` stage of the lab workflow. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,10 @@
+---
+name: "lab-report"
+description: Produce the final report from validated iteration artifacts
+argument-hint: report context
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-report` 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 `report` stage of the lab workflow. It must produce a user-facing final report plus the managed `main-tables.md` artifact, explicitly carry the approved primary and secondary metrics forward, explain the selected metrics in plain language, say which metrics are only health or support metrics, and explain what each main table proves or does not prove.

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

@@ -0,0 +1,10 @@
+---
+name: "lab-review"
+description: Review a research plan or result in reviewer mode
+argument-hint: artifact or result to review
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-review` 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 `review` stage of the lab workflow. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,10 @@
+---
+name: "lab-run"
+description: Execute the smallest meaningful experiment and normalize its output
+argument-hint: run context
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-run` 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 `run` stage of the lab workflow. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,10 @@
+---
+name: "lab-spec"
+description: Convert an approved idea into a lab change directory
+argument-hint: approved idea context
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-spec` 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 `spec` stage of the lab workflow. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,10 @@
+---
+name: "lab-write"
+description: Turn validated research artifacts into paper sections with small evidence-bound revisions
+argument-hint: section or writing target
+---
+
+Use the installed `lab` skill at `.claude/skills/lab/SKILL.md`.
+
+Execute the requested `/lab-write` command against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
+This command runs the `write` stage of the lab workflow. Use `.claude/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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

@@ -0,0 +1,14 @@
+---
+description: Orchestrate approved lab execution stages inside a bounded autonomous loop
+argument-hint: autonomous campaign target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:auto` 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:auto` stage. It must read `.lab/context/eval-protocol.md`, `.lab/context/auto-mode.md`, `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`, enforce the declared terminal goal schema, make the primary gate, secondary guard, promotion condition, stop reason, and escalation reason explicit, orchestrate approved run, iterate, review, and report stages inside that contract, poll long-running work until completion or stop conditions, and write live owner state plus progress and the final outcome back into `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`.
+The first visible block must be `Auto preflight`. That first visible block must list the files read and echo `Autonomy level`, `Approval status`, `Allowed stages`, `Terminal goal`, `Primary gate`, and `Secondary guard` before any execution summary or action plan.
+If the preflight block cannot be completed because any required field is missing, stale, or inconsistent, stop before execution and say exactly which field blocked arming the loop.
+When the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a literal identifier must stay unchanged.
+Treat `Layer 3`, `Phase 1`, or `Table 2` as paper-scope targets. Treat `Autonomy level L3` as the execution permission level.
+Do not replace the real long-running experiment command with a short watcher such as `sleep 30`, `pgrep`, or a one-shot `metrics.json` probe. While the real experiment process is still alive, emit only a progress update and keep waiting.

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

@@ -0,0 +1,9 @@
+---
+description: Select datasets and benchmark packages with explicit source, year, and paper-usage audit
+argument-hint: dataset or benchmark selection target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:data` 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:data` stage. It must turn the approved idea into an approved dataset package with dataset year, papers that used each dataset, source audit, download plan, explicit benchmark-role rationale for classic-public, recent-strong-public, and claim-specific benchmarks, and explicit comparison rationale for canonical baselines, strong historical baselines, recent strong public methods, and closest prior work.

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

@@ -0,0 +1,9 @@
+---
+description: Lock paper-facing naming, title, and contribution framing before drafting
+argument-hint: naming, title, or contribution framing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:framing` 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:framing` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Research and refine a paper or experiment idea before specification
+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. 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. In the final user-facing summary, say what current methods do, why they still fall short, how the proposed direction differs, the rough approach, the main risk, and where to read the full idea artifact and source log. 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/iterate.md

@@ -0,0 +1,9 @@
+---
+description: Run bounded Ralph-style experiment iterations with fixed success criteria
+argument-hint: iteration mission
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:iterate` 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:iterate` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Produce the final report from validated iteration artifacts
+argument-hint: report context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:report` 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:report` stage. It must produce a user-facing final report plus the managed `main-tables.md` artifact, explicitly carry the approved primary and secondary metrics forward, explain the selected metrics in plain language, say which metrics are only health or support metrics, and explain what each main table proves or does not prove.

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

@@ -0,0 +1,9 @@
+---
+description: Review a research plan or result in reviewer mode
+argument-hint: artifact or result to review
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:review` 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:review` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Execute the smallest meaningful experiment and normalize its output
+argument-hint: run context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:run` 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:run` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Convert an approved idea into a lab change directory
+argument-hint: approved idea context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:spec` 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:spec` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Turn validated research artifacts into paper sections with small evidence-bound revisions
+argument-hint: section or writing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

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

@@ -7,7 +7,22 @@ argument-hint: workflow question or stage choice
 
 `/lab` is a strict research workflow command family. Use the same repository artifacts and stage boundaries every time.
 
-## Subcommands
+## Accepted Stage Spellings
+
+Treat all of these as equivalent stage requests:
+
+- `/lab:idea ...`, `/lab: idea ...`, `/lab idea ...`, `/lab-idea`, `/lab：idea ...`
+- `/lab:data ...`, `/lab: data ...`, `/lab data ...`, `/lab-data`, `/lab：data ...`
+- `/lab:auto ...`, `/lab: auto ...`, `/lab auto ...`, `/lab-auto`, `/lab：auto ...`
+- `/lab:framing ...`, `/lab: framing ...`, `/lab framing ...`, `/lab-framing`, `/lab：framing ...`
+- `/lab:spec ...`, `/lab: spec ...`, `/lab spec ...`, `/lab-spec`, `/lab：spec ...`
+- `/lab:run ...`, `/lab: run ...`, `/lab run ...`, `/lab-run`, `/lab：run ...`
+- `/lab:iterate ...`, `/lab: iterate ...`, `/lab iterate ...`, `/lab-iterate`, `/lab：iterate ...`
+- `/lab:review ...`, `/lab: review ...`, `/lab review ...`, `/lab-review`, `/lab：review ...`
+- `/lab:report ...`, `/lab: report ...`, `/lab report ...`, `/lab-report`, `/lab：report ...`
+- `/lab:write ...`, `/lab: write ...`, `/lab write ...`, `/lab-write`, `/lab：write ...`
+
+## Stage Aliases
 
 - `/lab:idea`
   Research the idea through two brainstorm passes and two literature sweeps, define the problem and failure case, compare against closest prior work, then end with a source-backed recommendation and an explicit approval gate before any implementation.
@@ -44,7 +59,8 @@ argument-hint: workflow question or stage choice
 
 - Always use `skills/lab/SKILL.md` as the workflow contract.
 - Use `skills/lab/references/recipes.md` as the quick path for common stage chains; do not invent new slash commands or aliases from it.
-- When the user explicitly invokes `/lab:<stage>`, execute that stage now against the provided argument instead of only recommending another `/lab` stage.
+- When the user explicitly invokes a stage through `/lab:<stage>`, `/lab: <stage>`, `/lab <stage>`, `/lab-<stage>`, or `/lab：<stage>`, execute that stage now against the provided argument instead of only recommending another `/lab` stage.
+- If the input looks like a stage request but does not match one of the accepted spellings, stop and ask the user to restate it with an exact supported stage name instead of guessing.
 - Start by giving the user a concise stage summary. Materialize managed artifacts immediately when the stage contract requires them, 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>/`.

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

@@ -0,0 +1,14 @@
+---
+description: Orchestrate approved lab execution stages inside a bounded autonomous loop
+argument-hint: autonomous campaign target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:auto` 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:auto` stage. It must read `.lab/context/eval-protocol.md`, `.lab/context/auto-mode.md`, `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`, enforce the declared terminal goal schema, make the primary gate, secondary guard, promotion condition, stop reason, and escalation reason explicit, orchestrate approved run, iterate, review, and report stages inside that contract, poll long-running work until completion or stop conditions, and write live owner state plus progress and the final outcome back into `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`.
+The first visible block must be `Auto preflight`. That first visible block must list the files read and echo `Autonomy level`, `Approval status`, `Allowed stages`, `Terminal goal`, `Primary gate`, and `Secondary guard` before any execution summary or action plan.
+If the preflight block cannot be completed because any required field is missing, stale, or inconsistent, stop before execution and say exactly which field blocked arming the loop.
+When the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a literal identifier must stay unchanged.
+Treat `Layer 3`, `Phase 1`, or `Table 2` as paper-scope targets. Treat `Autonomy level L3` as the execution permission level.
+Do not replace the real long-running experiment command with a short watcher such as `sleep 30`, `pgrep`, or a one-shot `metrics.json` probe. While the real experiment process is still alive, emit only a progress update and keep waiting.

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

@@ -0,0 +1,9 @@
+---
+description: Select datasets and benchmark packages with explicit source, year, and paper-usage audit
+argument-hint: dataset or benchmark selection target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:data` 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:data` stage. It must turn the approved idea into an approved dataset package with dataset year, papers that used each dataset, source audit, download plan, explicit benchmark-role rationale for classic-public, recent-strong-public, and claim-specific benchmarks, and explicit comparison rationale for canonical baselines, strong historical baselines, recent strong public methods, and closest prior work.

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

@@ -0,0 +1,9 @@
+---
+description: Lock paper-facing naming, title, and contribution framing before drafting
+argument-hint: naming, title, or contribution framing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:framing` 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:framing` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Research and refine a paper or experiment idea before specification
+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. 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. In the final user-facing summary, say what current methods do, why they still fall short, how the proposed direction differs, the rough approach, the main risk, and where to read the full idea artifact and source log. 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:iterate.md

@@ -0,0 +1,9 @@
+---
+description: Run bounded Ralph-style experiment iterations with fixed success criteria
+argument-hint: iteration mission
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:iterate` 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:iterate` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Produce the final report from validated iteration artifacts
+argument-hint: report context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:report` 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:report` stage. It must produce a user-facing final report plus the managed `main-tables.md` artifact, explicitly carry the approved primary and secondary metrics forward, explain the selected metrics in plain language, say which metrics are only health or support metrics, and explain what each main table proves or does not prove.

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

@@ -0,0 +1,9 @@
+---
+description: Review a research plan or result in reviewer mode
+argument-hint: artifact or result to review
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:review` 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:review` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Execute the smallest meaningful experiment and normalize its output
+argument-hint: run context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:run` 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:run` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Convert an approved idea into a lab change directory
+argument-hint: approved idea context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:spec` 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:spec` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

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

@@ -0,0 +1,9 @@
+---
+description: Turn validated research artifacts into paper sections with small evidence-bound revisions
+argument-hint: section or writing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package-assets/codex/prompts/lab/357/274/232auto.md

@@ -0,0 +1,14 @@
+---
+description: Orchestrate approved lab execution stages inside a bounded autonomous loop
+argument-hint: autonomous campaign target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:auto` 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:auto` stage. It must read `.lab/context/eval-protocol.md`, `.lab/context/auto-mode.md`, `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`, enforce the declared terminal goal schema, make the primary gate, secondary guard, promotion condition, stop reason, and escalation reason explicit, orchestrate approved run, iterate, review, and report stages inside that contract, poll long-running work until completion or stop conditions, and write live owner state plus progress and the final outcome back into `.lab/context/auto-status.md`, `.lab/context/auto-ledger.md`, and `.lab/context/auto-outcome.md`.
+The first visible block must be `Auto preflight`. That first visible block must list the files read and echo `Autonomy level`, `Approval status`, `Allowed stages`, `Terminal goal`, `Primary gate`, and `Secondary guard` before any execution summary or action plan.
+If the preflight block cannot be completed because any required field is missing, stale, or inconsistent, stop before execution and say exactly which field blocked arming the loop.
+When the repository workflow language is Chinese, summaries, checklist items, task labels, and progress updates should be written in Chinese unless a literal identifier must stay unchanged.
+Treat `Layer 3`, `Phase 1`, or `Table 2` as paper-scope targets. Treat `Autonomy level L3` as the execution permission level.
+Do not replace the real long-running experiment command with a short watcher such as `sleep 30`, `pgrep`, or a one-shot `metrics.json` probe. While the real experiment process is still alive, emit only a progress update and keep waiting.

package/package-assets/codex/prompts/lab/357/274/232data.md

@@ -0,0 +1,9 @@
+---
+description: Select datasets and benchmark packages with explicit source, year, and paper-usage audit
+argument-hint: dataset or benchmark selection target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:data` 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:data` stage. It must turn the approved idea into an approved dataset package with dataset year, papers that used each dataset, source audit, download plan, explicit benchmark-role rationale for classic-public, recent-strong-public, and claim-specific benchmarks, and explicit comparison rationale for canonical baselines, strong historical baselines, recent strong public methods, and closest prior work.

package/package-assets/codex/prompts/lab/357/274/232framing.md

@@ -0,0 +1,9 @@
+---
+description: Lock paper-facing naming, title, and contribution framing before drafting
+argument-hint: naming, title, or contribution framing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:framing` 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:framing` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

package/package-assets/codex/prompts/lab/357/274/232idea.md

@@ -0,0 +1,9 @@
+---
+description: Research and refine a paper or experiment idea before specification
+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. 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. In the final user-facing summary, say what current methods do, why they still fall short, how the proposed direction differs, the rough approach, the main risk, and where to read the full idea artifact and source log. 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/357/274/232iterate.md

@@ -0,0 +1,9 @@
+---
+description: Run bounded Ralph-style experiment iterations with fixed success criteria
+argument-hint: iteration mission
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:iterate` 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:iterate` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

package/package-assets/codex/prompts/lab/357/274/232report.md

@@ -0,0 +1,9 @@
+---
+description: Produce the final report from validated iteration artifacts
+argument-hint: report context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:report` 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:report` stage. It must produce a user-facing final report plus the managed `main-tables.md` artifact, explicitly carry the approved primary and secondary metrics forward, explain the selected metrics in plain language, say which metrics are only health or support metrics, and explain what each main table proves or does not prove.

package/package-assets/codex/prompts/lab/357/274/232review.md

@@ -0,0 +1,9 @@
+---
+description: Review a research plan or result in reviewer mode
+argument-hint: artifact or result to review
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:review` 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:review` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

package/package-assets/codex/prompts/lab/357/274/232run.md

@@ -0,0 +1,9 @@
+---
+description: Execute the smallest meaningful experiment and normalize its output
+argument-hint: run context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:run` 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:run` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

package/package-assets/codex/prompts/lab/357/274/232spec.md

@@ -0,0 +1,9 @@
+---
+description: Convert an approved idea into a lab change directory
+argument-hint: approved idea context
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:spec` 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:spec` stage. Follow the installed skill, stage guide, and the project assets under `.lab/`.

package/package-assets/codex/prompts/lab/357/274/232write.md

@@ -0,0 +1,9 @@
+---
+description: Turn validated research artifacts into paper sections with small evidence-bound revisions
+argument-hint: section or writing target
+---
+
+Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
+
+Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
+This command runs the `/lab:write` stage. Use `.codex/skills/lab/stages/write.md` as the single source of truth for template choice, paper-plan requirements, section references, validator gates, asset coverage, and final manuscript rules. Read the matching paper-writing reference and any bundled example-bank files for the requested section, revise only one section, and keep draft rounds warning-only while final-draft or export rounds must satisfy the write-stage acceptance gates. Draft ordinary manuscript rounds in `workflow_language`, and ordinary `.tex` section drafts must stay in `workflow_language` instead of treating `paper_language` as the default draft language. Treat a readable workflow-language deliverable as a real persisted artifact rather than a review layer. Maintain `.lab/writing/terminology-glossary.md` as the write-stage glossary for full forms, approved short forms, reader-facing explanations, and aliases. Apply the same academic readability standard in every language: when the round introduces or revises key terms, abbreviations, metrics, mechanism names, or system labels, use the full form first, define any short form at first mention, explain what the term is and why it matters here, keep one natural-language paper-facing name per concept, use natural-language full names in prose, and do not use labels containing `_` or `-` in reader-facing prose. Keep internal identifiers out of reader-facing prose unless they are mapped once for the reader and then moved back out of prose, and record the terminology-clarity self-check in the write iteration artifact. If the manuscript would start from the managed scaffold and no template decision is recorded yet, ask once whether to keep the default scaffold or attach a template directory first. If finalization reaches a round where `workflow_language` and `paper_language` differ, finish and preserve the workflow-language deliverable first, then ask once whether to keep the draft language or convert the canonical manuscript to `paper_language`, persist that answer, record both the language decision and the workflow-language deliverable path in the latest write iteration, and only then edit the final manuscript in the chosen language.

package/package.json

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