paperlint 7.0.0 → 7.2.0

package/docs/rules/cycle/port-done.md

@@ -0,0 +1,75 @@
+# cycle/port-done
+
+**Level:** error · **Reads:** `paper.tex` → the paper's `paperlint.json` (`cycles`) → the venue
+preset's `template` · **Reported on:** `paper.tex`
+
+## What it catches
+
+The current cycle declares `"phase": "porting"` — the source is still in the previous venue's
+template, so the venue's format rules are silent — and the paper's `\documentclass` is already the
+one the venue's preset requires. The port is done and the declaration is stale.
+
+## Why
+
+`"phase": "porting"` is a record of open work, not a softer severity: the day a new venue is chosen
+the source is still in the old venue's template, and a page count under the wrong template says
+nothing about the new limit. While the phase is declared, every `pdf/*`, `format/*`, `anonymity/*`
+and `tex/*` venue rule stays silent for that paper. A declaration that silences rules must not be
+able to stay on after its reason is gone: once the class line is the venue's, this rule fires, and
+the only way to be quiet again is to drop the phase — which turns the format rules back on.
+
+## Examples
+
+Failing — `paperlint.json`:
+
+```json
+{
+  "cycles": [
+    {
+      "id": "blind-2027",
+      "venue": { "kind": "preset", "extends": "./blindconf.jsonc" },
+      "opened": "2026-09-09",
+      "phase": "porting"
+    }
+  ]
+}
+```
+
+where the preset's `template` is `\documentclass[conference,compsoc]{IEEEtran}`, and `paper.tex`
+begins with that very line:
+
+```text
+papers/my-paper/paper.tex
+  1:1  error  the \documentclass is already `\documentclass[conference,compsoc]{IEEEtran}`, which
+              BlindConf requires, and the cycle «blind-2027» still declares "phase": "porting" — the
+              port is done: remove the phase, so the venue's format rules judge this paper again
+              cycle/port-done
+```
+
+Passing:
+
+- the same paper with the phase removed (or `"phase": "prepared"`);
+- a cycle still porting whose `paper.tex` still has the old venue's class line — the port is open
+  work, as declared;
+- a preset that names no `template`: there is nothing to compare, as for `tex/template`;
+- a paper whose `paperlint.json` has no `cycles`.
+
+## Options / preset fields
+
+No rule options. It reads the preset's `template`, the field [`tex/template`](../tex/template.md)
+reads, and compares the way that rule does.
+
+## What it does not check
+
+- Whether the port is complete beyond the class line — the page limit, the fonts, the sections. Those
+  are the format rules' to judge, and they judge again the moment the phase is dropped.
+- A cycle declared `porting` whose class line is still the old one: that is the state the phase
+  describes.
+- A `porting` cycle that has already sent a PDF — [`cycle/stage`](stage.md) reports that on the
+  scorecard.
+
+## How to fix
+
+Remove `"phase": "porting"` from the current cycle in `paperlint.json`, then run `paperlint lint`
+and `paperlint build`: the venue's format rules judge the paper again, and what they report is the
+rest of the port.

package/docs/rules/cycle/record.md

