superlab 0.1.24 → 0.1.26

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

@@ -58,7 +58,8 @@ Use the same repository artifacts and stage boundaries every time.
 - `iterate` requires a normalized summary from `scripts/eval_report.py`.
 - `run`, `iterate`, `auto`, and `report` should all follow `.lab/context/eval-protocol.md`, including its recorded sources for metrics and comparison implementations.
 - `write` requires an approved framing artifact from the `framing` stage.
-- `write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+- `write` requires stable report artifacts, a mini-outline, the active section guide, the matching bundled examples when available, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+- Final-draft or export rounds in `write` should materialize paper-facing tables, figure placeholders, a non-empty `references.bib`, and pass `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper`.
 
 ## How to Ask for `/lab auto`
 

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

@@ -6,4 +6,4 @@ argument-hint: section or writing target
 Use the installed `lab` skill at `.codex/skills/lab/SKILL.md`.
 
 Execute the requested `/lab:write` stage against the user's argument now. Do not only recommend another lab stage. If a blocking prerequisite is missing, say exactly what is missing and ask at most one clarifying question.
-This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.codex/skills/lab/references/paper-writing/`, and for `abstract`, `introduction`, or `method` it must also read `.codex/skills/lab/references/paper-writing/examples/index.md` plus the matching examples index and 1-2 concrete example files. Then it should run `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, and revise only one section.
+This command runs the `/lab:write` stage. It requires an approved framing artifact from `/lab:framing`, must read the matching section reference from `.codex/skills/lab/references/paper-writing/`, and for any section with a bundled example bank it must also read `.codex/skills/lab/references/paper-writing/examples/index.md` plus the matching examples index and 1-2 concrete example files. Then it should run `paper-review.md` and `does-my-writing-flow-source.md`, build a mini-outline, plan the section's paper-facing tables/figures/citations, and revise only one section. Final-draft or export rounds must run `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper` before stopping.

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

@@ -52,7 +52,8 @@ argument-hint: workflow question or stage choice
 - `/lab:iterate` requires a normalized summary from `scripts/eval_report.py`.
 - `/lab:run`, `/lab:iterate`, `/lab:auto`, and `/lab:report` should all follow `.lab/context/eval-protocol.md`, including its recorded sources for metrics and comparison implementations.
 - `/lab:write` requires an approved framing artifact from `/lab:framing`.
-- `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+- `/lab:write` requires stable report artifacts, a mini-outline, the active section guide, the matching bundled examples when available, `paper-review.md`, and `does-my-writing-flow-source.md`, and should only change one section per round.
+- Final-draft or export rounds in `/lab:write` should materialize paper-facing tables, figure placeholders, a non-empty `references.bib`, and pass `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper`.
 
 ## How to Ask for `/lab:auto`
 

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

