paperlint 2.0.0

package/fixtures/build-e2e/unbalanced/paper.tex

@@ -0,0 +1,28 @@
+% A two-column acmart paper whose last page comes out UNBALANCED. Measured 2026-09-24 on TeX Live
+% 2023: the last page ends at 621.5 / 264.8 pt. paperlint build does not touch that (it no longer judges
+% layout); the e2e checks the build leaves it as TeX set it, and that the optional lint rule
+% pdf/last-page-balance reports it once a consumer turns the rule on.
+% Tuned by length: one section fewer leaves the right column nearly empty, one more pushes the
+% bibliography onto a third page. Change the text and re-measure before trusting the numbers above.
+\documentclass[sigconf,nonacm]{acmart}
+\input{paper-guards}
+\newcommand{\sentence}{Balancing the columns of the last page is a requirement of the publisher, and
+  the class option that promises it does nothing, because it calls the balancing macro from the
+  second column. }
+\newcommand{\para}{\sentence\sentence\sentence\sentence\sentence\sentence}
+\begin{document}
+\title{A fixture whose last page is unbalanced}
+\author{A. Author}
+\affiliation{\institution{X University}\city{Almaty}\country{Kazakhstan}}
+\maketitle
+\section{Part 1}\para
+\section{Part 2}\para
+\section{Part 3}\para
+\section{Part 4}\para
+\section{Part 5}\para
+\section{Part 6}\para
+\section{Part 7}\para
+\nocite{*}
+\bibliographystyle{ACM-Reference-Format}
+\bibliography{refs}
+\end{document}

package/fixtures/build-e2e/unbalanced/refs.bib

