Pre-Submission Report

Aggregates all quality checks into one dated report. Run before submitting to a journal/conference or sharing with collaborators.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

Source slug: pre-submission-report
Write reports to: reviews/<paper-slug>/pre-submission-report/<YYYY-MM-DD-HHMM>.md inside the project, where <paper-slug> is the paper directory name being reviewed (e.g., paper-jtp if reviewing paper-jtp/main.tex). Path is relative to the research project root, not the Task-Management repo.
Citation-integrity companion: when citation integrity runs, write <YYYY-MM-DD-HHMM>.citation-integrity.json beside the report. It is a typed companion, not a second report or INDEX row.
Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
Idempotency: if the minute-based timestamp file exists, append a same-run descriptor ({timestamp}-r2.md, {timestamp}-revision.md) — never overwrite.
Index policy: the aggregate pre-submission report is an output-only artefact and receives no Check=pre-submission-report row. Each reporting gate/check receives its own row with Trigger=pre-submission-report.
Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.