@@ -0,0 +1,175 @@
+#!/usr/bin/env python3
+import argparse
+import re
+import sys
+from pathlib import Path
+
+
+ABSOLUTE_PATH_MARKERS = ("/Users/", "/home/", "/tmp/", "/private/tmp/")
+REQUIRED_TABLE_FILES = ("main-results.tex", "ablations.tex")
+REQUIRED_FIGURE_FILES = ("method-overview.tex", "results-overview.tex")
+
+
+def parse_args():
+    parser = argparse.ArgumentParser(
+        description="Validate that a paper delivery contains basic manuscript-ready assets."
+    )
+    parser.add_argument("--paper-dir", required=True, help="Path to the paper deliverable root")
+    return parser.parse_args()
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8")
+
+
+def check_exists(path: Path, issues: list[str], label: str):
+    if not path.exists():
+        issues.append(f"missing required file: {label} ({path})")
+
+
+def check_bibliography(paper_dir: Path, issues: list[str]):
+    bib_path = paper_dir / "references.bib"
+    check_exists(bib_path, issues, "references.bib")
+    if not bib_path.exists():
+        return
+    text = read_text(bib_path)
+    if "TODO" in text or "todo" in text or "Add bibliography entries" in text or "@" not in text:
+        issues.append("missing a non-empty references.bib")
+
+
+def check_global_tex(paper_dir: Path, issues: list[str]):
+    tex_files = sorted(paper_dir.rglob("*.tex"))
+    combined = "\n".join(read_text(path) for path in tex_files)
+
+    if r"\cite{" not in combined:
+        issues.append("missing citation commands in manuscript tex files")
+    if "+/-" in combined:
+        issues.append("replace '+/-' with LaTeX \\pm formatting")
+    if any(marker in combined for marker in ABSOLUTE_PATH_MARKERS):
+        issues.append("manuscript tex files must not contain absolute local paths")
+
+
+def check_table_file(path: Path, issues: list[str], label: str):
+    if not path.exists():
+        if label == "tables/main-results.tex":
+            issues.append("missing a main results table")
+        elif label == "tables/ablations.tex":
+            issues.append("missing an ablation table")
+        else:
+            issues.append(f"missing required file: {label} ({path})")
+        return
+    text = read_text(path)
+    if r"\begin{table}" not in text:
+        issues.append(f"{label} must contain a table environment")
+    if r"\caption{" not in text or r"\label{" not in text:
+        issues.append(f"{label} must contain both caption and label")
+    if not all(token in text for token in (r"\toprule", r"\midrule", r"\bottomrule")):
+        issues.append(f"{label} must use booktabs structure")
+
+
+def check_figure_file(path: Path, issues: list[str], label: str):
+    if not path.exists():
+        if label == "figures/method-overview.tex":
+            issues.append("missing a method figure placeholder")
+        elif label == "figures/results-overview.tex":
+            issues.append("missing an experiments figure placeholder")
+        else:
+            issues.append(f"missing required file: {label} ({path})")
+        return
+    text = read_text(path)
+    if r"\begin{figure}" not in text:
+        issues.append(f"{label} must contain a figure environment")
+    if r"\caption{" not in text or r"\label{" not in text:
+        issues.append(f"{label} must contain both caption and label")
+    if "Figure intent:" not in text and "图意图：" not in text:
+        issues.append(f"{label} must explain figure intent")
+
+
+def check_experiments_section(paper_dir: Path, issues: list[str]):
+    experiments = paper_dir / "sections" / "experiments.tex"
+    check_exists(experiments, issues, "sections/experiments.tex")
+    if not experiments.exists():
+        return
+    text = read_text(experiments)
+    has_table = any(
+        token in text
+        for token in (
+            r"\input{tables/main-results}",
+            r"\input{tables/ablations}",
+            r"\begin{table}",
+        )
+    )
+    has_figure = any(
+        token in text
+        for token in (
+            r"\input{figures/results-overview}",
+            r"\begin{figure}",
+        )
+    )
+    if not has_table:
+        issues.append("experiments section is missing a main results table")
+    if not has_figure:
+        issues.append("experiments section is missing an experiments figure placeholder")
+
+
+def check_method_section(paper_dir: Path, issues: list[str]):
+    method = paper_dir / "sections" / "method.tex"
+    check_exists(method, issues, "sections/method.tex")
+    if not method.exists():
+        return
+    text = read_text(method)
+    has_figure = any(
+        token in text
+        for token in (
+            r"\input{figures/method-overview}",
+            r"\begin{figure}",
+        )
+    )
+    if not has_figure:
+        issues.append("method section is missing a method figure placeholder")
+
+
+def check_main_tex(paper_dir: Path, issues: list[str]):
+    main_tex = paper_dir / "main.tex"
+    check_exists(main_tex, issues, "main.tex")
+    if not main_tex.exists():
+        return
+    text = read_text(main_tex)
+    if r"\bibliography{references}" not in text:
+        issues.append("main.tex must include the references bibliography")
+
+
+def main():
+    args = parse_args()
+    paper_dir = Path(args.paper_dir)
+    issues: list[str] = []
+
+    if not paper_dir.exists():
+        print(f"paper directory does not exist: {paper_dir}", file=sys.stderr)
+        return 1
+
+    check_main_tex(paper_dir, issues)
+    check_bibliography(paper_dir, issues)
+    check_global_tex(paper_dir, issues)
+    check_method_section(paper_dir, issues)
+    check_experiments_section(paper_dir, issues)
+
+    tables_dir = paper_dir / "tables"
+    check_table_file(tables_dir / REQUIRED_TABLE_FILES[0], issues, "tables/main-results.tex")
+    check_table_file(tables_dir / REQUIRED_TABLE_FILES[1], issues, "tables/ablations.tex")
+
+    figures_dir = paper_dir / "figures"
+    check_figure_file(figures_dir / REQUIRED_FIGURE_FILES[0], issues, "figures/method-overview.tex")
+    check_figure_file(figures_dir / REQUIRED_FIGURE_FILES[1], issues, "figures/results-overview.tex")
+
+    if issues:
+        for issue in issues:
+            print(issue, file=sys.stderr)
+        return 1
+
+    print("manuscript delivery artifacts are valid")
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