@@ -0,0 +1,152 @@
+# cycle/record
+
+**Level:** error · **Reads:** the paper's `paperlint.json` (`cycles`) and the venue presets it names ·
+**Reported on:** the first line of the paper's `PIPELINE-STATUS.md`
+
+## What it catches
+
+The paper's `cycles` — its attempts at venues, one entry each, oldest first — do not describe one
+consistent history:
+
+- **one source's deadlines are out of order.** The order a venue's deadlines keep is
+
+  ```text
+  registration ≤ submission ≤ resubmission < notification < camera-ready
+  ```
+
+  and it is checked within each source: the portal's readings among themselves, the call's among
+  themselves, the overrides among themselves. A call's abstract day after its own paper day is a
+  date typed wrong or an AoE day miscounted.
+
+- **a portal reading the venue's preset already carries.** A cycle whose venue is a preset derives
+  the portal's readings from it (`presets/msr.jsonc` carries MSR's); the same reading typed into the
+  paper is a second copy, and it goes stale the day paperlint updates the preset.
+
+The structural problems of the record — a bare date where an instant is needed, two open cycles, an
+open cycle that is not the last, two cycles with one id, one deadline in two entries, two readings
+from one source, an override without its reason or evidence, an unknown key anywhere in the record
+— are refused earlier, by `paperlint lint` itself before any rule runs, with one line naming the
+file, the place and the problem, and exit code 2, the same way an unknown key in `paperlint.json` is
+refused. This rule judges what the record parses with.
+
+## Why
+
+A deadline is the one fact in the record whose error costs the attempt. The record keeps what each
+page said — the portal, which refuses the upload, and the call, which only announces — with where and
+when it was read, and the **earlier** reading binds unless a human override says otherwise. That the
+portal and the call disagree is expected and is not a finding: at MSR 2027 the portal's "submissions
+must be completed by" falls at 04:00 UTC on the call's _abstract_ day, four days before the call's
+_paper_ day, and keeping both is how the earlier one is seen. What is a finding is a source that
+contradicts itself, and a fact recorded in two places.
+
+## Examples
+
+Failing — `paperlint.json`, the call's own dates inverted:
+
+```json
+{
+  "cycles": [
+    {
+      "id": "conf-2027",
+      "venue": { "kind": "preset", "extends": "paperlint:acm-sigconf" },
+      "opened": "2026-09-09",
+      "deadlines": [
+        {
+          "what": "registration",
+          "observed": [
+            {
+              "at": "2026-10-25 AoE",
+              "source": "call",
+              "url": "https://conf.example/cfp",
+              "read": "2026-09-09"
+            }
+          ]
+        },
+        {
+          "what": "submission",
+          "observed": [
+            {
+              "at": "2026-10-23 AoE",
+              "source": "call",
+              "url": "https://conf.example/cfp",
+              "read": "2026-09-09"
+            }
+          ]
+        }
+      ]
+    }
+  ]
+}
+```
+
+```text
+papers/my-paper/PIPELINE-STATUS.md
+  1:1  error  paperlint.json, cycle «conf-2027»: the call's "registration" (2026-10-26T11:59:59Z) is
+              after its "submission" (2026-10-24T11:59:59Z) — a date typed wrong, or an AoE day
+              miscounted (write a call's date as "YYYY-MM-DD AoE" and paperlint converts it)
+              cycle/record
+```
+
+Failing — a cycle at `paperlint:msr` that copies the portal's reading the preset carries:
+
+```text
+  1:1  error  paperlint.json, cycle «msr-2027»: the "submission" deadline records a portal reading,
+              and the preset paperlint:msr carries the portal's reading of it (2026-10-20T04:00:00Z,
+              read 2026-10-05) — a second copy drifts when paperlint updates the preset: delete this
+              one (the call's reading and an override stay)  cycle/record
+```
+
+Passing:
+
+- the first record with the registration on `2026-10-20 AoE`;
+- a cycle at `paperlint:msr` recording the call's abstract day as `registration` (`2026-10-20 AoE`)
+  and its paper day as `submission` (`2026-10-23 AoE`): the preset's portal `submission`
+  (`2026-10-20T04:00:00Z`) is earlier than both, binds, and is not a contradiction;
+- a cycle with no `deadlines` at all;
+- a paper whose `paperlint.json` has no `cycles` (the flat form, `"extends": "paperlint:…"`).
+
+## Options / preset fields
+
+No rule options. One deadline entry:
+
+```jsonc
+{
+  "what": "submission", // registration (the call's abstract) · submission (the full paper) · resubmission · notification · camera-ready
+  "observed": [
+    {
+      "at": "2026-10-23 AoE", // or an instant with its zone: 2026-10-20T04:00:00Z
+      "source": "call", // or "portal"
+      "url": "https://conf.example/cfp",
+      "read": "2026-10-05", // the day the page was read
+    },
+  ],
+  // optional; wins over every reading
+  "override": {
+    "at": "2026-10-27T04:00:00Z",
+    "reason": "the chairs extended the deadline by mail",
+    "evidence": "mail/extension.eml",
+  },
+}
+```
+
+The preset field is `deadlines` in a venue preset: a list of readings `{ "what", "at", "source",
+"url", "read" }`, `at` in UTC. Shipped presets carry their portal's readings and are refreshed by a
+scheduled workflow in paperlint's repository; your own preset may carry readings the same way.
+
+## What it does not check
+
+- Whether a reading is still what the page says. The rule has no network and no clock; a shipped
+  preset's readings are re-read daily in paperlint's repository and reach you as a patch release.
+  A venue without a preset (`"kind": "named"`) is re-read by you.
+- Whether a deadline has passed, or how long is left.
+- A disagreement between sources — that is what the record holds; the earlier reading binds.
+- Whether an override's evidence exists — that is [`cycle/evidence`](evidence.md).
+- Whether the scorecard's stages name these cycles — that is [`cycle/stage`](stage.md).
+
+## How to fix
+
+Correct the date. For a deadline read from a call for papers, write it as the call prints it,
+`"YYYY-MM-DD AoE"`, and let paperlint do the arithmetic; for one read from a portal, write the instant
+the portal shows with its zone. Delete a portal reading the venue's preset already carries. A
+deadline the chairs moved by mail is an `override`, with the mail saved in the paper folder as its
+`evidence`.

package/docs/rules/cycle/stage.md