@@ -0,0 +1,269 @@
+@article{ref01,
+  author  = {Author01, Alice and Writer01, Bob},
+  title   = {A study of balanced columns, part 1},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1991},
+  volume  = {1},
+  pages   = {10--19}
+}
+
+@article{ref02,
+  author  = {Author02, Alice and Writer02, Bob},
+  title   = {A study of balanced columns, part 2},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1992},
+  volume  = {2},
+  pages   = {20--29}
+}
+
+@article{ref03,
+  author  = {Author03, Alice and Writer03, Bob},
+  title   = {A study of balanced columns, part 3},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1993},
+  volume  = {3},
+  pages   = {30--39}
+}
+
+@article{ref04,
+  author  = {Author04, Alice and Writer04, Bob},
+  title   = {A study of balanced columns, part 4},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1994},
+  volume  = {4},
+  pages   = {40--49}
+}
+
+@article{ref05,
+  author  = {Author05, Alice and Writer05, Bob},
+  title   = {A study of balanced columns, part 5},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1995},
+  volume  = {5},
+  pages   = {50--59}
+}
+
+@article{ref06,
+  author  = {Author06, Alice and Writer06, Bob},
+  title   = {A study of balanced columns, part 6},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1996},
+  volume  = {6},
+  pages   = {60--69}
+}
+
+@article{ref07,
+  author  = {Author07, Alice and Writer07, Bob},
+  title   = {A study of balanced columns, part 7},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1997},
+  volume  = {7},
+  pages   = {70--79}
+}
+
+@article{ref08,
+  author  = {Author08, Alice and Writer08, Bob},
+  title   = {A study of balanced columns, part 8},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1998},
+  volume  = {8},
+  pages   = {80--89}
+}
+
+@article{ref09,
+  author  = {Author09, Alice and Writer09, Bob},
+  title   = {A study of balanced columns, part 9},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {1999},
+  volume  = {9},
+  pages   = {90--99}
+}
+
+@article{ref10,
+  author  = {Author10, Alice and Writer10, Bob},
+  title   = {A study of balanced columns, part 10},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2000},
+  volume  = {10},
+  pages   = {100--109}
+}
+
+@article{ref11,
+  author  = {Author11, Alice and Writer11, Bob},
+  title   = {A study of balanced columns, part 11},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2001},
+  volume  = {11},
+  pages   = {110--119}
+}
+
+@article{ref12,
+  author  = {Author12, Alice and Writer12, Bob},
+  title   = {A study of balanced columns, part 12},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2002},
+  volume  = {12},
+  pages   = {120--129}
+}
+
+@article{ref13,
+  author  = {Author13, Alice and Writer13, Bob},
+  title   = {A study of balanced columns, part 13},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2003},
+  volume  = {13},
+  pages   = {130--139}
+}
+
+@article{ref14,
+  author  = {Author14, Alice and Writer14, Bob},
+  title   = {A study of balanced columns, part 14},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2004},
+  volume  = {14},
+  pages   = {140--149}
+}
+
+@article{ref15,
+  author  = {Author15, Alice and Writer15, Bob},
+  title   = {A study of balanced columns, part 15},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2005},
+  volume  = {15},
+  pages   = {150--159}
+}
+
+@article{ref16,
+  author  = {Author16, Alice and Writer16, Bob},
+  title   = {A study of balanced columns, part 16},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2006},
+  volume  = {16},
+  pages   = {160--169}
+}
+
+@article{ref17,
+  author  = {Author17, Alice and Writer17, Bob},
+  title   = {A study of balanced columns, part 17},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2007},
+  volume  = {17},
+  pages   = {170--179}
+}
+
+@article{ref18,
+  author  = {Author18, Alice and Writer18, Bob},
+  title   = {A study of balanced columns, part 18},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2008},
+  volume  = {18},
+  pages   = {180--189}
+}
+
+@article{ref19,
+  author  = {Author19, Alice and Writer19, Bob},
+  title   = {A study of balanced columns, part 19},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2009},
+  volume  = {19},
+  pages   = {190--199}
+}
+
+@article{ref20,
+  author  = {Author20, Alice and Writer20, Bob},
+  title   = {A study of balanced columns, part 20},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2010},
+  volume  = {20},
+  pages   = {200--209}
+}
+
+@article{ref21,
+  author  = {Author21, Alice and Writer21, Bob},
+  title   = {A study of balanced columns, part 21},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2011},
+  volume  = {21},
+  pages   = {210--219}
+}
+
+@article{ref22,
+  author  = {Author22, Alice and Writer22, Bob},
+  title   = {A study of balanced columns, part 22},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2012},
+  volume  = {22},
+  pages   = {220--229}
+}
+
+@article{ref23,
+  author  = {Author23, Alice and Writer23, Bob},
+  title   = {A study of balanced columns, part 23},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2013},
+  volume  = {23},
+  pages   = {230--239}
+}
+
+@article{ref24,
+  author  = {Author24, Alice and Writer24, Bob},
+  title   = {A study of balanced columns, part 24},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2014},
+  volume  = {24},
+  pages   = {240--249}
+}
+
+@article{ref25,
+  author  = {Author25, Alice and Writer25, Bob},
+  title   = {A study of balanced columns, part 25},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2015},
+  volume  = {25},
+  pages   = {250--259}
+}
+
+@article{ref26,
+  author  = {Author26, Alice and Writer26, Bob},
+  title   = {A study of balanced columns, part 26},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2016},
+  volume  = {26},
+  pages   = {260--269}
+}
+
+@article{ref27,
+  author  = {Author27, Alice and Writer27, Bob},
+  title   = {A study of balanced columns, part 27},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2017},
+  volume  = {27},
+  pages   = {270--279}
+}
+
+@article{ref28,
+  author  = {Author28, Alice and Writer28, Bob},
+  title   = {A study of balanced columns, part 28},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2018},
+  volume  = {28},
+  pages   = {280--289}
+}
+
+@article{ref29,
+  author  = {Author29, Alice and Writer29, Bob},
+  title   = {A study of balanced columns, part 29},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2019},
+  volume  = {29},
+  pages   = {290--299}
+}
+
+@article{ref30,
+  author  = {Author30, Alice and Writer30, Bob},
+  title   = {A study of balanced columns, part 30},
+  journal = {Journal of Reproducible Typesetting},
+  year    = {2020},
+  volume  = {30},
+  pages   = {300--309}
+}