package/package-assets/shared/lab/.managed/templates/artifact-status.md

@@ -0,0 +1,28 @@
+# Artifact Status
+
+## Deliverable Status
+
+- Collaborator-facing report path:
+- Managed main tables path:
+- Current report mode:
+- Why this status is appropriate:
+
+## Workflow Audit
+
+- Latest completed action:
+- Latest artifact path:
+- Latest run or report id:
+- Rerun or validation notes:
+
+## Internal Provenance
+
+- Frozen result artifacts used:
+- Canonical context files refreshed:
+- Evidence index anchors:
+
+## Paper Handoff
+
+- Sections ready for `/lab:write`:
+- Evidence bundles to cite:
+- Claims that still need stronger support:
+- Paper-finishing items still open:

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

@@ -105,11 +105,6 @@
 - Final performance summary:
 - Table coverage:
 
-## Artifact Status
-
-- Deliverables or workflow artifacts that are ready:
-- Artifact status notes that are not scientific findings:
-
 ## Main Results
 
 Summarize validated iteration outcomes.
@@ -129,9 +124,3 @@ Describe unresolved risks and external validity limits.
 ## Next Steps
 
 List concrete follow-up actions.
-
-## Paper Handoff
-
-- Sections ready for `/lab:write`:
-- Evidence bundles to cite:
-- Claims that still need stronger support:

package/package-assets/shared/lab/.managed/templates/paper-figure.tex

@@ -0,0 +1,6 @@
+\begin{figure}[t]
+\centering
+\fbox{\rule{0pt}{1.2in}\rule{0.9\linewidth}{0pt}}
+\caption{Figure title. Figure intent: explain what this figure should show and why the reader needs it.}
+\label{fig:placeholder}
+\end{figure}

package/package-assets/shared/lab/.managed/templates/paper-references.bib

@@ -0,0 +1,9 @@
+% Add paper-facing bibliography entries here.
+% Keep keys stable with the manuscript's \cite{...} usage.
+
+@article{placeholder2026,
+  title = {Replace with a real cited work before finalizing},
+  author = {Placeholder, Example},
+  journal = {Placeholder Venue},
+  year = {2026}
+}

package/package-assets/shared/lab/.managed/templates/paper-table.tex

@@ -0,0 +1,13 @@
+\begin{table}[t]
+\caption{One-sentence message of the table and the evaluation protocol.}
+\label{tab:placeholder}
+\centering
+\begin{tabular}{lcc}
+\toprule
+Method & Metric 1 $\uparrow$ & Metric 2 $\uparrow$ \\
+\midrule
+Ours & 0.0000 & 0.0000 \\
+Baseline & 0.0000 & 0.0000 \\
+\bottomrule
+\end{tabular}
+\end{table}

package/package-assets/shared/lab/context/auto-mode.md

@@ -51,8 +51,8 @@ If `eval-protocol.md` declares structured rung entries, auto mode follows those
 
 - Run stage contract: write persistent outputs under `results_root`.
 - Iterate stage contract: update persistent outputs under `results_root`.
-- Review stage contract: update canonical review context such as `.lab/context/decisions.md`, `state.md`, `open-questions.md`, or `evidence-index.md`.
-- Report stage contract: write the final report to `<deliverables_root>/report.md`.
+- Review stage contract: update canonical review context such as `.lab/context/decisions.md`, `state.md`, `workflow-state.md`, `open-questions.md`, or `evidence-index.md`.
+- Report stage contract: write `<deliverables_root>/report.md`, `<deliverables_root>/main-tables.md`, and `<deliverables_root>/artifact-status.md`.
 - Write stage contract: write LaTeX output under `<deliverables_root>/paper/`.
 
 ## Promotion Policy

package/package-assets/shared/lab/context/session-brief.md

@@ -24,7 +24,7 @@ One sentence describing the active research mission.
 ## Read First
 
 1. `.lab/context/mission.md`
-2. `.lab/context/state.md`
+2. `.lab/context/workflow-state.md`
 3. `.lab/context/evidence-index.md`
 
 ## Do Not Change Silently

package/package-assets/shared/lab/context/state.md

@@ -1,19 +1,25 @@
-# Workflow State
+# Research State
 