@@ -0,0 +1,85 @@
+# cycle/stage
+
+**Level:** error · **Reads:** the paper's `PIPELINE-STATUS.md` frontmatter (`stages`) and its
+`paperlint.json` (`cycles`) · **Reported on:** the frontmatter of `PIPELINE-STATUS.md`
+
+## What it catches
+
+With `cycles` declared in the paper's `paperlint.json`, a `stages` entry in the scorecard's
+frontmatter must say which attempt it belongs to, `cycle: <id>`, and that attempt must exist. Three
+things can be wrong:
+
+- a stage names no `cycle`;
+- a stage names a `cycle` no declared cycle has as its `id`;
+- a `submitted` or `camera-ready` stage belongs to a cycle whose `phase` is still `porting` — a PDF
+  was sent to the venue while the record says the source is still in the previous venue's template.
+
+Without `cycles` (the flat form) the rule is silent and `venue:` stays what it was.
+
+## Why
+
+A paper's attempts are recorded once, in `paperlint.json`; the scorecard's stages are the evidence
+— which PDF, how many bytes, when. A stage that names its cycle says which attempt the evidence
+belongs to, and the venue's name is then spelled once, in the preset, instead of as a free string
+retyped per stage (`REALM @ EMNLP 2026`, `AISec 2026 @ ACM CCS`, …). A stage whose cycle does not
+exist is evidence of nothing.
+
+The `porting` case is the other half of a declaration: `"phase": "porting"` silences the venue's
+format rules because the source is, by declaration, not yet in the venue's template. A PDF sent
+from such a cycle contradicts that declaration — either the port is done and the phase is stale, or
+the stage is wrong.
+
+## Examples
+
+Failing — `paperlint.json` declares one cycle, `open-2027`, and `PIPELINE-STATUS.md` has
+
+```yaml
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/a.pdf
+    bytes: 1
+---
+```
+
+```text
+papers/my-paper/PIPELINE-STATUS.md
+  1:1  error  the «submitted» stage (2026-07-22) names no `cycle` — this paper declares `cycles` in
+              paperlint.json, so each stage says which attempt it belongs to: `cycle: <id>`, one of
+              open-2027  cycle/stage
+```
+
+Passing:
+
+```yaml
+---
+stages:
+  - stage: submitted
+    cycle: open-2027
+    date: 2026-07-22
+    pdf: versions/a.pdf
+    bytes: 1
+---
+```
+
+Also passing: a paper without `cycles`, whatever its stages say.
+
+## Options / preset fields
+
+No rule options.
+
+## What it does not check
+
+- The PDF, its bytes, or the frozen source — [`paper/stages`](../../rules.md) and `paper/source`
+  do.
+- Whether a stage's `date` falls inside its cycle (after `opened`, before the outcome's `date`).
+- Whether a cycle without any `submitted` stage was in fact submitted; that is the portal's record
+  (`paperlint submission`), not the scorecard's.
+- The rest of the cycle record — [`cycle/record`](record.md) does.
+
+## How to fix
+
+Add `cycle: <id>` to each stage, with the id of the cycle the PDF was sent in. For a stage whose
+cycle is still `porting`: if the port is done, remove `"phase": "porting"` from the cycle
+([`cycle/port-done`](port-done.md) says when); if no PDF was sent, remove the stage.

package/docs/rules/format/page-limit.md

@@ -17,6 +17,19 @@ How the body is counted depends on the preset:
   appendices» excludes an appendix wherever it sits. What follows is not counted. The page the body
   ends on counts as body when body text stands above the heading there: a body that runs half a
   page past the limit is over the limit.
+- **With `"appendix_in_body": true` as well** (MSR: «All submissions must not exceed 10 pages for
+  the main text, inclusive of all figures, tables, appendices, etc. Two more pages containing only
+  references are permitted.»), the appendix is body wherever it sits, and banal's two counts are
+  replaced by the text's. The body is every page up to the references — that page too when body
+  text stands above the heading — and, when the appendix starts after the references, every page
+  from the appendix's to the last. The pages between hold only references, and they are what
+  `ref_pages_max` limits. An appendix before the references ends nothing.
+
+Why not banal's count for such a venue, measured on IEEEtran `[10pt,conference]` builds
+(2026-10-05): banal types a page whose first heading reads «Appendix» as bibliography, so ten pages
+of main text whose appendix stands before the references measured body 9, references 3 — a correct
+paper failed on its references; and an appendix after the references was counted as reference
+pages, so eleven pages of main text measured body 10, references 2 — an over-long paper passed.
 
 ## How it finds where the body ends
 
@@ -83,13 +96,17 @@ When a structural signal and the text disagree, the count is not made and the ru
 ## Options / preset fields
 
 No rule options. It reads, from the preset, `format.kinds.<kind>.body_pages_max`,
