@bohuyeshan/openagent-labforge-core 3.11.1 → 3.11.3

package/generated/skills-bundles/paper/skills/research/document-authoring/auto-claude__paper-write/templates/icml2025.tex

@@ -0,0 +1,87 @@
+% ICML 2025 Paper Template
+% Generated by ARIS paper-write skill
+% Style file: download from https://icml.cc/Conferences/2025/CallForPapers
+
+\documentclass[accepted]{icml2025}
+% For submission: remove [accepted]
+
+% Math
+\usepackage{amsmath,amssymb,amsfonts,amsthm,mathtools}
+
+% Typography
+\usepackage[utf8]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{hyperref}
+\usepackage{url}
+\usepackage{booktabs}
+\usepackage{nicefrac}
+\usepackage{microtype}
+\usepackage{xcolor}
+\usepackage{graphicx}
+\usepackage{subcaption}
+\usepackage{multirow}
+\usepackage{algorithm}
+\usepackage{algorithmic}
+
+% cleveref must be loaded AFTER hyperref
+\usepackage[capitalize,noabbrev]{cleveref}
+
+% Theorems
+\theoremstyle{plain}
+\newtheorem{theorem}{Theorem}[section]
+\newtheorem{proposition}[theorem]{Proposition}
+\newtheorem{lemma}[theorem]{Lemma}
+\newtheorem{corollary}[theorem]{Corollary}
+\theoremstyle{definition}
+\newtheorem{definition}[theorem]{Definition}
+\newtheorem{assumption}[theorem]{Assumption}
+\theoremstyle{remark}
+\newtheorem{remark}[theorem]{Remark}
+
+% cleveref names for custom theorem types
+\crefname{assumption}{Assumption}{Assumptions}
+\Crefname{assumption}{Assumption}{Assumptions}
+
+% Shared math commands
+\input{math_commands}
+
+\icmltitlerunning{Paper Title Here}
+
+\begin{document}
+
+\twocolumn[
+\icmltitle{Paper Title Here}
+
+% Authors — leave anonymous for submission
+% Uncomment and fill for camera-ready
+% \icmlsetsymbol{equal}{*}
+% \begin{icmlauthorlist}
+% \icmlauthor{Author Name}{inst1}
+% \end{icmlauthorlist}
+% \icmlaffiliation{inst1}{Affiliation}
+% \icmlcorrespondingauthor{Author Name}{email@example.com}
+
+\vskip 0.3in
+]
+
+\printAffiliationsAndNotice{}
+
+\begin{abstract}
+\input{sections/0_abstract}
+\end{abstract}
+
+\input{sections/1_introduction}
+\input{sections/2_related_work}
+\input{sections/3_method}
+\input{sections/4_experiments}
+\input{sections/5_conclusion}
+
+\bibliography{references}
+\bibliographystyle{icml2025}
+
+\newpage
+\appendix
+\onecolumn
+\input{sections/A_appendix}
+
+\end{document}

package/generated/skills-bundles/paper/skills/research/document-authoring/auto-claude__paper-write/templates/math_commands.tex

