paperlint 3.2.0 → 4.1.0

package/skills/pc-panel-review/SKILL.md

@@ -4,7 +4,7 @@ description: Use when asking "what would the program committee decide?" / "simul
 allowed-tools: [Read, Write, Grep, Glob, Bash, WebSearch, WebFetch, Agent, Skill]
 ---
 
-<!-- vigiles:sha256:9622701a349ea249 compiled from skills/pc-panel-review/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:b9feb099347291ff compiled from skills/pc-panel-review/SKILL.md.spec.ts -->
 
 # pc-panel-review — model the whole PC, not one reviewer
 
@@ -15,17 +15,6 @@ allowed-tools: [Read, Write, Grep, Glob, Bash, WebSearch, WebFetch, Agent, Skill
 > single-lens spot-check (formerly the standalone `venue-review-sim` skill). Reach for Venue-fit mode or
 > `paper-adversarial-review` for a fast spot-check; run the full panel (this) for the decision.
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs pc-panel-review <paper-dir>
-```
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 The Venue-fit mode gives ONE reviewer's fit score; `paper-adversarial-review` gives ONE defect hunt.
 A real decision is made by **2–4 reviewers with different priorities + a meta-review** that weighs
 consensus over any single voice. This skill runs that. The payoff over a single review: a **must-fix
@@ -61,8 +50,7 @@ prose-only read can.
    (proven: ~88% accept on a paper the human reader found exhausting). These two artifacts are the
    panel's only legitimate source for the readability/structure signal.
    *(Scorecard: this gate is row **`panel`**, and it declares **`structure`** (tighten-paper) + **`writing`**
-   (grade-paper-writing) as its required inputs — `pipeline-check.mjs` reports `panel` marked done while
-   either input is missing or newer than it.)*
+   (grade-paper-writing) as its required inputs.)*
 3. **Pick 3 (or 4) reviewer lenses** that a real PC for THIS venue would field. Menu — choose by fit:
    - **Methods/stats skeptic** — sample size, construct validity, multiple comparisons, overclaims,
      whether the CIs support the claims.
@@ -145,38 +133,6 @@ the claim falsifiable: *TEXT* invites "then write it", and *IMMOVABLE* invites "
 🔴 **A deadline is a constraint on how much you rework, never an argument for the current form.** If
 the author invokes it against a TEXT prong, that is the failure this section exists to catch.
 
-**Enforced** by `../paper-pipeline/scripts/pipeline-check.mjs` → `ceiling-unplanned`: a ceiling recorded
-in the scorecard whose prongs carry none of the three labels is a finding.
-
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record pc-panel-review <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record pc-panel-review <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `<count>` is the number of **consensus** must-fixes (flagged by ≥2 independent
-reviewers, not the union of everything anyone said), `<report-path>` is the meta-review. Add
-`--blocking` when the chair's decision is reject.
-**ABSTAINED** — `blocked`: the panel never ran because its required inputs (the persona stall
-inventory, the structural verdict) do not exist. `no-witness`: the panel ran and reached no
-consensus must-fix.
-
-🔴 **THIS IS THE SKILL THE DELETION OF `PASS` WAS WRITTEN FOR.** Five model reviewers from one
-vendor agreeing was being recorded as an acquittal — and correlated agreement between instances of
-one model is not independent evidence of anything. There is now no constructor that can say it.
-"Accept with no must-fix" is `ABSTAINED no-witness`: the panel produced no finding, which is a fact
-about the panel and not a fact about the paper.
-
-🔴 **The `blocked` row is the one that matters most here.** A blocked panel and a panel nobody
-launched read identically in prose, and on 2026-08-04 a status line said the panel was running when
-it had never been launched at all. Record the block; do not leave the check silent.
-
-Venue-fit mode records under the same skill name with the fit verdict and `<count>` 0 — it is one
-reviewer's spot-check, and its row should not be mistaken for the panel's decision.
-
 ## Rules
 - **Independence is non-negotiable** — never let reviewers see each other's reviews before the
   meta-review; shared context collapses the panel into one voice.

package/skills/pc-panel-review/SKILL.md.spec.ts

@@ -31,17 +31,6 @@ export default experimental_skill({
 > single-lens spot-check (formerly the standalone \`venue-review-sim\` skill). Reach for Venue-fit mode or
 > \`paper-adversarial-review\` for a fast spot-check; run the full panel (this) for the decision.
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs pc-panel-review <paper-dir>
-\`\`\`
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 The Venue-fit mode gives ONE reviewer's fit score; \`paper-adversarial-review\` gives ONE defect hunt.
 A real decision is made by **2–4 reviewers with different priorities + a meta-review** that weighs
 consensus over any single voice. This skill runs that. The payoff over a single review: a **must-fix
@@ -77,8 +66,7 @@ prose-only read can.
    (proven: ~88% accept on a paper the human reader found exhausting). These two artifacts are the
    panel's only legitimate source for the readability/structure signal.
    *(Scorecard: this gate is row **\`panel\`**, and it declares **\`structure\`** (tighten-paper) + **\`writing\`**
-   (grade-paper-writing) as its required inputs — \`pipeline-check.mjs\` reports \`panel\` marked done while
-   either input is missing or newer than it.)*
+   (grade-paper-writing) as its required inputs.)*
 3. **Pick 3 (or 4) reviewer lenses** that a real PC for THIS venue would field. Menu — choose by fit:
    - **Methods/stats skeptic** — sample size, construct validity, multiple comparisons, overclaims,
      whether the CIs support the claims.
@@ -161,38 +149,6 @@ the claim falsifiable: *TEXT* invites "then write it", and *IMMOVABLE* invites "
 🔴 **A deadline is a constraint on how much you rework, never an argument for the current form.** If
 the author invokes it against a TEXT prong, that is the failure this section exists to catch.
 
-**Enforced** by \`../paper-pipeline/scripts/pipeline-check.mjs\` → \`ceiling-unplanned\`: a ceiling recorded
-in the scorecard whose prongs carry none of the three labels is a finding.
-
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record pc-panel-review <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record pc-panel-review <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-**FINDING** — \`<count>\` is the number of **consensus** must-fixes (flagged by ≥2 independent
-reviewers, not the union of everything anyone said), \`<report-path>\` is the meta-review. Add
-\`--blocking\` when the chair's decision is reject.
-**ABSTAINED** — \`blocked\`: the panel never ran because its required inputs (the persona stall
-inventory, the structural verdict) do not exist. \`no-witness\`: the panel ran and reached no
-consensus must-fix.
-
-🔴 **THIS IS THE SKILL THE DELETION OF \`PASS\` WAS WRITTEN FOR.** Five model reviewers from one
-vendor agreeing was being recorded as an acquittal — and correlated agreement between instances of
-one model is not independent evidence of anything. There is now no constructor that can say it.
-"Accept with no must-fix" is \`ABSTAINED no-witness\`: the panel produced no finding, which is a fact
-about the panel and not a fact about the paper.
-
-🔴 **The \`blocked\` row is the one that matters most here.** A blocked panel and a panel nobody
-launched read identically in prose, and on 2026-08-04 a status line said the panel was running when
-it had never been launched at all. Record the block; do not leave the check silent.
-
-Venue-fit mode records under the same skill name with the fit verdict and \`<count>\` 0 — it is one
-reviewer's spot-check, and its row should not be mistaken for the panel's decision.
-
 ## Rules
 - **Independence is non-negotiable** — never let reviewers see each other's reviews before the
   meta-review; shared context collapses the panel into one voice.

package/skills/plan-paper-timeline/SKILL.md

@@ -1,24 +1,13 @@
 ---
 name: plan-paper-timeline
 description: Turn a venue's CFP dates into a scheduled, buffered plan on the Google Calendar — build the timeline backwards from the AoE submission deadline (harden + panel-review + artifact + anonymized host all land BEFORE it), create calendar events in the author's own time zone for submit-day / deadline / camera-ready, and apply the FILING-SPACING rule so multiple papers don't cluster in the month before a planned external filing. Use right after find-venue hands you real deadlines and before you start drafting. Compose with find-venue (deadline source) and submit-paper.
-allowed-tools: [Read, Write, Grep, Glob, mcp__Google_Calendar__list_events, mcp__Google_Calendar__search_events, mcp__Google_Calendar__create_event, mcp__Google_Calendar__update_event, Bash(node .claude/skills/paper-pipeline/scripts/announce.mjs:*), Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)]
+allowed-tools: [Read, Write, Grep, Glob, mcp__Google_Calendar__list_events, mcp__Google_Calendar__search_events, mcp__Google_Calendar__create_event, mcp__Google_Calendar__update_event]
 ---
 
-<!-- vigiles:sha256:faf0c175f1a0c5e5 compiled from skills/plan-paper-timeline/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:0f95e8225033cd72 compiled from skills/plan-paper-timeline/SKILL.md.spec.ts -->
 
 # plan-paper-timeline — CFP dates → a buffered, filing-aware schedule
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs plan-paper-timeline <paper-dir>
-```
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 A deadline is not a plan. This skill converts the four dates every CFP gives you — **submission (AoE),
 notification, camera-ready, event** — into calendar events with the buffers that actually keep a
 submission from slipping, and sequences *multiple* papers so the cadence reads as sustained acclaim,
@@ -58,7 +47,6 @@ institutional email has no expedite route** — no support queue jump, no "I'm o
 That is why `access` is scheduled in the first week rather than the last: it is the one item where the
 only remedy for being late is having started earlier.
 
-`pipeline-check.mjs` reports an `access` row still `☐` inside the moderation window as a finding, and
 `submit-paper` is hard-blocked on `access` being green.
 
 ## 1. Build the timeline backwards from the AoE deadline
@@ -142,28 +130,6 @@ When scheduling paper N against papers already on the calendar and a known/likel
   second, stronger publication lands in a later month on purpose.
 - Prefer a paper with an earlier, safely-past deadline over one that would pile onto the filing month.
 
-## 5. Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record plan-paper-timeline <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record plan-paper-timeline <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `<count>` slots have no buffer, or collide with another paper's pre-filing window;
-`<report-path>` is the plan. Add `--blocking` when the deadline cannot be met from here.
-**ABSTAINED** — `no-witness`: the backwards plan is on the calendar, `access` is green and no slot
-is tight. `input-missing`: `find-venue` has produced no dated deadline to plan against.
-
-This is the one skill whose blocking finding is a fact about the calendar rather than about the
-paper: portal moderation runs up to two weeks and an author with no institutional email has no
-expedite route, so one recorded today is still true tomorrow no matter how good the science gets.
-
-🔴 **There is no PASS**, so "the plan is on the calendar" is not storable here. Put the event ids in
-the `ABSTAINED` note — markdown is the source of truth and the calendar is its projection, and a row
-with neither is a claim about a calendar nobody opened.
-
 ## Scorecard rows this skill owns
 Two, and they fail differently — see `paper-pipeline/references/pipeline-status-template.md`:
 - **`access`** — *can you physically submit?* (§0). Account · profile ACTIVE since `<ISO>` · portal

package/skills/plan-paper-timeline/SKILL.md.spec.ts

@@ -19,23 +19,10 @@ export default experimental_skill({
     "mcp__Google_Calendar__search_events",
     "mcp__Google_Calendar__create_event",
     "mcp__Google_Calendar__update_event",
-    "Bash(node .claude/skills/paper-pipeline/scripts/announce.mjs:*)",
-    "Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)",
   ],
   body: `
 # plan-paper-timeline — CFP dates → a buffered, filing-aware schedule
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs plan-paper-timeline <paper-dir>
-\`\`\`
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 A deadline is not a plan. This skill converts the four dates every CFP gives you — **submission (AoE),
 notification, camera-ready, event** — into calendar events with the buffers that actually keep a
 submission from slipping, and sequences *multiple* papers so the cadence reads as sustained acclaim,
@@ -75,7 +62,6 @@ institutional email has no expedite route** — no support queue jump, no "I'm o
 That is why \`access\` is scheduled in the first week rather than the last: it is the one item where the
 only remedy for being late is having started earlier.
 
-\`pipeline-check.mjs\` reports an \`access\` row still \`☐\` inside the moderation window as a finding, and
 \`submit-paper\` is hard-blocked on \`access\` being green.
 
 ## 1. Build the timeline backwards from the AoE deadline
@@ -159,28 +145,6 @@ When scheduling paper N against papers already on the calendar and a known/likel
   second, stronger publication lands in a later month on purpose.
 - Prefer a paper with an earlier, safely-past deadline over one that would pile onto the filing month.
 
-## 5. Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record plan-paper-timeline <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record plan-paper-timeline <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-**FINDING** — \`<count>\` slots have no buffer, or collide with another paper's pre-filing window;
-\`<report-path>\` is the plan. Add \`--blocking\` when the deadline cannot be met from here.
-**ABSTAINED** — \`no-witness\`: the backwards plan is on the calendar, \`access\` is green and no slot
-is tight. \`input-missing\`: \`find-venue\` has produced no dated deadline to plan against.
-
-This is the one skill whose blocking finding is a fact about the calendar rather than about the
-paper: portal moderation runs up to two weeks and an author with no institutional email has no
-expedite route, so one recorded today is still true tomorrow no matter how good the science gets.
-
-🔴 **There is no PASS**, so "the plan is on the calendar" is not storable here. Put the event ids in
-the \`ABSTAINED\` note — markdown is the source of truth and the calendar is its projection, and a row
-with neither is a claim about a calendar nobody opened.
-
 ## Scorecard rows this skill owns
 Two, and they fail differently — see \`paper-pipeline/references/pipeline-status-template.md\`:
 - **\`access\`** — *can you physically submit?* (§0). Account · profile ACTIVE since \`<ISO>\` · portal

package/skills/render-paper/SKILL.md

@@ -4,21 +4,10 @@ description: Compile a LaTeX paper (ACM/IEEE/arXiv) to PDF and render its pages
 allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, SendUserFile]
 ---
 
-<!-- vigiles:sha256:0943963cae95f8f1 compiled from skills/render-paper/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:5e2ee8850c098375 compiled from skills/render-paper/SKILL.md.spec.ts -->
 
 # render-paper — .tex → PDF → readable page PNGs
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs render-paper <paper-dir>
-```
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 Turns a LaTeX source into (a) a compiled PDF and (b) per-page PNG images crisp enough to read
 the font on a phone. Encodes the exact toolchain and the failures already debugged, so it works
 first try.
@@ -45,7 +34,7 @@ That list was replaced on 2026-08-03; nothing about the toolchain below changed.
   by `kpsewhich` against the files each profile names. The last line it prints is `bin: <dir>` —
   put that directory first on PATH before calling `pdflatex` or `check-render.sh` by hand.
 
-  🔴 The package list lives in the venue profiles (`submit-paper/references/venues/*.jsonc`, the
+  🔴 The package list lives in the venue profiles (`presets/*.jsonc` in the package, the
   `tex` block; `tex-base.jsonc` for every paper) and nowhere else. A new venue that needs a new
   package gets it there — never in a script, never here. A TeX Live without `libertine` builds an
   acmart paper GREEN in Computer Modern; that is why the files are checked, not the exit code.
@@ -130,30 +119,5 @@ python3 -c "import fitz; d=fitz.open('paper.pdf'); \
 - Send the PNGs with `SendUserFile` (`display: render`) so the user can read on phone; caption what
   changed since the last render. Send the PDF too (`display: attach`) if they want the file.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record render-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record render-paper <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-🔴 **There is no PASS**, not even here, where the temptation is strongest — an exit code of 0 from
-`check-render.sh` means the parser found no defect in the log, which is not the same as the page
-being right, and the delivered-PDF check exists because that difference once put `7 x 10^13` on
-page one.
-
-**FINDING** — `check-render.sh` exited non-zero; `<count>` is Overfull boxes plus undefined
-refs/citations and `<report-path>` is the log. Always `--blocking`: every one of these is a fact
-about the artifact, never a matter of taste.
-**ABSTAINED** — `no-witness`: it compiled and the log parser found nothing. `input-missing`: there
-is no `.tex` to compile. `crashed`: no LaTeX toolchain on this machine, which must never be read
-as a clean render.
-
-It runs twenty times a day, so the ledger fills with rows, and that is fine: each row pins a page count
-to a specific set of paper bytes, which is exactly what the `tighten-paper` structure gate is blocked
-on and what a remembered page count keeps getting wrong.
-
 ## Compose with
 - `paper-adversarial-review` / `pc-panel-review` (incl. its venue-fit mode) — review the rendered draft.

package/skills/render-paper/SKILL.md.spec.ts

@@ -14,17 +14,6 @@ export default experimental_skill({
   body: `
 # render-paper — .tex → PDF → readable page PNGs
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs render-paper <paper-dir>
-\`\`\`
-
-An advisory pass cannot be observed failing — silence is both its error state and its normal
-state — so starting is an event, and events get written down.
-
 Turns a LaTeX source into (a) a compiled PDF and (b) per-page PNG images crisp enough to read
 the font on a phone. Encodes the exact toolchain and the failures already debugged, so it works
 first try.
@@ -51,7 +40,7 @@ That list was replaced on 2026-08-03; nothing about the toolchain below changed.
   by \`kpsewhich\` against the files each profile names. The last line it prints is \`bin: <dir>\` —
   put that directory first on PATH before calling \`pdflatex\` or \`check-render.sh\` by hand.
 
-  🔴 The package list lives in the venue profiles (\`submit-paper/references/venues/*.jsonc\`, the
+  🔴 The package list lives in the venue profiles (\`presets/*.jsonc\` in the package, the
   \`tex\` block; \`tex-base.jsonc\` for every paper) and nowhere else. A new venue that needs a new
   package gets it there — never in a script, never here. A TeX Live without \`libertine\` builds an
   acmart paper GREEN in Computer Modern; that is why the files are checked, not the exit code.
@@ -136,31 +125,6 @@ python3 -c "import fitz; d=fitz.open('paper.pdf'); \\
 - Send the PNGs with \`SendUserFile\` (\`display: render\`) so the user can read on phone; caption what
   changed since the last render. Send the PDF too (\`display: attach\`) if they want the file.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record render-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record render-paper <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-🔴 **There is no PASS**, not even here, where the temptation is strongest — an exit code of 0 from
-\`check-render.sh\` means the parser found no defect in the log, which is not the same as the page
-being right, and the delivered-PDF check exists because that difference once put \`7 x 10^13\` on
-page one.
-
-**FINDING** — \`check-render.sh\` exited non-zero; \`<count>\` is Overfull boxes plus undefined
-refs/citations and \`<report-path>\` is the log. Always \`--blocking\`: every one of these is a fact
-about the artifact, never a matter of taste.
-**ABSTAINED** — \`no-witness\`: it compiled and the log parser found nothing. \`input-missing\`: there
-is no \`.tex\` to compile. \`crashed\`: no LaTeX toolchain on this machine, which must never be read
-as a clean render.
-
-It runs twenty times a day, so the ledger fills with rows, and that is fine: each row pins a page count
-to a specific set of paper bytes, which is exactly what the \`tighten-paper\` structure gate is blocked
-on and what a remembered page count keeps getting wrong.
-
 ## Compose with
 - \`paper-adversarial-review\` / \`pc-panel-review\` (incl. its venue-fit mode) — review the rendered draft.`,
 });

package/skills/render-paper/check-render.sh

@@ -25,75 +25,28 @@ set -uo pipefail
 # check — that is, the defect the guard was set up for comes back together with a green report.
 # A broken `import` in JS fails loudly; here we have to fail on our own.
 #
-# A ladder of THREE candidates, because the directory MOVED (12.09): `venues/` is now carried by the
-# `paperlint` package, and at the consumer's old location there is a symlink into it.
-# The order "the declared package → a sibling inside the package → the consumer's directory" is
-# deliberate: the package must win silently. It only gets loud when there is NOT A SINGLE ONE.
-# 🔴 THE SCRIPT'S OWN DIRECTORY — TAKEN ABSOLUTE AND BEFORE ANY `cd` (12.09.2026, evening).
-# Found by a RED HARNESS, `gates.harness.mjs`, not by proofreading, and it is my own regression from
-# the same day: below, the script does `cd "$DIR"` into the paper directory, and the venues resolve
-# stood AFTER that `cd`. So `git rev-parse --show-toplevel` was already running in the fixture's
-# temporary directory, the root was not found, and the build honestly stopped — on a test that had
-# been passing until then.
+# TWO candidates, in this order: the package by its NAME, from the current directory (a consumer's
+# installed paperlint wins), then the package THIS script ships in. Loud only when neither holds it.
 #
-# ⚠️ The previous version was wrong THE SAME WAY, but silently: it did not check the result and built
-# the PDF without the reference guard. That is, going red is not a new breakage but a manifestation
-# of an old one; still, a test that was green yesterday and is red today is mine to fix.
-#
-# The neighbouring `build.sh` already carries this same lesson in a comment ("The script directory is
-# taken ONCE and ABSOLUTE, before cd") — CI failed on it there on 30.08. A second instance of the same
-# class in a file right next door.
+# 🔴 THE SCRIPT'S OWN DIRECTORY IS TAKEN ABSOLUTE AND BEFORE ANY `cd`: below, the script `cd`s into
+# the paper directory, and a lookup after that would start from the paper, not from here.
 SELF_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
 
 resolve_venues() {
-  local root pkg
-  # Three sources for the root, from the most explicit to the most reliable. The last one is the
-  # SCRIPT's location (`.claude/skills/render-paper/` ⇒ three levels up), and it is the only one that
-  # depends neither on the current directory nor on whether the caller sits inside a git tree.
-  # ⚠️ THE PARENTHESES ARE MANDATORY, and the harness caught this a minute after I wrote the line
-  # without them. In bash `A || B && C` parses as `(A || B) && C`, so on a SUCCESSFUL `git rev-parse`
-  # the `pwd` ran as well, and the substitution returned TWO lines — the repository root plus the
-  # current directory. By hand from a directory outside git this did not reproduce: there git failed,
-  # and only one branch ran.
-  # ⚠️ THE LAST RUNG SEARCHES, IT DOES NOT COUNT LEVELS. `cd "$SELF_DIR/../../.."` used to stand here
-  # — correct for `.claude/skills/render-paper/` (three levels to the root) and silently wrong after
-  # the skill moved into the package, where it lies in `skills/render-paper/` (two): the climb
-  # overshot ABOVE the repository, and rung 2 looked for venues in someone else's directory. Climbing
-  # up to the directory that holds `.claude` does not depend on the depth.
-  local probe="$SELF_DIR" fallback=""
-  while [ "$probe" != "/" ]; do
-    if [ -d "$probe/.claude" ]; then fallback="$probe"; break; fi
-    probe=$(dirname "$probe")
-  done
-  root="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || printf '%s' "$fallback")}"
-
-  # 1) the package, if it already carries venues/ (after step 5)
-  pkg=$(node -e 'try{process.stdout.write(require.resolve("paperlint/venues/paper-guards.tex"))}catch{}' 2>/dev/null || true)
+  local pkg own
+  # 1) the package by its name. `node -e` resolves from the current directory.
+  pkg=$(node -e 'try{process.stdout.write(require.resolve("paperlint/presets/tex/paper-guards.tex"))}catch{}' 2>/dev/null || true)
   if [ -n "$pkg" ] && [ -f "$pkg" ]; then
     dirname "$pkg"
     return 0
   fi
 
-  # 2) THE SIBLING SKILL, from THIS script's directory. Added 12.09 together with the move of
-  # `submit-paper` into the package, and it is the only one of the three that works in BOTH worlds at
-  # once:
-  #   • package checkout   `skills/render-paper/..` → `skills/submit-paper/references/venues`
-  #   • consumer           `.claude/skills/render-paper/..` → `.claude/skills/submit-paper/...`
-  #     (both directories are symlinks into the package, `-f` goes through them, and `cd`+`pwd`
-  #     leaves the logical path)
-  # Rung 1 depends on cwd (`node -e` resolves from the current directory), rung 3 depends on the
-  # consumer's root having been found at all. This one depends on neither — exactly the anchor whose
-  # absence had `gates.harness.mjs` red on 12.09.
-  local sibling="$SELF_DIR/../submit-paper/references/venues"
-  if [ -f "$sibling/paper-guards.tex" ]; then
-    (cd "$sibling" && pwd)
-    return 0
-  fi
-
-  # 3) the skill directory in the consumer — for a consumer that mounted the skills differently
-  local local_dir="$root/.claude/skills/submit-paper/references/venues"
-  if [ -f "$local_dir/paper-guards.tex" ]; then
-    printf '%s\n' "$local_dir"
+  # 2) the package this script is part of: `skills/render-paper/` → `presets/tex/`. `cd -P` follows
+  # the symlinks a consumer's `.claude/skills/render-paper` is made of, so `../..` is the PACKAGE's
+  # root, not the consumer's `.claude/`. Depends neither on the cwd nor on a git tree.
+  own="$(cd -P "$SELF_DIR" && pwd)/../../presets/tex"
+  if [ -f "$own/paper-guards.tex" ]; then
+    (cd "$own" && pwd)
     return 0
   fi
 
@@ -107,8 +60,8 @@ if [ "${1:-}" = "--print-venues" ]; then
     printf '%s\n' "$VD"
     exit 0
   fi
-  echo "✗ paper-guards.tex not found: not under the package name paperlint, not beside the script" >&2
-  echo "  (skills/submit-paper/references/venues), not at the consumer (.claude/skills/submit-paper/references/venues)." >&2
+  echo "✗ paper-guards.tex not found: not under the package name paperlint (paperlint/presets/tex)," >&2
+  echo "  not in the package this script ships in (../../presets/tex from it)." >&2
   echo "  Building the paper without it is not allowed: \\input{paper-guards} will not fail, it will vanish silently," >&2
   echo "  and the PDF will be built WITHOUT the check for dangling \\ref and \\cite." >&2
   exit 2
@@ -135,7 +88,7 @@ if [ "${NO_COMPILE:-0}" != "1" ] && [ -f "$BASE.tex" ]; then
   # Two passes: overfull boxes surface on every pass; a second pass settles refs
   # so Reference/Citation-undefined warnings are accurate.
   # 🔴 TEXINPUTS is mandatory, and that was found by a crash on 26.08. Papers pull in their venue's
-  # numbers via `\input{<venue>}`, and the file lies in `.claude/skills/submit-paper/references/venues/`.
+  # numbers via `\input{<venue>}`, and the file lies in the package's `presets/tex/`.
   # Without that path the build fails with `File \`agenticdev.tex' not found` — and the `|| true`
   # below swallows it, after which the script reads a log of UNKNOWN origin and reports on it. That
   # is, compiling this paper here silently did not work, and it only became visible once a pass

package/skills/render-paper/render-paper.harness.mjs

@@ -68,34 +68,11 @@ await checkSkill("render-paper");
   const run = (args, opts = {}) =>
     spawnSync("bash", [CHECK, ...args], { encoding: "utf8", ...opts });
 
-  // First half — on TODAY's tree, resolution must succeed IF THERE IS ANYTHING TO
-  // resolve.
-  //
-  // 🔴 THERE USED TO BE AN UNCONDITIONAL `assert.equal(status, 0)` HERE, AND THE MOVE BROKE IT —
-  // for a real reason, not by accident. It relied on the SURROUNDING tree: while the skill lived
-  // at the consumer, the second rung of the ladder won
-  // (`.claude/skills/submit-paper/references/venues/`). The package checkout has neither that nor
-  // the first rung — `venues/` arrives together with `submit-paper`, which hasn't moved yet. So
-  // the assertion wasn't checking resolution, it was checking for the presence of an unrelated
-  // directory nearby.
-  //
-  // The form now is: resolution must succeed IF AND ONLY IF at least one candidate exists on
-  // disk. This is still a real assertion — it fails if a candidate exists and the script didn't
-  // find it — but it stops requiring the existence of something this repository doesn't have yet.
-  // The absence of both candidates gets PRINTED, not swallowed: "the check found nothing to
-  // check" and "the check passed" have to look different.
+  // First half — on this tree, resolution must succeed IF AND ONLY IF a candidate exists on disk:
+  // the package's own `presets/tex/`. The absence of it is PRINTED, not swallowed: "the check found
+  // nothing to check" and "the check passed" have to look different.
   const candidates = [
-    // rung 1 — the package
-    join(HERE, "..", "..", "venues", "paper-guards.tex"),
-    // rung 2 — the skill directory at the consumer
-    join(
-      HERE,
-      "..",
-      "submit-paper",
-      "references",
-      "venues",
-      "paper-guards.tex",
-    ),
+    join(HERE, "..", "..", "presets", "tex", "paper-guards.tex"),
   ].filter((c) => existsSync(c));
 
   const ok = run(["--print-venues"]);
@@ -108,9 +85,8 @@ await checkSkill("render-paper");
         `silent success this whole block was written to catch.`,
     );
     console.log(
-      `  --print-venues: NOT VERIFIED on the live tree — paper-guards.tex is absent from both ` +
-        `the package (venues/) and next to it (submit-paper/references/venues/). It arrives with ` +
-        `\`submit-paper\`; until then only the fixtures below hold this half.`,
+      `  --print-venues: NOT VERIFIED on the live tree — paper-guards.tex is absent from the ` +
+        `package's presets/tex/; only the fixtures below hold this half.`,
     );
   } else {
     assert.equal(
@@ -159,18 +135,9 @@ await checkSkill("render-paper");
   // When the file is NOWHERE, the script must exit with code 2 and say why. A silent success here
   // is exactly the defect the whole ladder was written for.
   //
-  // 🔴 RUN AGAINST A COPY OF THE SCRIPT, AND THIS IS NOT A TEST WORKAROUND, IT'S A CONSEQUENCE OF
-  // THE MOVE (09-12, wave ③). Before `submit-paper` moved, "nowhere" was reproduced by an empty
-  // consumer root: both former rungs looked outward (the package name from cwd · `.claude/` under
-  // the root), and an empty directory found nothing at either. Now the script has a rung anchored
-  // to ITS OWN directory (`$SELF_DIR/../submit-paper/references/venues`) — added for
-  // cwd-independence — so as long as the script sits inside the package, venues next to it exist
-  // ALWAYS, and "nowhere" can no longer be reached through the environment. The only honest way to
-  // demonstrate that state is to move the script itself out of the package. The property being
-  // checked is otherwise identical, word for word: nothing resolved ⇒ exit 2 + the name of the
-  // missing file. ⚠️ What this form no longer checks: that an empty consumer root won't make the
-  // script lie — and it shouldn't, because such a root is now legitimately shadowed by the copy in
-  // the package.
+  // 🔴 RUN AGAINST A COPY OF THE SCRIPT. Inside the package its second rung (the package it ships
+  // in) always holds the file, so "nowhere" is reachable only by moving the script out of the
+  // package: nothing resolved ⇒ exit 2 + the name of the missing file.
   const empty = realpathSync(mkdtempSync(join(tmpdir(), "venues-none-")));
   const lonely = join(empty, "check-render.sh");
   copyFileSync(CHECK, lonely);
@@ -190,30 +157,21 @@ await checkSkill("render-paper");
     "the failure message must name the missing file",
   );
 
-  // Third half — the ORDER of the rungs. Not cosmetic: on the day of the move, both rungs will be
-  // true at once, and the package has to win, otherwise the consumer silently keeps building with
-  // their old copy. Plant BOTH candidates and see which one is chosen.
+  // Third half — the ORDER of the rungs. The package the consumer installed, found by its name,
+  // must win over the copy this script ships in; otherwise a consumer silently builds with a stale
+  // copy. Plant a package by name beside the real script and see which one is chosen.
   const both = realpathSync(mkdtempSync(join(tmpdir(), "venues-both-")));
-  const pkgVenues = join(both, "node_modules", "paperlint", "venues");
-  const skillVenues = join(
-    both,
-    ".claude",
-    "skills",
-    "submit-paper",
-    "references",
-    "venues",
-  );
-  for (const d of [pkgVenues, skillVenues]) mkdirSync(d, { recursive: true });
+  const pkgVenues = join(both, "node_modules", "paperlint", "presets", "tex");
+  mkdirSync(pkgVenues, { recursive: true });
   writeFileSync(
     join(both, "node_modules", "paperlint", "package.json"),
     JSON.stringify({
       name: "paperlint",
       version: "0.0.0",
-      exports: { "./venues/*": "./venues/*" },
+      exports: { "./*": "./*" },
     }),
   );
   writeFileSync(join(pkgVenues, "paper-guards.tex"), "% from package\n");
-  writeFileSync(join(skillVenues, "paper-guards.tex"), "% from skill dir\n");
   const race = run(["--print-venues"], {
     cwd: both,
     env: { ...process.env, CLAUDE_PROJECT_DIR: both },
@@ -226,7 +184,7 @@ await checkSkill("render-paper");
   assert.equal(
     race.stdout.trim(),
     pkgVenues,
-    "with both candidates present, the PACKAGE wins, not the skill directory",
+    "with both candidates present, the INSTALLED package wins, not the copy the script ships in",
   );
 }
 
@@ -276,7 +234,7 @@ await checkSkill("render-paper");
     );
     assert.match(
       build,
-      /require\.resolve\("paperlint\/venues\/paper-guards\.tex"\)/,
+      /require\.resolve\("paperlint\/presets\/tex\/paper-guards\.tex"\)/,
       `${where}: the ladder's first rung (the package) must remain`,
     );
     assert.match(