paperlint 2.0.1 → 3.0.0

package/docs/configuration.md

@@ -1,103 +1,175 @@
 # Configuration reference
 
-One key in your `package.json`, written by `paperlint init`. It holds the facts only your repository can
-supply — nothing in it is guessable by a package that has never seen your corpus.
+paperlint reads one file name at two levels, `paperlint.json`, with one schema. Both files are
+optional: a project with its papers in `papers/` and no special wishes needs neither.
 
-The README carries the minimal version of this. Everything below is the full surface, moved out on
-2026-09-19.
+```
+paperlint.json               the PROJECT (optional): where the papers are, the project's rules,
+                             defaults for every paper
+papers/
+  my-paper/
+    paper.tex
+    PIPELINE-STATUS.md
+    paperlint.json           THIS PAPER: its venue preset, its kind, its own rules — `paperlint new` writes it
+venues/usenix-sec.jsonc      (optional, your own) a VENUE PRESET: format, page limits, TeX packages, rules
+```
+
+The shipped presets (`paperlint:<name>`) live in the package, under
+`skills/submit-paper/references/venues/`: `acm-sigconf`, `agenticdev`, `aisec`, `realm`.
+
+## The root `paperlint.json`
+
+It sits beside your `package.json`. Without it every setting has its default.
 
 ```json
 {
-  "paperlint": {
-    "papersDir": "papers",
-    "authorListCommand": "node scripts/bib-authors.mjs",
-    "typographyDebt": { "papers/my-paper": { "sectionSign": 12 } },
-    "docFields": { "read": { "values": ["full", "abstract", "none"] } },
-    "reviewSince": "2026-08-23",
-    "minFindings": 3,
-    "causeMarker": "Cause:",
-    "rules": [
-      {
-        "files": ["papers/agenticdev-2026/**"],
-        "rules": { "pdf/last-page-balance": ["error", { "tolerancePt": 120 }] }
-      }
-    ]
-  }
+  "papersDir": "docs/papers",
+  "extends": "paperlint:acm-sigconf",
+  "rules": [
+    {
+      "files": ["docs/papers/old-draft/**"],
+      "rules": { "paper/section-word": "off" }
+    }
+  ]
 }
 ```
 
