superlab 0.1.70 → 0.1.71

package/lib/i18n.cjs

@@ -887,6 +887,60 @@ const ZH_SKILL_FILES = {
 - [ ] 标准化并验证评估摘要。
 - [ ] 执行有边界的 iteration rounds。
 - [ ] 产出 final report。
+`,
+  [path.join(".lab", ".managed", "templates", "stage-report.md")]:
+`# 阶段报告
+
+## 规则预检
+
+- Rule source file:
+- Rule source revision:
+- Project version:
+- Resolved stage:
+- Resolved mode:
+- Resolved target:
+- Preflight stamp:
+- Override reason, if any:
+
+## 阶段身份
+
+- Stage:
+- Target:
+- Date:
+- Status:
+- Primary artifact:
+- Next owner:
+
+## 核心说明表
+
+| 问题 | 白话回答 |
+|---|---|
+| 这是什么阶段？ |  |
+| 背景是什么？ |  |
+| 为什么现在要做？ |  |
+| 这轮具体做了什么？ |  |
+| 怎么做的？ |  |
+| 结果好的地方是什么？ |  |
+| 结果坏的地方是什么？ |  |
+| 这验证了什么？ |  |
+| 还没有验证什么？ |  |
+| 是否需要改进？为什么？ |  |
+| 下一步怎么改？为什么这样改？ |  |
+| 关键证据在哪里？ |  |
+| 现在应该继续、停止、重做还是升级？ |  |
+
+## 证据与工件
+
+- 主工件：
+- 支撑工件：
+- 验证命令：
+- 已知缺口：
+
+## 下一步动作
+
+- 决策：continue / stop / revise / rerun / escalate / handoff
+- 具体下一步：
+- 为什么这样做：
 `,
   [path.join(".lab", ".managed", "templates", "iteration-report.md")]:
 `# 迭代报告
@@ -3020,6 +3074,41 @@ ZH_CONTENT[path.join(".claude", "skills", "lab", "stages", "auto.md")] =
 ZH_CONTENT[path.join(".claude", "skills", "lab", "stages", "report.md")] =
   ZH_CONTENT[path.join(".codex", "skills", "lab", "stages", "report.md")];
 
+const zhStageReportCloseout = `
+
+## 阶段报告收尾
+
+- 阶段进入最终交接、停止、失败或升级前，必须用 \`.lab/.managed/templates/stage-report.md\` 写或更新一个 \`.lab/stage-reports/<date>--<stage>--<target>.md\`。
+- \`核心说明表\` 必须用白话写清背景、为什么现在做、做了什么、怎么做、好结果、坏结果、验证了什么、还没验证什么、是否需要改进及原因、下一步怎么改及原因、关键证据，以及 continue/stop/revise/rerun/escalate/handoff 决策。
+- 阶段报告是收尾和交接工件，不是新命令，也不能替代 idea、iteration report、final report 或 write iteration 等阶段专属工件。
+- 收尾前运行 \`.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage <stage>\`，并在最终给用户的总结里给出阶段报告路径和校验结果。
+`;
+
+for (const platformRoot of [".codex", ".claude"]) {
+  for (const stage of ["idea", "data", "auto", "framing", "spec", "run", "iterate", "review", "report", "write"]) {
+    const key = path.join(platformRoot, "skills", "lab", "stages", `${stage}.md`);
+    if (ZH_CONTENT[key] && !ZH_CONTENT[key].includes("validate_stage_report.py")) {
+      ZH_CONTENT[key] += zhStageReportCloseout;
+    }
+  }
+}
+
+const zhStageReportGlobalRules =
+  "- 每个 `/lab:*` 阶段进入最终交接前，都必须在 `.lab/stage-reports/` 下写或更新一个白话阶段报告，并通过 `.lab/.managed/scripts/validate_stage_report.py` 校验。\n" +
+  "- 阶段报告必须包含核心说明表，讲清背景、为什么做、做了什么、怎么做、好坏结果、验证与未验证边界、是否需要改进及原因、下一步怎么改及原因、关键证据和继续/停止/修订/重跑/升级/交接决策。\n" +
+  "- 阶段报告只是统一收尾和交接层，不新增用户命令，也不替代各阶段自己的受管工件。\n";
+
+for (const platformRoot of [".codex", ".claude"]) {
+  const key = path.join(platformRoot, "skills", "lab", "SKILL.md");
+  if (ZH_CONTENT[key] && !ZH_CONTENT[key].includes("validate_stage_report.py")) {
+    ZH_CONTENT[key] = ZH_CONTENT[key].replace(
+      "- 项目里已安装的规则优先于模型记忆；如果记忆里的旧做法和 `.lab/.managed/rule-manifest.json` 记录的规则冲突，以项目里安装的规则为准。\n",
+      "- 项目里已安装的规则优先于模型记忆；如果记忆里的旧做法和 `.lab/.managed/rule-manifest.json` 记录的规则冲突，以项目里安装的规则为准。\n" +
+        zhStageReportGlobalRules
+    );
+  }
+}
+
 function getLocalizedContent(relativePath, lang) {
   if (lang !== "zh") {
     return null;

package/lib/install.cjs

@@ -674,6 +674,7 @@ function localizeInstalledAssets(targetDir, lang, { newlyCreatedProjectOwnedPath
     path.join(".lab", ".managed", "templates", "design.md"),
     path.join(".lab", ".managed", "templates", "spec.md"),
     path.join(".lab", ".managed", "templates", "tasks.md"),
+    path.join(".lab", ".managed", "templates", "stage-report.md"),
     path.join(".lab", ".managed", "templates", "iteration-report.md"),
     path.join(".lab", ".managed", "templates", "review-checklist.md"),
     path.join(".lab", ".managed", "templates", "final-report.md"),

package/package-assets/shared/lab/.managed/scripts/validate_stage_report.py

@@ -0,0 +1,301 @@
+#!/usr/bin/env python3
+import argparse
+import re
+import sys
+from pathlib import Path
+
+
+REQUIRED_SECTIONS = {
+    "Rule Preflight": [r"^##\s+Rule Preflight\s*$", r"^##\s+规则预检\s*$"],
+    "Stage Identity": [r"^##\s+Stage Identity\s*$", r"^##\s+阶段身份\s*$"],
+    "Core Explanation Table": [r"^##\s+Core Explanation Table\s*$", r"^##\s+核心说明表\s*$"],
+    "Evidence And Artifacts": [r"^##\s+Evidence And Artifacts\s*$", r"^##\s+证据与工件\s*$"],
+    "Next Action": [r"^##\s+Next Action\s*$", r"^##\s+下一步动作\s*$"],
+}
+
+REQUIRED_CORE_ROWS = {
+    "stage": ("这是什么阶段", "what stage is this", "stage"),
+    "background": ("背景是什么", "background"),
+    "why_now": ("为什么现在要做", "why now", "why this stage ran"),
+    "what_done": ("这轮具体做了什么", "what this stage did", "what did this stage do"),
+    "how_done": ("怎么做的", "how it was done", "how was it done"),
+    "worked": ("结果好的地方是什么", "what worked"),
+    "did_not_work": ("结果坏的地方是什么", "what did not work", "negative result"),
+    "verifies": ("这验证了什么", "what this verifies", "what was verified"),
+    "unverified": ("还没有验证什么", "what remains unverified", "not yet verified"),
+    "improve_why": ("是否需要改进", "need improvement", "what needs improvement"),
+    "how_improve": ("下一步怎么改", "how to improve"),
+    "evidence": ("关键证据在哪里", "key evidence", "evidence"),
+    "decision": ("现在应该继续", "continue, stop", "decision"),
+}
+
+PLACEHOLDER_VALUES = {
+    "",
+    "-",
+    "--",
+    "—",
+    "todo",
+    "tbd",
+    "n/a",
+    "na",
+    "none",
+    "待补",
+    "待定",
+    "无",
+}
+
+SHALLOW_VALUES = {
+    "done",
+    "ok",
+    "pass",
+    "passed",
+    "符合预期",
+    "已完成",
+    "继续优化",
+    "继续推进",
+    "没有问题",
+}
+
+INTERNAL_META_PATTERNS = [
+    r"用户说",
+    r"我来解释",
+    r"我会",
+    r"我已经",
+    r"你要求",
+    r"\bagent\b",
+    r"\bsubagent\b",
+    r"\bprompt\b",
+    r"提示词",
+    r"按.*技能",
+    r"service-style",
+    r"AI-assistant",
+]
+
+WHY_MARKERS = (
+    "because",
+    "so that",
+    "therefore",
+    "reason",
+    "why",
+    "因为",
+    "所以",
+    "因此",
+    "原因",
+    "以便",
+    "用于",
+    "避免",
+)
+
+
+def parse_args():
+    parser = argparse.ArgumentParser(description="Validate a plain-language lab stage report.")
+    parser.add_argument("--stage-report", required=True, help="Path to the stage report markdown file.")
+    parser.add_argument("--stage", default="", help="Expected lab stage name, such as run, auto, or write.")
+    return parser.parse_args()
+
+
+def normalize(text: str) -> str:
+    return re.sub(r"\s+", " ", text.strip().lower())
+
+
+def extract_section(text: str, patterns: list[str]) -> str:
+    for pattern in patterns:
+        match = re.search(pattern, text, flags=re.MULTILINE)
+        if not match:
+            continue
+        start = match.end()
+        next_heading = re.search(r"^##\s+", text[start:], flags=re.MULTILINE)
+        end = start + next_heading.start() if next_heading else len(text)
+        return text[start:end].strip()
+    return ""
+
+
+def find_missing_sections(text: str) -> list[str]:
+    missing = []
+    for name, patterns in REQUIRED_SECTIONS.items():
+        if not any(re.search(pattern, text, flags=re.MULTILINE) for pattern in patterns):
+            missing.append(name)
+    return missing
+
+
+def parse_core_table_rows(text: str) -> dict[str, str]:
+    section = extract_section(text, REQUIRED_SECTIONS["Core Explanation Table"])
+    rows = {}
+    for raw_line in section.splitlines():
+        line = raw_line.strip()
+        if not line.startswith("|") or line.count("|") < 3:
+            continue
+        cells = [cell.strip() for cell in line.strip("|").split("|")]
+        if len(cells) < 2:
+            continue
+        question = normalize(cells[0])
+        answer = cells[1].strip()
+        if question in {"question", "---", ""}:
+            continue
+        rows[question] = answer
+    return rows
+
+
+def find_row_value(rows: dict[str, str], markers: tuple[str, ...]) -> str | None:
+    normalized_markers = tuple(normalize(marker) for marker in markers)
+    for question, answer in rows.items():
+        if any(marker in question for marker in normalized_markers):
+            return answer
+    return None
+
+
+def is_blank_or_placeholder(value: str | None) -> bool:
+    if value is None:
+        return True
+    compact = normalize(value).strip(" .:;，。；：")
+    return compact in PLACEHOLDER_VALUES
+
+
+def has_marker_with_value(body: str, markers: tuple[str, ...]) -> bool:
+    for line in body.splitlines():
+        stripped = line.strip()
+        for marker in markers:
+            if marker not in stripped:
+                continue
+            value = stripped.split(marker, 1)[1].strip()
+            return not is_blank_or_placeholder(value)
+    return False
+
+
+def is_shallow(value: str | None) -> bool:
+    if value is None:
+        return True
+    compact = normalize(value).strip(" .:;，。；：")
+    return compact in SHALLOW_VALUES or len(compact) < 8
+
+
+def has_why(value: str) -> bool:
+    lowered = normalize(value)
+    return any(marker in lowered for marker in WHY_MARKERS)
+
+
+def validate_core_table(text: str) -> list[str]:
+    issues = []
+    rows = parse_core_table_rows(text)
+    missing_rows = []
+    for row_name, markers in REQUIRED_CORE_ROWS.items():
+        value = find_row_value(rows, markers)
+        if is_blank_or_placeholder(value):
+            missing_rows.append(row_name)
+    if missing_rows:
+        issues.append(f"Core Explanation Table is missing non-empty answers for: {', '.join(missing_rows)}")
+
+    for row_name in ("did_not_work", "verifies", "improve_why", "how_improve", "decision"):
+        value = find_row_value(rows, REQUIRED_CORE_ROWS[row_name])
+        if is_shallow(value):
+            issues.append(f"Core Explanation Table row '{row_name}' is too shallow")
+
+    for row_name in ("improve_why", "how_improve"):
+        value = find_row_value(rows, REQUIRED_CORE_ROWS[row_name])
+        if value and not has_why(value):
+            issues.append(f"Core Explanation Table row '{row_name}' must include a reason, not only an action")
+    return issues
+
+
+def validate_evidence_section(text: str) -> list[str]:
+    issues = []
+    body = extract_section(text, REQUIRED_SECTIONS["Evidence And Artifacts"])
+    marker_groups = (
+        ("Primary artifact:", "主工件："),
+        ("Supporting artifacts:", "支撑工件："),
+        ("Validation commands:", "验证命令："),
+        ("Known gaps:", "已知缺口："),
+    )
+    if not body:
+        return ["Evidence And Artifacts section is empty"]
+    for group in marker_groups:
+        if not any(marker in body for marker in group):
+            issues.append(f"Evidence And Artifacts is missing '{group[0]}'")
+            continue
+        if not has_marker_with_value(body, group):
+            issues.append(f"Evidence And Artifacts field '{group[0]}' must have a non-empty value")
+    return issues
+
+
+def validate_rule_preflight(text: str) -> list[str]:
+    body = extract_section(text, REQUIRED_SECTIONS["Rule Preflight"])
+    marker_groups = (
+        ("Rule source file:",),
+        ("Rule source revision:",),
+        ("Project version:",),
+        ("Resolved stage:",),
+        ("Resolved mode:",),
+        ("Resolved target:",),
+        ("Preflight stamp:",),
+    )
+    issues = []
+    for group in marker_groups:
+        marker = group[0]
+        if marker not in body:
+            issues.append(f"Rule Preflight is missing '{marker}'")
+            continue
+        if not has_marker_with_value(body, group):
+            issues.append(f"Rule Preflight field '{marker}' must have a non-empty value")
+    return issues
+
+
+def validate_next_action(text: str) -> list[str]:
+    body = extract_section(text, REQUIRED_SECTIONS["Next Action"])
+    if is_shallow(body):
+        return ["Next Action section must state a concrete decision and next step"]
+    allowed = ("continue", "stop", "revise", "rerun", "escalate", "handoff", "继续", "停止", "修订", "重跑", "升级", "交接")
+    if not any(marker in normalize(body) for marker in allowed):
+        return ["Next Action must choose continue, stop, revise, rerun, escalate, or handoff"]
+    if not has_why(body):
+        return ["Next Action must include why the next step is appropriate"]
+    return []
+
+
+def validate_stage_identity(text: str, expected_stage: str) -> list[str]:
+    if not expected_stage:
+        return []
+    body = extract_section(text, REQUIRED_SECTIONS["Stage Identity"])
+    if expected_stage.lower() not in body.lower():
+        return [f"Stage Identity must mention expected stage '{expected_stage}'"]
+    return []
+
+
+def validate_internal_meta(text: str) -> list[str]:
+    issues = []
+    for pattern in INTERNAL_META_PATTERNS:
+        if re.search(pattern, text, flags=re.IGNORECASE):
+            issues.append(f"stage report contains internal or service-style meta language: {pattern}")
+    return issues
+
+
+def validate(path: Path, expected_stage: str = "") -> list[str]:
+    if not path.exists():
+        return [f"stage report does not exist: {path}"]
+    text = path.read_text(encoding="utf-8")
+    issues = []
+    missing_sections = find_missing_sections(text)
+    if missing_sections:
+        issues.append(f"stage report is missing required sections: {', '.join(missing_sections)}")
+    if not missing_sections:
+        issues.extend(validate_rule_preflight(text))
+        issues.extend(validate_stage_identity(text, expected_stage))
+        issues.extend(validate_core_table(text))
+        issues.extend(validate_evidence_section(text))
+        issues.extend(validate_next_action(text))
+    issues.extend(validate_internal_meta(text))
+    return issues
+
+
+def main():
+    args = parse_args()
+    issues = validate(Path(args.stage_report), args.stage)
+    if issues:
+        for issue in issues:
+            print(issue, file=sys.stderr)
+        return 1
+    print("stage report is valid")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

package/package-assets/shared/lab/.managed/templates/stage-report.md

@@ -0,0 +1,52 @@
+# Stage Report
+
+## Rule Preflight
+
+- Rule source file:
+- Rule source revision:
+- Project version:
+- Resolved stage:
+- Resolved mode:
+- Resolved target:
+- Preflight stamp:
+- Override reason, if any:
+
+## Stage Identity
+
+- Stage:
+- Target:
+- Date:
+- Status:
+- Primary artifact:
+- Next owner:
+
+## Core Explanation Table
+
+| Question | Plain Answer |
+|---|---|
+| 这是什么阶段？ |  |
+| 背景是什么？ |  |
+| 为什么现在要做？ |  |
+| 这轮具体做了什么？ |  |
+| 怎么做的？ |  |
+| 结果好的地方是什么？ |  |
+| 结果坏的地方是什么？ |  |
+| 这验证了什么？ |  |
+| 还没有验证什么？ |  |
+| 是否需要改进？为什么？ |  |
+| 下一步怎么改？为什么这样改？ |  |
+| 关键证据在哪里？ |  |
+| 现在应该继续、停止、重做还是升级？ |  |
+
+## Evidence And Artifacts
+
+- Primary artifact:
+- Supporting artifacts:
+- Validation commands:
+- Known gaps:
+
+## Next Action
+
+- Decision: continue / stop / revise / rerun / escalate / handoff
+- Concrete next step:
+- Why this next step:

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

@@ -42,6 +42,10 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Generate the `Rule Preflight` block from `.lab/.managed/rule-manifest.json` with the managed preflight renderer instead of handwriting it from memory.
 - Treat missing, stale, or contradictory `Rule Preflight` data as a stage-contract failure.
 - Project-installed rules take priority over model memory. If remembered patterns conflict with the installed rule source, follow the installed source recorded in `.lab/.managed/rule-manifest.json`.
+- Before a `/lab:*` stage reaches a final handoff, write or update one plain-language stage report under `.lab/stage-reports/` from `.lab/.managed/templates/stage-report.md`.
+- The stage report must include a filled `Core Explanation Table` that answers, in workflow language and plain language: background, why now, what was done, how it was done, what worked, what did not work, what was verified, what remains unverified, whether improvement is needed and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Stage reports are closeout and handoff artifacts, not a new user command and not a replacement for stage-specific artifacts such as idea memos, iteration reports, final reports, or write-iteration records.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage <stage>` before claiming the stage is complete, and include the stage-report path plus validation result in the final user-facing summary.
 - Final paper output should default to LaTeX, and its manuscript language should be decided separately from the workflow language.
 - Separate sourced facts from model-generated hypotheses.
 - Preserve failed runs, failed ideas, and limitations.
@@ -317,6 +321,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - No auto start without an explicit autonomy level and `Approval status: approved`.
 - No final report without validated normalized results.
 - No paper-writing round without stable report artifacts, an approved framing artifact, evidence links, and LaTeX manuscript output.
+- No stage-final handoff without a validated plain-language stage report.
 - No final-draft or export round without passing section-quality, claim-safety, and manuscript-delivery validation.
 - No final-draft or export round with mismatched `workflow_language` and `paper_language` unless the latest write iteration records the language decision audit that justified the final manuscript language and the persisted workflow-language paper-layer path.
 

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

@@ -194,3 +194,9 @@
 - If the user chooses to convert, persist `paper_language_finalization_decision: convert-to-paper-language`
 - While the real experiment process is still alive, emit only a progress update and keep waiting. Do not present a terminal summary for that rung until the process exits or the rung hits an explicit stop boundary.
 - While the loop is healthy, do not ask the user to trigger the next poll. Keep polling until a meaningful change, keepalive boundary, stop boundary, escalation boundary, or terminal boundary is reached.
+
+## Stage Report Closeout
+
+- At every stop, failure, escalation, or final handoff, write or update `.lab/stage-reports/<date>--auto--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what ran, how the loop ran, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage auto` and include the report path plus validation result in the final user-facing summary.

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

@@ -66,3 +66,9 @@
 6. Recommended approved dataset package
 7. Risks and exclusions
 8. Approval gate
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--data--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what changed, how the dataset package was chosen, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage data` and include the report path plus validation result in the final user-facing summary.

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

@@ -69,3 +69,9 @@
 5. Recommended framing pack
 6. Forbidden claims and wording
 7. Approval gate
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--framing--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what naming or framing changed, how it was checked, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage framing` and include the report path plus validation result in the final user-facing summary.

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

@@ -119,6 +119,12 @@
 28. Minimum viable experiment
 29. Idea source log aligned with the two literature sweeps
 
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--idea--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what idea work was done, how sources and brainstorm passes were used, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage idea` and include the report path plus validation result in the final user-facing summary.
+
 ## Writing Standard
 
 - Keep the problem statement short, concrete, and easy to scan.

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

@@ -78,3 +78,9 @@ If the loop stops without success, record:
 - If the next move depends on an unresolved assumption, ask one clarifying question at a time.
 - If more than one next hypothesis is credible, present 2-3 approaches with trade-offs and recommend the next bounded experiment before changing the mission state.
 - Keep an approval gate when a proposed change would alter the frozen mission instead of only changing the implementation hypothesis.
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--iterate--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what rounds ran, how the loop evaluated them, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage iterate` and include the report path plus validation result in the final user-facing summary.

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

@@ -90,3 +90,9 @@
 - If a missing assumption would change report interpretation, ask one clarifying question at a time.
 - If there are multiple defensible report framings, present 2-3 approaches with trade-offs and recommend the most evidence-faithful framing before writing.
 - Keep an approval gate when the reporting frame would materially affect what the paper later claims.
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--report--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what report artifacts were produced, how evidence was carried forward, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage report` and include the report path plus validation result in the final user-facing summary.

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

@@ -58,3 +58,9 @@
 - If there are multiple legitimate review framings, present 2-3 approaches with trade-offs and recommend the strictest useful framing.
 - Do not use brainstorming to soften critique; once scope is clear, stay in reviewer mode and deliver findings directly.
 - Call out the strongest remaining alternative explanation and the strongest boundary risk when either one could materially narrow the claim.
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--review--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what was reviewed, how the review was performed, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage review` and include the report path plus validation result in the final user-facing summary.

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

@@ -55,3 +55,9 @@
 - If the next run depends on an unresolved assumption, ask one clarifying question at a time.
 - If there are multiple defensible tiny-run options, present 2-3 approaches with trade-offs and recommend the cheapest informative run.
 - Only ask for approval when choosing a run path would materially spend more time or compute than the default smallest experiment.
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--run--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what ran, how it ran, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage run` and include the report path plus validation result in the final user-facing summary.

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

@@ -72,3 +72,9 @@
 - evaluation normalization
 - bounded iteration
 - final report
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--spec--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what change artifacts were created, how the spec was structured, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage spec` and include the report path plus validation result in the final user-facing summary.

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

@@ -303,3 +303,9 @@ Do not enter prose polish until the current section has passed the reference-con
 - If the user asks to continue tightening the same section, default to a section-level acceptance review first instead of another immediate prose-polish pass.
 - Only recommend another tighten/compress/polish pass after the current section has passed the section-level acceptance gate.
 - If the round introduces or revises key terms, abbreviations, metrics, or mechanism names, include a short terminology note in the final user-facing response that says the full form, approved short form if any, what each term is, and why it matters here, and point to `.lab/writing/terminology-glossary.md` plus the write iteration artifact for the full terminology audit.
+
+## Stage Report Closeout
+
+- Before final handoff, write or update `.lab/stage-reports/<date>--write--<target>.md` from `.lab/.managed/templates/stage-report.md`.
+- Fill the `Core Explanation Table` in plain language: background, why now, what section or asset changed, how evidence and writing rules were applied, what worked, what did not work, what was verified, what remains unverified, what needs improvement and why, how to improve and why, key evidence, and the continue/stop/revise/rerun/escalate/handoff decision.
+- Run `.lab/.managed/scripts/validate_stage_report.py --stage-report <stage-report> --stage write` and include the report path plus validation result in the final user-facing summary.

package/package.json

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