-`format.kinds.<kind>.ref_pages_max` and `format.body_ends_at`; from the paper's `paperlint.json`,
+`format.kinds.<kind>.ref_pages_max`, `format.body_ends_at` and `format.appendix_in_body` (which
+the schema accepts only beside `body_ends_at`); from the paper's `paperlint.json`,
 `kind`. A preset with no kinds, or a kind with no limits, has nothing to check.
 
 ## What it does not check
 
 - **An appendix before the references, without hyperref**, is counted as body: nothing structural
   says where it starts. With hyperref it ends the body.
+- **An appendix after the references, without hyperref, under `appendix_in_body`**, is counted
+  as reference pages: nothing structural says where it starts. `ref_pages_max` still limits the
+  pages after the references, so a long one is reported, as references.
 - **An appendix whose heading does not read «Appendix…»** (the standard classes print `A` and the
   title) is reported as `unclear` when hyperref anchors it.
 - **A bibliography that is not numbered and not linked by hyperref** has no confirmed heading and no

package/docs/rules/tex/template.md

@@ -5,8 +5,9 @@
 ## What it catches
 
 The paper is not set in the class its venue requires. The rule compares the `\documentclass` line
-of `paper.tex` with the preset's `template`: the class must be the same, and every option the
-template names must be there. The paper may add options of its own.
+of `paper.tex` with the preset's `template`: the class must be the same, every option the
+template names must be there, and no option the preset forbids (`template_forbids`) may be. The
+paper may add other options of its own.
 
 A source that keeps one file for several venues and picks the class behind a TeX switch has several
 `\documentclass` lines. The switch is not evaluated: each line is a candidate, the paper passes when
@@ -49,6 +50,16 @@ The first line reports:
 
 > the class option `compsoc` is missing: aidc requires `\documentclass[conference,compsoc]{IEEEtran}`
 
+Under a preset that forbids options — MSR: «LaTeX users must use \documentclass[10pt,conference]{IEEEtran}
+without including the compsoc or compsocconf options» (https://2027.msrconf.org/track/msr-2027-technical-papers):
+
+```latex
+\documentclass[10pt,conference,compsoc]{IEEEtran} % fails: compsoc is forbidden
+\documentclass[10pt,conference]{IEEEtran}         % passes
+```
+
+> the class option `compsoc` is forbidden: MSR requires `\documentclass[10pt,conference]{IEEEtran}` without `compsoc`, `compsocconf`
+
 ## Preset field
 
 No rule options. It reads `template`, merged along `extends` (a child's replaces its parent's):
@@ -60,15 +71,24 @@ No rule options. It reads `template`, merged along `extends` (a child's replaces
 A whole `\documentclass[…]{…}` line, or a bare class name (`"article"`), which requires the class
 and no option. A value that is neither is reported as a finding that names the preset file.
 
+```jsonc
+"template_forbids": ["compsoc", "compsocconf"]
+```
+
+Class options the venue's call forbids, each reported where the class line carries it. Read with the
+`template` of the same file, and only with it: the schema refuses it alone, and a child preset's
+`template` replaces both.
+
 ## What it does not check
 
-- Options a venue forbids (`review`, `anonymous` in a camera-ready): only that what the venue
-  requires is there.
+- An option a venue forbids that its preset does not list in `template_forbids` (`review` in a
+  camera-ready).
 - The version of the class file (#94).
 - A `\documentclass` inside a comment: the rule reads the parse tree, so it does not count.
 - Which branch of a TeX switch builds: with several class lines, one matching candidate is enough.
 
 ## How to fix
 
-Set the `\documentclass` line to the one the message quotes, keeping your own extra options. A new
+Set the `\documentclass` line to the one the message quotes, keeping your own extra options
+and dropping a forbidden one. A new
 paper made with `paperlint new <name> --venue <preset>` already has it.

package/docs/rules/tex/venue-leftover.md

@@ -57,10 +57,23 @@ No rule options. It reads every shipped preset's `name` and `aliases`, collected
 A name the paper's own chain also declares (two workshops of one parent conference) is never
 reported.
 
+```jsonc
+"mentions": "with-year"
+```
+
+A venue whose name is also a common acronym counts only with a year beside the name: under
+`paperlint:msr`, «First written for MSR 2027.», «MSR'27» and «MSR~2027» are reported, and
+«Manual Speech Recognition (MSR)», «Microsoft Research (MSR)» or «MSR, in 2027» are not. Any
+whole-word use counted for MSR at first, and an accepted ACSAC paper that defines «MSR» for itself
+drew six warnings. Per preset, not hard-coded: a name that only a venue uses (`AgenticDev`) stays
+reported with or without a year.
+
 ## What it does not check
 
 - A venue no shipped preset describes.
 - A name split by markup (`\textbf{AI}Sec`).
+- A `with-year` venue named without a year («submitted to MSR»): the rule cannot tell it from the
+  acronym.
 
 ## How to fix