package/fixtures/install-path-literals/clean.fixture.mjs

@@ -0,0 +1,3 @@
+// Clean: every answer to *where* comes from the port.
+import { consumerRoot } from "../../skills/paper-pipeline/scripts/consumer.mjs";
+export const LEDGER = (env, cwd) => `${consumerRoot({ env, cwd })}/runs.jsonl`;

package/fixtures/install-path-literals/clean.md

@@ -0,0 +1,15 @@
+---
+name: planted-clean
+allowed-tools: [Bash(node ${CLAUDE_SKILL_DIR}/../paper-pipeline/scripts/ledger.mjs:*)]
+---
+
+# A skill that asks the port where it is
+
+Record the verdict:
+
+```
+node ${CLAUDE_SKILL_DIR}/../paper-pipeline/scripts/ledger.mjs record planted . FINDING 1 report.md
+```
+
+Paths inside the repository, such as `skills/paper-pipeline/scripts/consumer.mjs`, are not
+install-specific and must stay quiet: they are the same in every channel.

package/fixtures/install-path-literals/defect.fixture.mjs

@@ -0,0 +1,3 @@
+// Planted: a shipped module betting on one channel, in both literal forms.
+export const LEDGER = "node_modules/research-paper-pipeline/runs.jsonl";
+export const skill = (n) => `.claude/skills/${n}/SKILL.md`;

package/fixtures/install-path-literals/defect.md

@@ -0,0 +1,14 @@
+---
+name: planted-defect
+allowed-tools: [Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)]
+---
+
+# A skill that bets on one delivery channel
+
+Record the verdict:
+
+```
+node .claude/skills/paper-pipeline/scripts/ledger.mjs record planted . FINDING 1 report.md
+```
+
+The module lives at `node_modules/research-paper-pipeline/skills/paper-pipeline/scripts/consumer.mjs`.

package/fixtures/latex-language/clean.tex

@@ -0,0 +1,50 @@
+% Fixture for the LaTeX language: one document carrying every construct the projection has
+% to survive -- preamble, abstract environment, sections, inline and display math, an opaque
+% macro family, a `\texttt{}` span, a float with a caption, a footnote, comments, and a
+% bibliography macro. The projection must stay character-for-character the same LENGTH as
+% this file, and no rule may fire on it.
+%
+% Author note, deliberately carrying a promise phrase: the appendix will be released once
+% the table below is redrawn. It sits in a comment, so it is not prose and not a finding.
+\documentclass[sigconf,screen]{acmart}
+\usepackage{natbib}
+\newcommand{\tool}{Widget}
+\settopmatter{printfolios=true}
+\begin{document}
+\title{A short and honest paper}
+\author{Anonymous Author}
+
+\begin{abstract}
+We measured one thing and report it plainly. The number is small and we say so.
+\end{abstract}
+
+\section{Introduction}
+\label{sec:intro}
+We wanted to know whether a cheap check finds the same defects as an expensive one.
+The flag \texttt{shadow-budget} caps the run, and the cap is $n = 10$ files in total.
+We cover 95\% of the cases we set out to cover, at a cost of \$5 per run.
+
+\begin{table}[t]
+\caption{Deterministic audit of ten files, reported exactly as they were counted.}
+\label{tab:results}
+\begin{tabular}{lrr}
+check & found & missed \\
+cheap & 4 & 6 \\
+expensive & 9 & 1 \\
+\end{tabular}
+\end{table}
+
+\section{Method}
+We took ten files, ran both checks, and wrote down what each one said.\footnote{Both
+runs used the same machine and the same working directory, in that order.}
+
+\[
+  E = m c^2
+\]
+
+\section{Results}
+We found four of the ten with the cheap check and nine with the expensive one, and we
+report both numbers together with the files behind them \cite{someone2020}.
+
+\bibliography{refs}
+\end{document}

package/fixtures/latex-language/defect.tex