-| key                 | required | what it is                                                                                |
-| ------------------- | -------- | ----------------------------------------------------------------------------------------- |
-| `papersDir`         | **yes**  | the directory your papers live in, relative to the file holding it. One string or a list. |
-| `structure`         | no       | which files every paper directory must contain — see below. `false` turns it off.         |
-| `authorListCommand` | no       | the command `paper/author-list` tells you to run when the check is missing                |
-| `typographyDebt`    | no       | per-paper allowance of existing typography findings, so the count can only go down        |
-| `docFields`         | no       | required front-matter fields in review files, and the values each may hold                |
-| `reviewSince`       | no       | only review files created on or after this date are checked                               |
-| `minFindings`       | no       | a review with fewer findings than this is not required to name causes                     |
-| `causeMarker`       | no       | the phrase a review uses to introduce a cause (default `Cause:`), in any language         |
-| `rules`             | no       | extra ESLint config blocks: turn optional rules on, change a rule's severity — see below  |
-
-The skill scripts read a few more keys of the same object — `ledger`, `scripts`, `timezone`,
-`contactEmail`, `citeChecks`, `triggerCases` — documented with the skills that use them.
-
-**Any other key is an error**, named in the message: `package.json → "paperlint":
-unknown key "typographyDept"`. A misspelt key would otherwise read as "not set", and the setting
-you meant would silently do nothing. The list of known keys is `SETTINGS_KEYS` in
-`lib/paper-config.mjs`.
-
-`papersDir` is required because the scope is the one thing that must not default: a default of `"."`
-turns every run into a green report over the whole checkout. `paperlint init` fills it by measuring —
-and when nothing on disk looks like a papers directory, it writes the documented default and says
-in the same breath that it is a guess.
-
-Until 2026-09-24 this field was called `papers`. The old name is not read as a fallback: `paperlint lint`,
-`paperlint init`, `paperlint doctor`, the ESLint helper and the edit guard all stop with
-`"papers" was renamed to "papersDir" in package.json → "paperlint"`. The two advisory
-hooks stay silent instead. The name is defined once, as `PAPERS_DIR_FIELD` in
-`lib/paper-config.mjs`.
-
-## Why the key lives in `package.json`
-
-Because of a count: the `package.json` key has **five** readers — the three editor hooks, the
-ESLint helper, the skill scripts — and a separate config file had **one**, the CLI. A hook cannot
-import code and cannot walk up a tree looking for a config; it can read a path it is able to name,
-and the one path it can always name is the project's `package.json`.
-
-`paperlint lint` looks for it in the current directory and then upwards, the way eslint and tsc find
-theirs, and prints which file it found. `--config <file>` overrides the search; the file has the
-same shape, with the settings under the `paperlint` key.
+| key         | default    | what it is                                                                                 |
+| ----------- | ---------- | ------------------------------------------------------------------------------------------ |
+| `papersDir` | `"papers"` | the directory your papers live in, relative to this file. One string or a list. Root only. |
+| `structure` | see below  | which files every paper directory must contain. `false` turns it off. Root only.           |
+| `rules`     | none       | rule overrides — see [below](#the-rules-key-turning-rules-on-and-off)                      |
+| `extends`   | none       | the venue preset for every paper that names none                                           |
+| `kind`      | none       | the kind of paper for every paper that names none                                          |
+| `pdf`       | none       | where the built PDF is, relative to each paper, when it is not `paper.pdf`                 |
+| `$comment`  | —          | a note for humans (JSON Schema's comment keyword); ignored                                 |
+
+The skill scripts read a few more root keys — `ledger`, `scripts`, `timezone`, `contactEmail`,
+`citeChecks`, `triggerCases` — documented with the skills that use them.
+
+**`paperlint lint` finds the file** by walking up from the current directory to the nearest
+`paperlint.json` that is not a paper's own (a paper's sits beside its `paper.tex`); if there is
+none, the project root is the nearest directory with a `package.json`. It prints which file it
+found. `--config <file>` names another file of the same shape.
+
+**No papers where `papersDir` points is an error**, not a clean run:
+
+```
+no papers in papers/ — create one with `npx paperlint new <name>`, or set "papersDir" in paperlint.json if your papers live elsewhere
+```
+
+`paperlint init` writes the root file only when something differs from the defaults: it measures
+where your papers are, and writes `{ "papersDir": … }` only when that is not `papers`. A
+`papersDir` already declared is kept, and nothing is measured or asked.
+
+**Under `papersDir`, only the files paperlint's own rules are written for are linted:**
+`PIPELINE-STATUS.md`, `paper.md`, `draft.md`, `paper.tex`, `reviews/*.md` and `siblings/*.md`.
+Everything else — a paper's `repro/` scripts, vendored JavaScript, data files — is never handed to
+ESLint, so it cannot fail the run. A file you name on the command line that is not one of these is
+refused by name. `node_modules/`, `.git/` and `<papers>/.template/` are skipped.
+
+## A paper's `paperlint.json`
+
+```json
+{
+  "extends": "paperlint:aisec",
+  "kind": "research",
+  "rules": { "pdf/body-size": "off" }
+}
+```
+
+The same keys as the root file, minus the project-only ones (`papersDir`, `structure` and the
+skills' keys), which are refused here by name. **It merges over the root file:** its `extends`,
+`kind` and `pdf` win; one it does not set comes from the root.
+
+| key        | what it is                                                                                                                                                                                 |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `extends`  | the venue preset the built PDF is judged against: `paperlint:<name>` (shipped) or `./path` / `../path` (your own, relative to this file) — [`rules.md`](rules.md#checks-against-the-venue) |
+| `kind`     | the kind of paper (`short`, `research`, …) whose page limit applies                                                                                                                        |
+| `pdf`      | where the built PDF is, relative to the paper, when it is not `paper.pdf`                                                                                                                  |
+| `rules`    | rule overrides for this paper alone — `{ "<rule>": "<severity>" }`, or blocks with globs relative to the paper                                                                             |
+| `$comment` | a note for humans; ignored                                                                                                                                                                 |
+
+`paperlint new` writes this file from the template (`templates/paper/paperlint.json`, or your
+`<papers>/.template/paperlint.json` if you keep one), with `"extends": null` — no venue chosen yet —
+and a `$comment` saying what goes there. Until `extends` names a preset (here or in the root file),
+`paperlint lint` gives that paper one warning, `pdf/measured`: "this paper names no venue preset
+yet … set "extends" in papers/my-paper/paperlint.json".
+
+**Any other key is an error**, in either file, named in the message: `paperlint.json: unknown key
+"papersdir"`. A misspelt key would otherwise read as "not set", and the setting you meant would
+silently do nothing. The key list is `SETTINGS_KEYS` in `lib/paper-config.mjs`.
+
+**Where a paper's rules come from, in order — a later one wins, rule by rule:** paperlint's own
+configuration → the preset chain's `rules`, from the root preset to the one the paper extends →
+the root `paperlint.json`'s `rules` → the paper's own `rules`. So a venue can turn a rule on, the
+project can change that for every paper, and one paper can still change it for itself. Only rules
+paperlint ships may be named, at every level.
+
+## Records in frontmatter, checked by shipped JSON Schemas
+
+Two kinds of file under a paper keep a record in their YAML frontmatter, and paperlint validates
+each against a JSON Schema it ships (`eslint-rules/*.schema.json`):
+
+- **a review** under `reviews/` (`review/frontmatter`, error) — its findings, each with a status and,
+  when open, the pipeline cause that let it through:
+
+  ```yaml
+  ---
+  findings:
+    - id: 1
+      status: open # open | fixed | wontfix
+      cause: missing-skill # skill-defect | missing-skill | hook | rule — required when open
+  ---
+  ```
+
+  A review with no `findings` key is not checked for findings.
+
+- **a sibling card** under `siblings/` (`sibling/frontmatter`, warn; `siblings/README.md` is the index,
+  not a card) — how much of the competing paper was actually read: `read: full | abstract | none`. A
+  card without it, or without frontmatter, is a finding.
 
 ## The `rules` key: turning rules on and off
 
-`rules` is a list of blocks in ESLint's own
-[flat-config shape](https://eslint.org/docs/latest/use/configure/configuration-files), limited to
-the three keys that make sense in JSON — `files`, `ignores` and `rules`. paperlint appends the blocks
-**after** its own configuration, so, as in ESLint, a later block wins: a block can turn on a rule
-that is off by default, or change the severity of one that is on.
+`rules` takes two shapes, in either file:
+
+- **`{ "<rule>": "<severity>" }`** — for every paper file in the file's scope: every paper in the
+  root file, that one paper in a paper's file. The simple form, with no glob to get wrong.
+- **a list of blocks** in ESLint's own
+  [flat-config shape](https://eslint.org/docs/latest/use/configure/configuration-files), limited to
+  the three keys that make sense in JSON — `files`, `ignores` and `rules` — for a rule across some
+  papers but not others.
+
+paperlint applies them **after** its own configuration, so, as in ESLint, a later one wins: they
+can turn on a rule that is off by default, or change the severity of one that is on.
 
 ```json
 "rules": [
   {
-    "files": ["papers/agenticdev-2026/**"],
-    "rules": { "pdf/last-page-balance": ["error", { "tolerancePt": 120 }] }
+    "files": ["papers/**"],
+    "rules": { "pdf/body-size": "off" }
   },
   {
     "files": ["papers/old-draft/**"],
-    "rules": { "paper/typography": "off" }
+    "rules": { "paper/section-word": "off" }
   }
 ]
 ```
 
-- **`files` and `ignores` are globs relative to the file that holds the settings** — the
-  directory of your `package.json` — exactly as ESLint resolves them relative to its config file,
+- **`files` and `ignores` are globs relative to the file that holds them** — the project root for
+  the root file, the paper for a paper's — exactly as ESLint resolves them relative to its config file,
   whatever directory you run `paperlint lint` from. A block without `files` applies to every linted file.
   A pattern ending in `/**` is the usual way to name one paper.
+- **Each rule reaches only the files it is written for.** A block with `"files": ["papers/**"]` and
+  `"rules": { "paper/source": "warn" }` turns `paper/source` on for every `PIPELINE-STATUS.md` under
+  `papers/`; `paper/section-word` in the same block lands on every `paper.md`, `draft.md` and
+  `paper.tex`. You do not need to know which file a rule reads: your `files` narrow where it runs,
+  never widen it. The [rule tables](rules.md) name each rule's file.
 - **A rule entry** is a severity (`"off"`, `"warn"`, `"error"`, or `0`/`1`/`2`), or a list whose
   first element is a severity and the rest are the rule's options.
 - **Only rules paperlint ships can be named** — the ones in [`docs/rules.md`](rules.md) and
   [`docs/optional-rules.md`](optional-rules.md). A rule id paperlint does not ship, a bad severity, a
-  `rules` that is not a list, or a block key other than `files`, `ignores` and `rules` stops the run
+  `rules` of another shape, or a block key other than `files`, `ignores` and `rules` stops the run
   with a message naming the exact key, before anything is linted.
 - **An optional rule you turned on must reach a paper.** If no linted `paper.tex` gets the rule —
   usually a `files` glob with a typo — `paperlint lint` fails and says so: a rule that never runs
@@ -116,7 +188,7 @@ and the real findings leave with it.
 
 ```json
 "structure": {
-  "markers":      ["PIPELINE-STATUS.md", "paper.tex", "paper.md", "venue.json"],
+  "markers":      ["PIPELINE-STATUS.md", "paper.tex", "paper.md", "paperlint.json"],
   "require":      ["PIPELINE-STATUS.md"],
   "requireOneOf": [["paper.tex", "paper.md"]],
   "ignore":       []
@@ -173,11 +245,12 @@ papers/my-paper
 
 The build does **not** judge the layout. A balanced last page, a page limit, the fonts a venue
 wants — those are verdicts about the finished PDF, and they belong to lint rules that can be
-turned on per venue, given a severity and suppressed with a reason. paperlint once searched for a
+turned on per venue, given a severity and suppressed with a reason: the `pdf/` venue rules
+([`rules.md`](rules.md#checks-against-the-venue)) and the optional `pdf/last-page-balance`. paperlint once searched for a
 `\balance` position itself and failed the build when none worked; that was removed on
 2026-09-24.
 
-The class and its options and the venue in `venue.json` are read from the paper and shown in the
+The class and its options and the venue in `paperlint.json` are read from the paper and shown in the
 plan; later steps decide from them whether they apply.
 
 **`paper.pdf` is deleted before anything runs**, for every targeted paper — before the TeX Live is
@@ -211,7 +284,7 @@ having run on it, because a missing build read as nothing to do.
 
 ⚠️ **A `build.sh` or `repro/build-submission.sh` in the paper directory is IGNORED.** Earlier
 versions ran it; `paperlint build` now says one line — `build.sh is ignored — paperlint builds the paper
-itself` — and builds the paper itself. The `buildScripts` key is ignored the same way.
+itself` — and builds the paper itself.
 Why: [#59](https://github.com/zernie/paperlint/issues/59).
 
 ## Using the rules from an existing ESLint config
@@ -225,7 +298,9 @@ the exact config the CLI uses, so the shortest path is:
 // eslint.config.mjs
 import { buildConfig } from "paperlint/bin/paperlint.mjs";
 import { texLanguage } from "paperlint/eslint-rules/latex-language.mjs";
-export default buildConfig({ minFindings: 3 }, texLanguage);
+export default buildConfig({}, texLanguage);
 ```
 
-Then point the CI action's `config` input at that file.
+That config is the whole config for your papers: it starts with a global ignore of every file its
+rules are not written for, so `eslint .` with it lints only the paper files. Do not spread it into a
+config that also lints your JavaScript — that code would be ignored.

package/docs/e2e.md

@@ -35,7 +35,7 @@ temporary tree, **under npm and under pnpm separately**, and drives the installe
 
 - the install itself finishes
 - `paperlint --help` answers with zero
-- `paperlint init` declares the papers directory in `package.json`
+- `paperlint init` takes the default papers directory and writes no `paperlint.json` for it
 - `paperlint init` finishes with zero — its doctor found no discrepancy
 - `paperlint init` wires the hooks into `.claude/settings.json` — the same commands `hooks.json`
   publishes, once each — and says they need `npm install` in a fresh clone; a second `init`

package/docs/install.md

@@ -14,21 +14,6 @@ npx paperlint init
 Two commands in one terminal, in this order: `init` links the skills and hooks to the copy in
 your project's `node_modules`, so it needs the install first.
 
-**Upgrading from `research-paper-pipeline`** (the package's name before 2.0.0):
-`npm rm research-paper-pipeline && npm i -D paperlint`, then `npx paperlint init`. It moves the
-`"research-paper-pipeline"` key in `package.json` to `"paperlint"`, and replaces the hook commands
-and skill links that pointed into the old package. Until then the old key is still read, with a
-warning.
-
-**Upgrading from 2.0.0**: 2.0.0 wrote hook commands that run `node_modules/paperlint/bin/rpp.mjs`,
-a file later versions do not ship, so those hooks stop running. `npx paperlint doctor` names them;
-`npx paperlint init` replaces them and keeps your own commands in the same matcher. The TeX Live
-and banal caches moved from `~/.cache/rpp/` to `~/.cache/paperlint/`, so `npx paperlint toolchain`
-downloads TeX Live once more (delete the old directory afterwards), and the environment variables
-are now `PAPERLINT_TEXLIVE_DIR`, `PAPERLINT_BANAL_DIR` and `PAPERLINT_CTAN_MIRROR` — the `RPP_*`
-names are no longer read. A leftover `rpp.json` is ignored; its settings belong under the
-`"paperlint"` key of `package.json`.
-
 The npm package carries everything: the `paperlint` command, the ESLint rules, the Claude Code skills
 and hooks, and the scripts the skills run. External programs are separate:
 
@@ -43,15 +28,18 @@ and hooks, and the scripts the skills run. External programs are separate:
 
 In order:
 
-1. **Finds the papers directory**, or asks for it. The project must have a `package.json`; without
-   one `init` stops and tells you to run `npm init -y` first.
-2. **Declares it once**, as the `paperlint` key in your `package.json`.
+1. **Finds the papers directory**, or asks for it when several directories look like one.
+2. **Declares it**, in a root `paperlint.json`, only when it is not the default `papers`. A project
+   on the defaults gets no config file at all.
 3. **Links each shipped skill** into `.claude/skills/<name>`, where Claude Code looks for skills.
 4. **Writes the hook commands** into `.claude/settings.json`, beside your own entries.
 5. **Offers a GitHub Actions workflow**, pinned to the release tag of the version you installed.
 6. **Offers a first paper** (`paperlint new`) if the papers directory has none.
-7. **Reports missing external programs** and the command that installs each. It installs nothing.
-8. **Runs `paperlint doctor`** and exits with its verdict.
+7. **Offers TeX Live** for `paperlint build` (`paperlint toolchain`, ~270 MB, ~3 min, once), with
+   the size in the question and NO as the default. Without a terminal it asks nothing and lists the
+   command as the next step. `paperlint lint` needs no TeX.
+8. **Reports missing external programs** and the command that installs each. It installs nothing.
+9. **Runs `paperlint doctor`** and exits with its verdict.
 
 It asks only what it cannot guess or what costs something. A human at a terminal is asked; an
 agent, CI or `--yes` takes the defaults, and `init` prints which default it took. An unanswered
@@ -61,23 +49,23 @@ question (Ctrl+D) also takes the default.
 
 | what                                                               | where                   | when                                                                                                                                                                              |
 | ------------------------------------------------------------------ | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| a `paperlint` key naming your papers directory                     | your `package.json`     | always                                                                                                                                                                            |
+| `{ "papersDir": … }` naming your papers directory                  | `paperlint.json`        | only when it is not the default `papers`                                                                                                                                          |
 | the three hook commands, merged in beside your own entries         | `.claude/settings.json` | by default. A human at a terminal is asked [Y/n]; an agent, CI or `--yes` gets YES; `--no-hooks` skips. Hand-wired under another spelling: nothing written, so nothing runs twice |
 | a GitHub Actions workflow, pinned to `@v<installed version>`       | `.github/workflows/`    | only if you say yes; it asks once, and only when a human is at a terminal (stdin and stdout, no `CI`, no `--yes`)                                                                 |
 | a first paper, via `paperlint new`                                 | `<papers>/<name>/`      | only when the papers directory holds none: asked of a human at a terminal, otherwise only with `--paper <name>`                                                                   |
 | one relative symlink per shipped skill, into the installed package | `.claude/skills/<name>` | always — except where that name is already taken (a directory, a file, a link elsewhere): that entry is left as it is and named in the report                                     |
 
-It installs no software and touches nothing else. Commit `.claude/settings.json` so every clone
+It installs no software you did not say yes to, and touches nothing else. Commit `.claude/settings.json` so every clone
 gets the hooks; the hook commands run files inside `node_modules`, so a fresh clone needs
 `npm install` first.
 
 ## Why it is shaped this way
 
-**One declaration, in `package.json`.** A hook cannot import code or walk up a tree looking for a
-config; it can only read a path it can spell, and the one it can always spell is
-`$CLAUDE_PROJECT_DIR/package.json`. That key is read by the three hooks, `eslint-rules/papers.mjs`,
-`lib/skill-trigger-cases.mjs` and `skills/paper-pipeline/scripts/consumer.mjs`; a separate
-config file would be read only by the CLI, so there is none.
+**One file, at the project root.** A hook cannot import code or walk up a tree looking for a
+config; it can only read a path it can spell, and `$CLAUDE_PROJECT_DIR/paperlint.json` is one. The
+same file is read by the CLI, the three hooks, `eslint-rules/papers.mjs`,
+`lib/skill-trigger-cases.mjs` and `skills/paper-pipeline/scripts/consumer.mjs`. It is optional:
+absent, every reader takes the same defaults.
 
 **Nothing runs at install time.** No postinstall script and no automatic TeX download. npm's rule
 is that _"the only valid use of install or preinstall scripts is for compilation"_; husky removed
@@ -110,9 +98,7 @@ resolve.
 nothing while guarding and says nothing while watching a directory that does not exist, so
 "installed" and "protecting you" look the same from outside. `doctor` prints the papers directory
 `paperlint lint` resolves and the one the hooks resolve, whether they match, whether the hooks are wired
-(once, twice, or not at all), and which external programs are missing. It also warns when the
-project still enables the old `research-paper-pipeline` plugin, because plugin plus settings would
-run every hook twice. A plugin installed at user scope is outside what it can read, and it says so.
+(once, twice, or not at all), and which external programs are missing.
 
 ### How comparable tools install
 
@@ -166,13 +152,12 @@ Neither `paperlint lint` nor any of the three hooks loads `@ast-grep` or `typesc
 
 ## Troubleshooting
 
-| symptom                                                      | cause and fix                                                                                                                                   |
-| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `init`: skills "nothing linked", or hooks that fail to start | the package is not installed in this project (`npx` ran a temporary copy). Run `npm i -D paperlint`, then `npx paperlint init` again            |
-| `init` stops: no `package.json`                              | run `npm init -y`, then `npx paperlint init` again                                                                                              |
-| `paperlint lint`: `nothing to lint`                          | no declaration was found. Run `npx paperlint init`, or pass the directory: `paperlint lint papers`                                              |
-| hooks fail with `Cannot find module` in a fresh clone        | the hook commands run files in `node_modules`: run `npm install`                                                                                |
-| `paperlint: not built`                                       | installed from git with `--ignore-scripts`, or a clone before building: run `npm run build` in the package                                      |
-| every hook runs twice                                        | the project still enables the old plugin. `init` and `doctor` print the uninstall command; also remove it from `enabledPlugins`                 |
-| a skill does not show up in Claude Code                      | its name was already taken in `.claude/skills/`. `init` names it and leaves it alone; rename or remove yours and run `npx paperlint init` again |
-| anything else                                                | `npx paperlint doctor` — it checks the setup and exits non-zero on anything miswired                                                            |
+| symptom                                                      | cause and fix                                                                                                                                                                          |
+| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `init`: skills "nothing linked", or hooks that fail to start | the package is not installed in this project (`npx` ran a temporary copy). Run `npm i -D paperlint`, then `npx paperlint init` again                                                   |
+| `paperlint lint`: `no papers in papers/`                     | there is no paper where `papersDir` points. Create one with `npx paperlint new <name>`, or set `"papersDir"` in `paperlint.json`                                                       |
+| hooks fail with `Cannot find module` in a fresh clone        | the hook commands run files in `node_modules`: run `npm install`                                                                                                                       |
+| `paperlint: not built`                                       | installed from git with `--ignore-scripts`, or a clone before building: run `npm run build` in the package                                                                             |
+| a skill does not show up in Claude Code                      | its name was already taken in `.claude/skills/`. `init` names it and leaves it alone; rename or remove yours and run `npx paperlint init` again                                        |
+| **every** shell command is blocked in Claude Code            | `paper-edit-guard` cannot parse the root `paperlint.json` (merge-conflict markers, a typo), and refuses rather than guess. Fix it with a normal file edit — file edits are not blocked |
+| anything else                                                | `npx paperlint doctor` — it checks the setup and exits non-zero on anything miswired                                                                                                   |

package/docs/optional-rules.md

@@ -1,8 +1,12 @@
 # Optional rules
 
-Some checks matter only for some venues. paperlint ships them **off**, and you turn them on for the
-papers that need them, in the `rules` setting of your `package.json`
-([`configuration.md`](configuration.md#the-rules-key-turning-rules-on-and-off)).
+Some checks matter only for some venues. paperlint ships them **off**. A venue preset that needs one
+turns it on for its papers (AgenticDev's turns on `pdf/last-page-balance`), and a paper can turn one
+on or off for itself in its own `paperlint.json`
+([`configuration.md`](configuration.md#a-papers-paperlintjson)). No glob is involved: a paper's
+rules apply to that paper. The root `paperlint.json` can turn it on for every paper, or for some
+with a block ([`configuration.md`](configuration.md#the-rules-key-turning-rules-on-and-off)); a
+paper's own file still has the last word for that paper.
 
 | rule                    | what it checks                                                | who needs it                                              |
 | ----------------------- | ------------------------------------------------------------- | --------------------------------------------------------- |
@@ -12,21 +16,18 @@ papers that need them, in the `rules` setting of your `package.json`
 
 ### Turning it on
 
+A paper that extends `paperlint:agenticdev` has it already, at 120 pt. For any other paper, in its
+`papers/my-paper/paperlint.json`:
+
 ```json
 {
-  "paperlint": {
-    "papersDir": "papers",
-    "rules": [
-      {
-        "files": ["papers/agenticdev-2026/**"],
-        "rules": { "pdf/last-page-balance": ["error", { "tolerancePt": 120 }] }
-      }
-    ]
-  }
+  "extends": "paperlint:aisec",
+  "kind": "research",
+  "rules": { "pdf/last-page-balance": ["error", { "tolerancePt": 120 }] }
 }
 ```
 
-`files` is relative to the `package.json`. `tolerancePt` is how far apart, in points, the two
+It applies to that paper alone; `"off"` there turns it off for a paper whose preset turns it on. `tolerancePt` is how far apart, in points, the two
 columns may end; it defaults to 120. On a real accepted paper the balanced build ended 2.7 pt apart
 and the one the publisher sent back 321.4 pt apart — nothing in between — so the default leaves a
 wide margin on both sides.
@@ -38,17 +39,18 @@ the result to `<paper>/_build/paper.facts.json` ([`configuration.md`](configurat
 and the rule judges that file, reporting on the paper's `paper.tex` at the `\documentclass` line.
 So: **build, then lint.**
 
-| the rule finds                                      | it says                                                                                                                       |
-| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| columns further apart than `tolerancePt`            | **the finding**, with both heights and how to fix it (below)                                                                  |
-| no `_build/paper.facts.json`                        | build the paper first                                                                                                         |
-| facts about a different PDF than the one on disk    | the facts are stale (their SHA-256 differs) — rebuild                                                                         |
-| facts whose PDF is gone (a failed build removes it) | rebuild                                                                                                                       |
-| a last page of a few lines                          | nothing — there is no layout to balance                                                                                       |
-| a review build with numbered lines                  | nothing — the numbers run down the whole page, so both columns measure full height, and balance is a camera-ready requirement |
-
-If you turn the rule on with a `files` glob that reaches no `paper.tex`, `paperlint lint` fails and says
-so, rather than reporting a clean run for a rule that never ran.
+| the rule finds                                      | it says                                                                                                                           |
+| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| columns further apart than `tolerancePt`            | **the finding**, with both heights and how to fix it (below)                                                                      |
+| no `_build/paper.facts.json`                        | build the paper first — unless the paper extends a venue preset: then `pdf/measured` already warns, once, and this rule is silent |
+| facts about a different PDF than the one on disk    | the facts are stale (their SHA-256 differs) — rebuild                                                                             |
+| facts whose PDF is gone (a failed build removes it) | rebuild                                                                                                                           |
+| a last page of a few lines                          | nothing — there is no layout to balance                                                                                           |
+| a review build with numbered lines                  | nothing — the numbers run down the whole page, so both columns measure full height, and balance is a camera-ready requirement     |
+
+If you turn the rule on — in a `paperlint.json` beside no `paper.tex`, or with a `files` glob in
+the root `paperlint.json` that reaches none — `paperlint lint` fails and says so, rather than reporting a clean
+run for a rule that never ran.
 
 ### Which venues need it