-## Current Stage
+## Approved Direction
 
-- Active stage:
-- Current objective:
-- Next required output:
+- One-sentence problem:
+- Approved direction:
+- Strongest supported claim:
 
-## Latest Update
+## Evidence Boundary
 
-- Last completed action:
-- Latest artifact path:
-- Latest run or report id:
+- What the current evidence really supports:
+- What is still outside the boundary:
+- Biggest research risk:
 
-## Next Step
+## Active Research Track
 
-- Immediate next action:
-- Blocking issue:
-- Human decision needed:
+- Current research focus:
+- Primary metric:
+- Dataset or benchmark scope:
+
+## Current Research Constraints
+
+- Hard constraints:
+- Claim boundary:
+- Conditions that require reopening the direction:

package/package-assets/shared/lab/context/workflow-state.md

@@ -0,0 +1,19 @@
+# Workflow State
+
+## Current Stage
+
+- Active stage:
+- Current objective:
+- Next required output:
+
+## Latest Update
+
+- Last completed action:
+- Latest artifact path:
+- Latest run or report id:
+
+## Next Step
+
+- Immediate next action:
+- Blocking issue:
+- Human decision needed:

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

@@ -8,7 +8,7 @@ For a new AI session, read these files in order:
 
 1. `.lab/context/session-brief.md`
 2. `.lab/context/mission.md`
-3. `.lab/context/state.md`
+3. `.lab/context/workflow-state.md`
 4. `.lab/context/evidence-index.md`
 
 Only expand to additional context when the brief points to it.
@@ -24,13 +24,15 @@ For auto-mode orchestration or long-running experiment campaigns, also read:
 
 ## Workflow Boundaries
 
-- `.lab/context/` holds durable project research state.
+- `.lab/context/` holds durable project research state plus lightweight workflow state.
 - `.lab/changes/`, `.lab/iterations/`, and `.lab/writing/` hold workflow control artifacts, lightweight manifests, and change-local harnesses.
 - `.lab/.managed/` holds tool-managed templates and scripts.
 - Durable run outputs belong under the configured `results_root`, not inside `.lab/changes/`.
 - Figures and plots belong under the configured `figures_root`, not inside `.lab/changes/`.
 - Deliverables belong under the configured `deliverables_root`, not inside `.lab/context/`.
 - Change-local `data/` directories may hold lightweight manifests or batch specs, but not the canonical dataset copy.
+- `.lab/context/state.md` holds durable research state; `.lab/context/workflow-state.md` holds live workflow state.
+- `.lab/context/summary.md` is the durable project summary; `.lab/context/session-brief.md` is the next-session startup brief.
 - `.lab/context/auto-mode.md` defines the bounded autonomous envelope; `.lab/context/auto-status.md` records live state for resume and handoff.
 - If the user provides a LaTeX template directory, validate it and attach it through `paper_template_root` before drafting.
 - Treat attached template directories as user-owned assets. Do not rewrite template files unless the user explicitly asks.

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

@@ -83,7 +83,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 ### `/lab:auto`
 
 - Use this stage to orchestrate approved execution stages with bounded autonomy.
-- Read `.lab/config/workflow.json`, `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/decisions.md`, `.lab/context/data-decisions.md`, `.lab/context/evidence-index.md`, `.lab/context/terminology-lock.md`, `.lab/context/auto-mode.md`, and `.lab/context/auto-status.md` before acting.
+- Read `.lab/config/workflow.json`, `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/decisions.md`, `.lab/context/data-decisions.md`, `.lab/context/evidence-index.md`, `.lab/context/terminology-lock.md`, `.lab/context/auto-mode.md`, and `.lab/context/auto-status.md` before acting.
 - Treat `.lab/context/auto-mode.md` as the control contract and `.lab/context/auto-status.md` as the live state file.
 - Require `Autonomy level` and `Approval status` in `.lab/context/auto-mode.md` before execution.
 - Treat `L1` as safe-run validation, `L2` as bounded iteration, and `L3` as aggressive campaign mode.
@@ -93,13 +93,13 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - You may add exploratory datasets, benchmarks, and comparison methods inside the approved exploration envelope.
 - You may promote an exploratory addition to the primary package only after the promotion policy in `auto-mode.md` is satisfied and the promotion is written back into `.lab/context/data-decisions.md`, `.lab/context/decisions.md`, `.lab/context/state.md`, and `.lab/context/session-brief.md`.
 - Poll long-running commands until they complete, time out, or hit a stop condition.