@@ -0,0 +1,48 @@
+% math_commands.tex — Shared notation for ML papers
+% Generated by ARIS paper-write skill
+% Add paper-specific notation below the common commands
+
+% === Common Math Shortcuts ===
+\newcommand{\R}{\mathbb{R}}
+\newcommand{\Z}{\mathbb{Z}}
+\newcommand{\N}{\mathbb{N}}
+\newcommand{\E}{\mathbb{E}}
+\newcommand{\Var}{\mathrm{Var}}
+\newcommand{\Cov}{\mathrm{Cov}}
+
+% Probability
+\newcommand{\Prob}{\mathbb{P}}
+\newcommand{\KL}{\mathrm{KL}}
+
+% Operators
+\DeclareMathOperator*{\argmin}{arg\,min}
+\DeclareMathOperator*{\argmax}{arg\,max}
+\DeclareMathOperator{\tr}{tr}
+\DeclareMathOperator{\diag}{diag}
+\DeclareMathOperator{\softmax}{softmax}
+
+% Vectors and matrices (bold)
+\newcommand{\vx}{\mathbf{x}}
+\newcommand{\vy}{\mathbf{y}}
+\newcommand{\vz}{\mathbf{z}}
+\newcommand{\vw}{\mathbf{w}}
+\newcommand{\vtheta}{\boldsymbol{\theta}}
+\newcommand{\mA}{\mathbf{A}}
+\newcommand{\mI}{\mathbf{I}}
+
+% Norms
+\newcommand{\norm}[1]{\left\|#1\right\|}
+\newcommand{\abs}[1]{\left|#1\right|}
+\newcommand{\inner}[2]{\langle #1, #2 \rangle}
+
+% Distributions
+\newcommand{\Normal}{\mathcal{N}}
+
+% Sets
+\newcommand{\cX}{\mathcal{X}}
+\newcommand{\cY}{\mathcal{Y}}
+\newcommand{\cD}{\mathcal{D}}
+\newcommand{\cL}{\mathcal{L}}
+
+% === Paper-Specific Notation ===
+% Add your paper's custom notation below this line

package/generated/skills-bundles/paper/skills/research/document-authoring/auto-claude__paper-write/templates/neurips2025.tex

@@ -0,0 +1,80 @@
+% NeurIPS 2025 Paper Template
+% Generated by ARIS paper-write skill
+% Style file: download from https://neurips.cc/Conferences/2025/CallForPapers
+
+\documentclass{article}
+\usepackage[preprint]{neurips_2025}
+% For camera-ready: \usepackage[final]{neurips_2025}
+
+% Math
+\usepackage{amsmath,amssymb,amsfonts,amsthm,mathtools}
+
+% Typography
+\usepackage[utf8]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{hyperref}
+\usepackage{url}
+\usepackage{booktabs}
+\usepackage{nicefrac}
+\usepackage{microtype}
+\usepackage{xcolor}
+\usepackage{graphicx}
+\usepackage{subcaption}
+\usepackage{multirow}
+\usepackage{algorithm}
+\usepackage{algorithmic}
+
+% cleveref must be loaded AFTER hyperref
+\usepackage[capitalize,noabbrev]{cleveref}
+
+% Theorems
+\theoremstyle{plain}
+\newtheorem{theorem}{Theorem}[section]
+\newtheorem{proposition}[theorem]{Proposition}
+\newtheorem{lemma}[theorem]{Lemma}
+\newtheorem{corollary}[theorem]{Corollary}
+\theoremstyle{definition}
+\newtheorem{definition}[theorem]{Definition}
+\newtheorem{assumption}[theorem]{Assumption}
+\theoremstyle{remark}
+\newtheorem{remark}[theorem]{Remark}
+
+% cleveref names for custom theorem types
+\crefname{assumption}{Assumption}{Assumptions}
+\Crefname{assumption}{Assumption}{Assumptions}
+
+% Shared math commands
+\input{math_commands}
+
+\title{Paper Title Here}
+
+% Authors — leave anonymous for submission
+% Uncomment and fill for camera-ready
+% \author{
+%   Author Name \\
+%   Affiliation \\
+%   \texttt{email@example.com}
+% }
+
+\begin{document}
+
+\maketitle
+
+\begin{abstract}
+\input{sections/0_abstract}
+\end{abstract}
+
+\input{sections/1_introduction}
+\input{sections/2_related_work}
+\input{sections/3_method}
+\input{sections/4_experiments}
+\input{sections/5_conclusion}
+
+\bibliography{references}
+\bibliographystyle{plainnat}
+
+\newpage
+\appendix
+\input{sections/A_appendix}
+
+\end{document}

package/generated/skills-bundles/paper/skills/research/document-authoring/auto-claude__paper-writing/SKILL.md

@@ -0,0 +1,255 @@
+---
+name: "auto-claude/paper-writing"
+description: "Workflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → paper-write → paper-compile → ULTRAWORK QA to go from a narrative report to a polished, submission-ready PDF. Use when user says \"写论文全流程\", \"write paper pipeline\", \"从报告到PDF\", \"paper writing\", or wants the complete paper generation workflow."
+argument-hint: ["narrative-report-path-or-topic"]
+allowed-tools: "Bash(*), Read, Write, Edit, Grep, Glob, Agent, Skill, mcp__codex__codex, mcp__codex__codex-reply"
+metadata:
+  category: "research/document-authoring"
+---
+
+# Workflow 3: Paper Writing Pipeline
+
+Orchestrate a complete paper writing workflow for: **$ARGUMENTS**
+
+## Overview
+
+This skill chains five sub-skills into a single automated pipeline:
+
+```
+/paper-plan → /paper-figure → /paper-write → /paper-compile → /ulw-loop
+  (outline)     (plots)        (LaTeX)        (build PDF)       (final QA + Oracle verify)
+```
+
+Each phase builds on the previous one's output. The final deliverable is a polished, reviewed `paper/` directory with LaTeX source and compiled PDF.
+
+## Constants
+
+- **VENUE = `ICLR`** — Target venue. Options: `ICLR`, `NeurIPS`, `ICML`. Affects style file, page limit, citation format.
+- **REVIEWER_MODEL = `gpt-5.4`** — Model used via Codex MCP for plan review, figure review, and writing review.
+- **AUTO_PROCEED = true** — Auto-continue between phases. Set `false` to pause and wait for user approval after each phase.
+
+> Override inline: `/paper-writing "NARRATIVE_REPORT.md" — venue: NeurIPS`
+
+## Inputs
+
+This pipeline accepts one of:
+
+1. **`NARRATIVE_REPORT.md`** (best) — structured research narrative with claims, experiments, results, figures
+2. **Research direction + experiment results** — the skill will help draft the narrative first
+3. **Existing `PAPER_PLAN.md`** — skip Phase 1, start from Phase 2
+
+The more detailed the input (especially figure descriptions and quantitative results), the better the output.
+
+## Pipeline
+
+### Phase 1: Paper Plan
+
+Invoke `/paper-plan` to create the structural outline:
+
+```
+/paper-plan "$ARGUMENTS"
+```
+
+**What this does:**
+- Parse NARRATIVE_REPORT.md for claims, evidence, and figure descriptions
+- Build a **Claims-Evidence Matrix** — every claim maps to evidence, every experiment supports a claim
+- Design section structure (5-8 sections depending on paper type)
+- Plan figure/table placement with data sources
+- Scaffold citation structure
+- GPT-5.4 reviews the plan for completeness
+
+**Output:** `PAPER_PLAN.md` with section plan, figure plan, citation scaffolding.
+
+**Checkpoint:** Present the plan summary to the user.
+
+```
+📐 Paper plan complete:
+- Title: [proposed title]
+- Sections: [N] ([list])
+- Figures: [N] auto-generated + [M] manual
+- Target: [VENUE], [PAGE_LIMIT] pages
+
+Shall I proceed with figure generation?
+```
+
+- **User approves** (or AUTO_PROCEED=true) → proceed to Phase 2.
+- **User requests changes** → adjust plan and re-present.
+
+### Phase 2: Figure Generation
+
+Invoke `/paper-figure` to generate data-driven plots and tables:
+
+```
+/paper-figure "PAPER_PLAN.md"
+```
+
+**What this does:**
+- Read figure plan from PAPER_PLAN.md
+- Generate matplotlib/seaborn plots from JSON/CSV data
+- Generate LaTeX comparison tables
+- Create `figures/latex_includes.tex` for easy insertion
+- GPT-5.4 reviews figure quality and captions
+
+**Output:** `figures/` directory with PDFs, generation scripts, and LaTeX snippets.
+
+> **Scope:** Auto-generates ~60% of figures (data plots, comparison tables). Architecture diagrams, pipeline figures, and qualitative result grids must be created manually and placed in `figures/` before proceeding. See `/paper-figure` SKILL.md for details.
+
+**Checkpoint:** List generated vs manual figures.
+
+```
+📊 Figures complete:
+- Auto-generated: [list]
+- Manual (need your input): [list]
+- LaTeX snippets: figures/latex_includes.tex
+
+[If manual figures needed]: Please add them to figures/ before I proceed.
+[If all auto]: Shall I proceed with LaTeX writing?
+```
+
+### Phase 3: LaTeX Writing
+
+Invoke `/paper-write` to generate section-by-section LaTeX:
+
+```
+/paper-write "PAPER_PLAN.md"
+```
+
+**What this does:**
+- Write each section following the plan, with proper LaTeX formatting
+- Insert figure/table references from `figures/latex_includes.tex`
+- Build `references.bib` from citation scaffolding
+- Clean stale files from previous section structures
+- Automated bib cleaning (remove uncited entries)
+- De-AI polish (remove "delve", "pivotal", "landscape"...)
+- GPT-5.4 reviews each section for quality
+
+**Output:** `paper/` directory with `main.tex`, `sections/*.tex`, `references.bib`, `math_commands.tex`.
+
+**Checkpoint:** Report section completion.
+
+```
+✍️ LaTeX writing complete:
+- Sections: [N] written ([list])
+- Citations: [N] unique keys in references.bib
+- Stale files cleaned: [list, if any]
+
+Shall I proceed with compilation?
+```
+
+### Phase 4: Compilation
+
+Invoke `/paper-compile` to build the PDF:
+
+```
+/paper-compile "paper/"
+```
+
+**What this does:**
+- `latexmk -pdf` with automatic multi-pass compilation
+- Auto-fix common errors (missing packages, undefined refs, BibTeX syntax)
+- Up to 3 compilation attempts
+- Post-compilation checks: undefined refs, page count, font embedding
+- Precise page verification via `pdftotext`
+- Stale file detection
+
+**Output:** `paper/main.pdf`
+
+**Checkpoint:** Report compilation results.
+
+```
+🔨 Compilation complete:
+- Status: SUCCESS
+- Pages: [X] (main body) + [Y] (references) + [Z] (appendix)
+- Within page limit: YES/NO
+- Undefined references: 0
+- Undefined citations: 0
+
+Shall I proceed with the ULTRAWORK final QA?
+```
+
+### Phase 5: ULTRAWORK Final QA
+
+Invoke `/ulw-loop` to do a final evidence-based QA pass:
+
+```
+/ulw-loop "Final QA for paper/: verify claims vs figures, references, and compile output" --max-iterations=2
+```
+
+**What this does (recommend 1-2 rounds):**
+
+- Verify claims vs figures and tables
+- Check references, citations, and build artifacts
+- Fix inconsistencies, missing evidence, and presentation gaps
+- Oracle verifies completion; if not verified, iterate
+
+**Output:** `paper/main.pdf` plus a `ULTRAWORK_LOG.md` describing evidence and fixes.
+
+**Format check** (included in improvement loop Step 8): After final recompilation, auto-detect and fix overfull hboxes (content exceeding margins), verify page count vs venue limit, and ensure compact formatting. Any overfull > 10pt is fixed before generating the final PDF.
+
+### Phase 6: Final Report
+
+```markdown
+# Paper Writing Pipeline Report
+
+**Input**: [NARRATIVE_REPORT.md or topic]
+**Venue**: [ICLR/NeurIPS/ICML]
+**Date**: [today]
+
+## Pipeline Summary
+
+| Phase | Status | Output |
+|-------|--------|--------|
+| 1. Paper Plan | ✅ | PAPER_PLAN.md |
+| 2. Figures | ✅ | figures/ ([N] auto + [M] manual) |
+| 3. LaTeX Writing | ✅ | paper/sections/*.tex ([N] sections, [M] citations) |
+| 4. Compilation | ✅ | paper/main.pdf ([X] pages) |
+| 5. ULTRAWORK QA | ✅ | ULTRAWORK_LOG.md |
+
+## Deliverables
+- paper/main.pdf — Final polished paper
+- paper/ULTRAWORK_LOG.md — QA log with evidence and fixes
+
+## Remaining Issues (if any)
+- [items from final review that weren't addressed]
+
+## Next Steps
+- [ ] Visual inspection of PDF
+- [ ] Add any missing manual figures
+- [ ] Submit to [venue] via OpenReview / CMT / HotCRP
+```
+
+## Key Rules
+
+- **Don't skip phases.** Each phase builds on the previous one — skipping leads to errors.
+- **Checkpoint between phases** when AUTO_PROCEED=false. Present results and wait for approval.
+- **Manual figures first.** If the paper needs architecture diagrams or qualitative results, the user must provide them before Phase 3.
+- **Compilation must succeed** before entering the improvement loop. Fix all errors first.
+- **Preserve all PDFs.** The user needs round0/round1/round2 for comparison.
+- **Document everything.** The pipeline report should be self-contained.
+- **Respect page limits.** If the paper exceeds the venue limit, suggest specific cuts before the improvement loop.
+
+## Composing with Other Workflows
+
+```
+/idea-discovery "direction"         ← Workflow 1: find ideas
+implement                           ← write code
+/run-experiment                     ← deploy experiments
+/ulw-loop "paper topic"     ← Workflow 2: iterate research
+/paper-writing "NARRATIVE_REPORT.md"  ← Workflow 3: you are here
+                                         submit! 🎉
+
+Or use /research-pipeline for the Workflow 1+2 end-to-end flow,
+then /paper-writing for the final writing step.
+```
+
+## Typical Timeline
+
+| Phase | Duration | Can sleep? |
+|-------|----------|------------|
+| 1. Paper Plan | 5-10 min | No |
+| 2. Figures | 5-15 min | No |
+| 3. LaTeX Writing | 15-30 min | Yes ✅ |
+| 4. Compilation | 2-5 min | No |
+| 5. Improvement | 15-30 min | Yes ✅ |
+
+**Total: ~45-90 min** for a full paper from narrative report to polished PDF.

package/generated/skills-bundles/paper/skills/research/literature-and-web-search/auto-claude__arxiv/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: "auto-claude/arxiv"
+description: "Search, download, and summarize academic papers from arXiv using MCP tools. Use when user says \"search arxiv\", \"download paper\", \"fetch arxiv\", \"arxiv search\", \"get paper pdf\", or wants to find and save papers from arXiv to the local paper library."
+argument-hint: ["query-or-arxiv-id"]
+allowed-tools: "Read, Write"
+metadata:
+  category: "research/literature-and-web-search"
+---
+# arXiv Paper Search & Download
+
+Search topic or arXiv paper ID: $ARGUMENTS
+
+## Constants
+
+- **PAPER_DIR** - Local directory to save downloaded PDFs. Default: `papers/` in the current project directory.
+- **MAX_RESULTS = 10** - Default number of search results.
+
+> Overrides (append to arguments):
+> - `/arxiv "attention mechanism" - max: 20` - return up to 20 results
+> - `/arxiv "2301.07041" - download` - download a specific paper by ID
+> - `/arxiv "query" - dir: literature/` - save PDFs to a custom directory
+> - `/arxiv "query" - download: all` - download all result PDFs
+
+## MCP Requirement (No Script Fallback)
+
+This skill uses MCP only. Ensure at least one of these is enabled:
+
+- `paper_search_mcp` (preferred, multi-source)
+- `arxiv_mcp` (arXiv-only)
+
+If MCP tools are missing, enable them in config:
+
+```json
+{
+  "mcp_policy": {
+    "enable": ["paper_search_mcp", "arxiv_mcp"]
+  }
+}
+```
+
+## Workflow
+
+### Step 1: Parse Arguments
+
+Parse `$ARGUMENTS` for directives:
+
+- **Query or ID**: main search term or a bare arXiv ID such as `2301.07041` or `cs/0601001`
+- **`- max: N`**: override MAX_RESULTS (e.g., `- max: 20`)
+- **`- dir: PATH`**: override PAPER_DIR (e.g., `- dir: literature/`)
+- **`- download`**: download the first result's PDF after listing
+- **`- download: all`**: download PDFs for all results
+
+If the argument matches an arXiv ID pattern (`YYMM.NNNNN` or `category/NNNNNNN`), skip the search and go directly to Step 3.
+
+### Step 2: Search arXiv (MCP)
+
+Use MCP tools to search:
+
+- Prefer `paper_search_mcp` if available (multi-source).
+- Otherwise use `arxiv_mcp` (arXiv-only).
+
+Call the search tool exposed by the MCP server (the exact tool name appears in your MCP tool list). Pass the query and `MAX_RESULTS`.
+
+Present results as a table:
+
+```text
+| # | arXiv ID   | Title               | Authors        | Date       | Category |
+|---|------------|---------------------|----------------|------------|----------|
+| 1 | 2301.07041 | Attention Is All... | Vaswani et al. | 2017-06-12 | cs.LG    |
+```
+
+### Step 3: Fetch Details for a Specific ID (MCP)
+
+Use the MCP server's fetch/details tool (if provided) to retrieve metadata for a specific arXiv ID.
+
+Display: title, all authors, categories, full abstract, published date, PDF URL, abstract URL.
+
+### Step 4: Download PDFs (MCP)
+
+When download is requested:
+
+- Use MCP download/fetch tool if available.
+- If the MCP server only returns URLs, create the directory and save the URL list so the user can fetch later.
+
+If a local file path is returned:
+
+- Confirm file size > 10 KB (reject smaller files - likely an error HTML page)
+- Add a 1-second delay between consecutive downloads to avoid rate limiting
+- Report: `Downloaded: papers/2301.07041.pdf (842 KB)`
+
+### Step 5: Summarize
+
+For each paper (downloaded or fetched by API):
+
+```markdown
+## [Title]
+
+- **arXiv**: [ID] - [abs_url]
+- **Authors**: [full author list]
+- **Date**: [published]
+- **Categories**: [cs.LG, cs.AI, ...]
+- **Abstract**: [full abstract]
+- **Key contributions** (extracted from abstract):
+  - [contribution 1]
+  - [contribution 2]
+  - [contribution 3]
+- **Local PDF**: papers/[ID].pdf (if downloaded)
+```
+
+### Step 6: Final Output
+
+Summarize what was done:
+
+- `Found N papers for "query"`
+- `Downloaded: papers/2301.07041.pdf (842 KB)` (for each download)
+- Any warnings (rate limit hit, file too small, already exists)
+
+Suggest follow-up skills:
+
+```text
+/research-lit "topic"     - multi-source review: Zotero + Obsidian + local PDFs + web
+/novelty-check "idea"     - verify your idea is novel against these papers
+```
+
+## Key Rules
+
+- Always show the arXiv ID prominently - users need it for citations and reproducibility
+- Verify downloaded PDFs: file must be > 10 KB; warn and delete if smaller
+- Rate limit: wait 1 second between consecutive PDF downloads; retry once after 5 seconds on HTTP 429
+- Never overwrite an existing PDF at the same path - skip it and report "already exists"
+- Handle both arXiv ID formats: new (`2301.07041`) and old (`cs/0601001`)
+- PAPER_DIR is created automatically if it does not exist
+- If the arXiv API is unreachable, report the error clearly and suggest using `/research-lit` with `- sources: web` as a fallback

package/generated/skills-bundles/paper/skills/research/literature-and-web-search/auto-claude__novelty-check/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: "auto-claude/novelty-check"
+description: "Verify research idea novelty against recent literature. Use when user says \"查新\", \"novelty check\", \"有没有人做过\", \"check novelty\", or wants to verify a research idea is novel before implementing."
+argument-hint: ["method-or-idea-description"]
+allowed-tools: "WebSearch, WebFetch, Grep, Read, Glob, mcp__codex__codex"
+metadata:
+  category: "research/literature-and-web-search"
+---
+# Novelty Check Skill
+
+Check whether a proposed method/idea has already been done in the literature: **$ARGUMENTS**
+
+## Constants
+
+- REVIEWER_MODEL = `gpt-5.4` — Model used via Codex MCP. Must be an OpenAI model (e.g., `gpt-5.4`, `o3`, `gpt-4o`)
+
+## Instructions
+
+Given a method description, systematically verify its novelty:
+
+### Phase A: Extract Key Claims
+1. Read the user's method description
+2. Identify 3-5 core technical claims that would need to be novel:
+   - What is the method?
+   - What problem does it solve?
+   - What is the mechanism?
+   - What makes it different from obvious baselines?
+
+### Phase B: Multi-Source Literature Search
+For EACH core claim, search using ALL available sources:
+
+1. **Web Search** (via `WebSearch`):
+   - Search arXiv, Google Scholar, Semantic Scholar
+   - Use specific technical terms from the claim
+   - Try at least 3 different query formulations per claim
+   - Include year filters for 2024-2026
+
+2. **Known paper databases**: Check against:
+   - ICLR 2025/2026, NeurIPS 2025, ICML 2025/2026
+   - Recent arXiv preprints (2025-2026)
+
+3. **Read abstracts**: For each potentially overlapping paper, WebFetch its abstract and related work section
+
+### Phase C: Cross-Model Verification
+Call REVIEWER_MODEL via Codex MCP (`mcp__codex__codex`) with xhigh reasoning:
+```
+config: {"model_reasoning_effort": "xhigh"}
+```
+Prompt should include:
+- The proposed method description
+- All papers found in Phase B
+- Ask: "Is this method novel? What is the closest prior work? What is the delta?"
+
+### Phase D: Novelty Report
+Output a structured report:
+
+```markdown
+## Novelty Check Report
+
+### Proposed Method
+[1-2 sentence description]
+
+### Core Claims
+1. [Claim 1] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]
+2. [Claim 2] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]
+...
+
+### Closest Prior Work
+| Paper | Year | Venue | Overlap | Key Difference |
+|-------|------|-------|---------|----------------|
+
+### Overall Novelty Assessment
+- Score: X/10
+- Recommendation: PROCEED / PROCEED WITH CAUTION / ABANDON
+- Key differentiator: [what makes this unique, if anything]
+- Risk: [what a reviewer would cite as prior work]
+
+### Suggested Positioning
+[How to frame the contribution to maximize novelty perception]
+```
+
+### Important Rules
+- Be BRUTALLY honest — false novelty claims waste months of research time
+- "Applying X to Y" is NOT novel unless the application reveals surprising insights
+- Check both the method AND the experimental setting for novelty
+- If the method is not novel but the FINDING would be, say so explicitly
+- Always check the most recent 6 months of arXiv — the field moves fast