@@ -0,0 +1,52 @@
+% Fixture for the LaTeX language, defect half. Identical in shape to `clean.tex`, with the
+% promise moved OUT of the comment and INTO the table caption -- one finding, no more, so that
+% what fires is unambiguous.
+%
+% The caption is the load-bearing part. Prose inside `\caption{}` used to be invisible to
+% every rule reading a `.tex` file, because it was blanked TWICE over: once as an opaque
+% macro argument and once again as part of the surrounding float. A measurement on the
+% source corpus (three papers, 2026-09-06) put the cost at 11 blocks / 384 words of author
+% English that no check could see; 253 of those words agree with `texcount`'s own
+% "Words outside text" count for one of the three.
+\documentclass[sigconf,screen]{acmart}
+\usepackage{natbib}
+\newcommand{\tool}{Widget}
+\settopmatter{printfolios=true}
+\begin{document}
+\title{A short and honest paper}
+\author{Anonymous Author}
+
+\begin{abstract}
+We measured one thing and report it plainly. The number is small and we say so.
+\end{abstract}
+
+\section{Introduction}
+\label{sec:intro}
+We wanted to know whether a cheap check finds the same defects as an expensive one.
+The flag \texttt{shadow-budget} caps the run, and the cap is $n = 10$ files in total.
+We cover 95\% of the cases we set out to cover, at a cost of \$5 per run.
+
+\begin{table}[t]
+\caption{Deterministic audit of ten files. The full table will be released later.}
+\label{tab:results}
+\begin{tabular}{lrr}
+check & found & missed \\
+cheap & 4 & 6 \\
+expensive & 9 & 1 \\
+\end{tabular}
+\end{table}
+
+\section{Method}
+We took ten files, ran both checks, and wrote down what each one said.\footnote{Both
+runs used the same machine and the same working directory, in that order.}
+
+\[
+  E = m c^2
+\]
+
+\section{Results}
+We found four of the ten with the cheap check and nine with the expensive one, and we
+report both numbers together with the files behind them \cite{someone2020}.
+
+\bibliography{refs}
+\end{document}

package/fixtures/paper-research-question/comment-only/PIPELINE-STATUS.md

@@ -0,0 +1,9 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS

package/fixtures/paper-research-question/comment-only/paper.tex

@@ -0,0 +1,7 @@
+\section{Introduction}
+% TODO: state the research question — this is a LaTeX COMMENT.
+% The rule reads RAW text and today does not tell it apart from the paper, so here it STAYS
+% SILENT. The hole is named in the rule's header and measured: on the live corpus there are
+% zero such cases, so it is latent. The fixture keeps it visible — the first real case turns
+% up and the assertion below has to be rewritten deliberately, not discovered after the fact.
+Body text of the paper, in which no question is stated.

package/fixtures/paper-research-question/declared-not-in-paper/PIPELINE-STATUS.md

@@ -0,0 +1,10 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+researchQuestion: "Does pruning reduce review cost?"
+---
+# PIPELINE-STATUS

package/fixtures/paper-research-question/declared-not-in-paper/paper.tex

@@ -0,0 +1,6 @@
+\section{Introduction}
+% This fixture is the one the predecessor could not express. The scorecard declares a question;
+% the paper does not carry it. And the words "research question" DO appear below — so the old
+% pattern `/\textbf{RQ|\bRQ[0-9]?\b|research question/i` matched and went silent on a paper that
+% states no question at all. Matching a phrase ABOUT the thing is not finding the thing.
+We leave the research question to future work.

package/fixtures/paper-research-question/draft/PIPELINE-STATUS.md

@@ -0,0 +1,6 @@
+---
+stages: []
+---
+# PIPELINE-STATUS
+
+A draft, never submitted anywhere.

package/fixtures/paper-research-question/draft/paper.tex

@@ -0,0 +1,2 @@
+\section{Introduction}
+A draft with no question. Nobody was asked to read it.

package/fixtures/paper-research-question/markdown-no-rq/PIPELINE-STATUS.md

@@ -0,0 +1,9 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS

package/fixtures/paper-research-question/markdown-no-rq/paper.md