-- Update `.lab/context/auto-status.md`, `.lab/context/state.md`, `.lab/context/decisions.md`, `.lab/context/data-decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/session-brief.md` as the campaign advances.
+- Update `.lab/context/auto-status.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/decisions.md`, `.lab/context/data-decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/session-brief.md` as the campaign advances.
 - Keep an explicit approval gate when a proposed action would leave the frozen core defined by the auto-mode contract.
 
 ### `/lab:spec`
 
 - Read `.lab/config/workflow.json` before drafting the change.
-- Read `.lab/context/mission.md`, `.lab/context/decisions.md`, `.lab/context/state.md`, and `.lab/context/data-decisions.md` before drafting the change.
+- Read `.lab/context/mission.md`, `.lab/context/decisions.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, and `.lab/context/data-decisions.md` before drafting the change.
 - Use `.lab/changes/<change-id>/` as the canonical lab change directory.
 - Convert the approved idea into lab change artifacts using `.lab/.managed/templates/proposal.md`, `.lab/.managed/templates/design.md`, `.lab/.managed/templates/spec.md`, and `.lab/.managed/templates/tasks.md`.
 - Update `.lab/context/state.md` and `.lab/context/decisions.md` after freezing the spec.
@@ -108,12 +108,12 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 ### `/lab:run`
 
 - Start with the smallest meaningful experiment.
-- Read `.lab/context/mission.md`, `.lab/context/state.md`, and `.lab/context/data-decisions.md` before choosing the run.
+- Read `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, and `.lab/context/data-decisions.md` before choosing the run.
 - Register the run with `.lab/.managed/scripts/register_run.py`.
 - Normalize the result with `.lab/.managed/scripts/eval_report.py`.
 - Validate normalized output with `.lab/.managed/scripts/validate_results.py`.
 - Read `.lab/context/eval-protocol.md` before choosing the smallest run so the first experiment already targets the approved tables, metrics, and gates.
-- Update `.lab/context/state.md`, `.lab/context/evidence-index.md`, and `.lab/context/eval-protocol.md` after the run.
+- Update `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/evidence-index.md`, and `.lab/context/eval-protocol.md` after the run.
 - If the evaluation protocol is still skeletal, initialize the smallest trustworthy source-backed version before treating the run as the protocol anchor.
 
 ### `/lab:iterate`
@@ -128,13 +128,13 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
   - maximum iteration count
 - Only change implementation hypotheses within the loop.
 - Require a normalized evaluation report each round.
-- Read `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/decisions.md`, and `.lab/context/evidence-index.md` at the start of each round.
+- Read `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/decisions.md`, and `.lab/context/evidence-index.md` at the start of each round.
 - Read `.lab/context/data-decisions.md` before changing benchmark-facing experiments.
 - Read `.lab/context/eval-protocol.md` before changing evaluation ladders, sample sizes, or promotion gates.
 - Keep metric definitions, baseline behavior, and comparison implementations anchored to the source-backed evaluation protocol before changing thresholds, gates, or ladder transitions.
 - Switch to diagnostic mode if risk increases for two consecutive rounds.
 - Write round reports with `.lab/.managed/templates/iteration-report.md`.
-- Update `.lab/context/state.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, `.lab/context/open-questions.md`, and `.lab/context/eval-protocol.md` each round as needed.
+- Update `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, `.lab/context/open-questions.md`, and `.lab/context/eval-protocol.md` each round as needed.
 - Keep `.lab/context/eval-protocol.md` synchronized with accepted ladder changes, benchmark scope, and source-backed implementation deviations.
 - Stop at threshold success or iteration cap, and record blockers plus next-best actions when the campaign ends without success.
 
@@ -151,13 +151,13 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 ### `/lab:report`
 
 - Summarize all validated iteration summaries.
