submission-pipelinelisted

# Submission Pipeline ## Core Rule Before submission, run **every reviewer lens at once**, dedupe across them, keep only findings that survive a confidence gate, and produce a single go/no-go report with a submission checklist. This is breadth-first (the whole manuscript, all lenses) — distinct from `/peer-review` (one referee report) and `/claim-check` (depth on each claim). It reports; it does not edit. Fixing a flagged claim is the author's call (and a Protected Claim). ## When to Use Invoke with `/submission-pipeline` when: - The manuscript is draft-complete and you want a pre-submission sweep - You want to pre-empt Reviewer 2 across rigor, integrity, and facts in one pass - Running headless (`/submission-pipeline mode:headless`) to produce a report artifact ## Process ### Phase 1 — Scope 1. Read `MANUSCRIPT_MAP.md` (thesis, contribution, venue) and assemble the manuscript file set (`main.tex` + `\input` sections). Note the target venue for `/journal-fit`. ### Phase 2 — Parallel review (run together, don't serialize) 2. Dispatch in parallel: - **`peer-reviewer`** agent — novelty, soundness, claim↔evidence, structure, recommendation. - **`integrity-reviewer`** agent — overclaim, p-hacking/HARKing, citation misuse, missing limitations. - **`fact-checker`** agent — claim-by-claim Supported / Overstated / Unsupported / Uncited. 3. In parallel, run the deterministic + checklist audits and collect their results: - **`/citation-audit`** (dangling/orphan/malfo