@@ -0,0 +1,4 @@
+# Introduction
+
+The paper is written in markdown, not LaTeX — that happens in this corpus, and the rule must
+see it the same way. No question is stated here.

package/fixtures/paper-research-question/shipped-no-rq/PIPELINE-STATUS.md

@@ -0,0 +1,12 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/a.pdf
+    bytes: 1
+  - stage: camera-ready
+    date: 2026-08-29
+    pdf: versions/b.pdf
+    bytes: 2
+---
+# PIPELINE-STATUS

package/fixtures/paper-research-question/shipped-no-rq/paper.tex

@@ -0,0 +1,3 @@
+\section{Introduction}
+We study how agents behave and measure how many rules survive to the run.
+The question is named nowhere — neither by a macro nor in words.

package/fixtures/paper-research-question/shipped-with-rq/PIPELINE-STATUS.md

@@ -0,0 +1,10 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+researchQuestion: "does a rule written in prose survive to the run?"
+---
+# PIPELINE-STATUS

package/fixtures/paper-research-question/shipped-with-rq/paper.tex

@@ -0,0 +1,2 @@
+\section{Introduction}
+\textbf{RQ1:} does a rule written in prose survive to the run?

package/fixtures/paper-stages/authors-ran/PIPELINE-STATUS.md

@@ -0,0 +1,16 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS
+
+<!-- Evidence of a run lives in the PROSE of a note cell — it has no node of its own, so the
+     rule looks for the marker across the whole scorecard. The fixture repeats that shape on purpose. -->
+
+| id | what | with | ok | when | note |
+|---|---|---|---|---|---|
+| cites | any \cite edit | verify-citations | ☑ | 2026-08-24 | `bib-authors` ran: 27 entries, 1 discrepancy, fixed |

package/fixtures/paper-stages/marker-in-prose/PIPELINE-STATUS.md

@@ -0,0 +1,17 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/a.pdf
+    bytes: 1
+---
+# PIPELINE-STATUS
+
+Need to run `bib-authors` before camera-ready — never got round to it.
+
+Exactly the case GREP cannot tell apart from a record of a run: the marker is in the file,
+but the scorecard is empty. An intention read as a fact.
+
+| id | what | ok | note |
+|---|---|---|---|
+| build | pdf builds | ☑ | nothing to note |

package/fixtures/paper-stages/nofile/PIPELINE-STATUS.md

@@ -0,0 +1,8 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS

package/fixtures/paper-stages/noheader/PIPELINE-STATUS.md

@@ -0,0 +1 @@
+# PIPELINE-STATUS

package/fixtures/paper-stages/nothing/PIPELINE-STATUS.md

@@ -0,0 +1,3 @@
+# PIPELINE-STATUS
+
+A draft, never submitted anywhere.

package/fixtures/paper-stages/ok/PIPELINE-STATUS.md

@@ -0,0 +1,9 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    venue: A Venue 2026
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS

package/fixtures/paper-stages/stale/PIPELINE-STATUS.md

@@ -0,0 +1 @@
+# PIPELINE-STATUS

package/fixtures/paper-stages/twice/PIPELINE-STATUS.md

@@ -0,0 +1,14 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-08-06
+    venue: REALM @ EMNLP 2026
+    pdf: versions/2026-08-06-submitted.pdf
+    bytes: 100
+  - stage: submitted
+    date: 2026-10-24
+    venue: MSR 2027
+    pdf: versions/2026-10-24-submitted.pdf
+    bytes: 150
+---
+# PIPELINE-STATUS

package/fixtures/paper-stages/undeclared/PIPELINE-STATUS.md

@@ -0,0 +1,8 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 100
+---
+# PIPELINE-STATUS

package/fixtures/paper-stages/wrongsize/PIPELINE-STATUS.md

@@ -0,0 +1,8 @@
+---
+stages:
+  - stage: submitted
+    date: 2026-07-22
+    pdf: versions/2026-07-22-submitted.pdf
+    bytes: 352357
+---
+# PIPELINE-STATUS