-- Read `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/data-decisions.md` before drafting.
+- Read `.lab/context/mission.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, `.lab/context/decisions.md`, `.lab/context/evidence-index.md`, and `.lab/context/data-decisions.md` before drafting.
 - Read `.lab/context/eval-protocol.md` before choosing tables, thresholds, or final result framing.
 - Keep metric definitions, comparison semantics, and implementation references anchored to the approved evaluation protocol instead of re-deriving them during reporting.
 - Aggregate them with `.lab/.managed/scripts/summarize_iterations.py`.
-- Write the final document with `.lab/.managed/templates/final-report.md` and the managed table summary with `.lab/.managed/templates/main-tables.md`.
+- Write the final document with `.lab/.managed/templates/final-report.md`, the managed table summary with `.lab/.managed/templates/main-tables.md`, and the internal handoff with `.lab/.managed/templates/artifact-status.md`.
 - Keep failed attempts and limitations visible.
-- Update `.lab/context/mission.md`, `.lab/context/eval-protocol.md`, `.lab/context/state.md`, and `.lab/context/evidence-index.md` with report-level handoff notes.
+- Update `.lab/context/mission.md`, `.lab/context/eval-protocol.md`, `.lab/context/state.md`, `.lab/context/workflow-state.md`, and `.lab/context/evidence-index.md` with report-level handoff notes.
 - If canonical context is still skeletal, hydrate the smallest trustworthy version from frozen artifacts before finalizing the report.
 - If collaborator-critical fields remain missing after hydration, downgrade to an `artifact-anchored interim report` instead of presenting a final collaborator-ready report.
 
@@ -172,14 +172,19 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Write one paper section or one explicit subproblem per round.
 - Bind each claim to evidence from `report`, iteration reports, or normalized summaries.
 - Write planning artifacts with `.lab/.managed/templates/paper-plan.md`, `.lab/.managed/templates/paper-section.md`, and `.lab/.managed/templates/write-iteration.md`.
-- Write final manuscript artifacts with `.lab/.managed/templates/paper.tex` and `.lab/.managed/templates/paper-section.tex`.
+- Write final manuscript artifacts with `.lab/.managed/templates/paper.tex`, `.lab/.managed/templates/paper-section.tex`, `.lab/.managed/templates/paper-table.tex`, `.lab/.managed/templates/paper-figure.tex`, and `.lab/.managed/templates/paper-references.bib`.
 - Use the vendored paper-writing references under `skills/lab/references/paper-writing/`.
-- For `abstract`, `introduction`, and `method`, also use the vendored example-bank files under `skills/lab/references/paper-writing/examples/`.
+- For any section with a bundled example bank, also use the vendored example-bank files under `skills/lab/references/paper-writing/examples/`.
 - Load only the current section guide, the matching examples index when one exists, 1-2 matching concrete example files, plus `paper-review.md` and `does-my-writing-flow-source.md`.
 - Build a compact mini-outline before prose.
+- Build the paper asset plan before prose when the section carries method or experiments claims.
 - For each subsection, explicitly cover motivation, design, and technical advantage when applicable.
 - Keep terminology stable across rounds and sections.
 - If a claim is not supported by evidence, weaken or remove it.
+- Treat tables, figures, citations, and bibliography as core manuscript content rather than optional polish.
+- Keep paper-facing LaTeX free of absolute local paths, rerun ids, shell transcripts, and internal workflow provenance.
+- Materialize real LaTeX tables and figure placeholders instead of leaving all evidence inside prose paragraphs.
+- Run `.lab/.managed/scripts/validate_manuscript_delivery.py --paper-dir <deliverables_root>/paper` before accepting a final-draft or export round.
 - Before finalizing a round, append and answer the five-dimension self-review checklist and revise unresolved items.
 - Apply paper-writing discipline without changing experimental truth.
 - If the evidence is insufficient, stop and route back to `review` or `iterate`.
@@ -194,7 +199,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - No unconstrained auto mode. Every `/lab:auto` campaign must declare allowed stages, stop conditions, and a promotion policy in `.lab/context/auto-mode.md`.
 - 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 paper-writing round without stable report artifacts, an approved framing artifact, evidence links, LaTeX manuscript output, and a passing manuscript-delivery validation for final-draft or export rounds.
 
 ## References
 
@@ -212,7 +217,7 @@ Use this skill when the user invokes `/lab:*` or asks for the structured researc
 - Write stage guide: `.codex/skills/lab/stages/write.md` or `.claude/skills/lab/stages/write.md`
 - Paper-writing integration: `.codex/skills/lab/references/paper-writing-integration.md` or `.claude/skills/lab/references/paper-writing-integration.md`
 - Vendored paper-writing references: `.codex/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md` or `.claude/skills/lab/references/paper-writing/{abstract,introduction,related-work,method,experiments,conclusion,paper-review,does-my-writing-flow-source}.md`
-- Vendored paper-writing example bank: `.codex/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples}.md` or `.claude/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples}.md`, plus the matching section subdirectories
+- Vendored paper-writing example bank: `.codex/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples,related-work-examples,experiments-examples,conclusion-examples}.md` or `.claude/skills/lab/references/paper-writing/examples/{index,abstract-examples,introduction-examples,method-examples,related-work-examples,experiments-examples,conclusion-examples}.md`, plus the matching section subdirectories
 - Command adapters: the installed `/lab:*` command assets
 - Shared workflow config: `.lab/config/workflow.json`
 - Shared project context: `.lab/context/{mission,state,decisions,evidence-index,open-questions,data-decisions,eval-protocol,auto-mode,auto-status}.md`

package/package-assets/shared/skills/lab/references/paper-writing/examples/conclusion/conservative-claim-boundary.md

@@ -0,0 +1,27 @@
+# Conservative Claim-Boundary LaTeX Example
+
+Use this example to close with the strongest supported claim while keeping the
+boundary explicit.
+
+```tex
+\section{Conclusion}
+
+This paper shows that adding a structured ranking backbone together with a
+post-hoc calibration stage improves uplift ranking under the frozen benchmark
+protocol. Across the three benchmark families used in this work, the full model
+consistently matches or exceeds the strongest baselines and remains stronger
+than the key ablated variants. This makes the main claim narrower than a
+universal superiority claim but stronger than a single-dataset win.
+
+We do not claim that the current method solves uplift modeling in every domain
+or that every design choice helps equally on every benchmark. In particular, the
+calibration stage appears beneficial on some datasets and neutral on others,
+which means its value should be interpreted as setting-dependent rather than as
+a guaranteed gain. That boundary is consistent with recent benchmarking
+practice, which argues for claim discipline and protocol-specific interpretation
+rather than broad overgeneralization~\cite{carlini2019evaluating}.
+
+The most useful next step is to extend the evaluation to a broader set of
+benchmark slices and to test whether the same ranking-versus-calibration split
+remains useful when the label distribution shifts more aggressively.
+```

package/package-assets/shared/skills/lab/references/paper-writing/examples/conclusion-examples.md

@@ -0,0 +1,16 @@
+# Conclusion Example Patterns
+
+Use these examples to end with a bounded claim, not a marketing recap. The
+referenced file is a complete LaTeX conclusion example with explicit claim
+boundary language.
+
+## Recommended Pattern
+
+1. Restate the narrow supported claim.
+2. Restate the strongest evidence in one compact sentence.
+3. State the main limitation or boundary.
+4. End with the next concrete direction, not generic future work.
+
+## Example Files
+
+- `examples/conclusion/conservative-claim-boundary.md`

package/package-assets/shared/skills/lab/references/paper-writing/examples/experiments/figure-placeholder-and-discussion.md

@@ -0,0 +1,44 @@
+# Figure Placeholder and Discussion Example
+
+Use complete figure placeholders when the visual asset is not finalized yet but
+the manuscript already needs a stable figure slot, caption, label, and prose
+attachment.
+
+## Method Figure Placeholder
+
+```tex
+\begin{figure}[t]
+\centering
+\fbox{\rule{0pt}{1.55in}\rule{0.92\linewidth}{0pt}}
+\caption{Method overview. Figure intent: show the full pipeline, highlight the
+boundary between the structured scoring module and the post-hoc calibration
+stage, and make the train-time versus inference-time data flow easy to inspect.}
+\label{fig:method-overview}
+\end{figure}
+```
+
+## Results Figure Placeholder
+
+```tex
+\begin{figure}[t]
+\centering
+\fbox{\rule{0pt}{1.55in}\rule{0.92\linewidth}{0pt}}
+\caption{Benchmark-level results overview. Figure intent: summarize the trend
+across datasets, show error bars or confidence intervals, and reveal whether the
+main gain is stable or dominated by one benchmark.}
+\label{fig:results-overview}
+\end{figure}
+```
+
+## Discussion Example
+
+```tex
+Figure~\ref{fig:method-overview} gives the reader the shortest path to the
+method's logic before the section moves into module details. The figure should
+make it obvious which component produces the structured signal and where the
+post-hoc calibration step changes the final ranking.
+
+Figure~\ref{fig:results-overview} should then complement the tables rather than
+repeat them. Its job is to show whether the gain is stable across datasets and
+seeds, not to claim a new effect that the tables do not already support.
+```