paperlint 3.2.0 → 4.0.0

package/skills/paper-pipeline/scripts/consumer.mjs

@@ -7,11 +7,9 @@
  *
  *   1. where is the consumer's repository root, now that walking `..` from here lands in
  *      `node_modules/` instead;
- *   2. where does the run ledger live, now that the directory next to this file is wiped by
- *      `npm ci`;
- *   3. was this file executed, or merely imported — a question whose usual answer stops
+ *   2. was this file executed, or merely imported — a question whose usual answer stops
  *      working the moment the file is reached through a symlink;
- *   4. by what path a SKILL'S PROSE names these scripts, so that a checker can tell an
+ *   3. by what path a SKILL'S PROSE names these scripts, so that a checker can tell an
  *      instruction that runs them from one that runs something else. See the fourth-carrier
  *      section at the bottom of this file.
  *
@@ -23,7 +21,7 @@
  *                                                paper-pipeline/scripts
  *
  * so every command a skill's prose already names — `node .claude/skills/paper-pipeline/scripts/
- * ledger.mjs …` — keeps working unchanged. That is the whole reason the symlink exists: the
+ * <script>.mjs …` — keeps working unchanged. That is the whole reason the symlink exists: the
  * first consumer names those paths 306 times across 129 files, almost all of it in the PROSE of
  * skills, which no refactor can rewrite.
  *
@@ -35,12 +33,11 @@
  *     process.cwd()     /…/<the consumer repository root>
  *
  * Node resolves the entry point to its realpath (`--preserve-symlinks-main` is off by default)
- * but leaves `argv[1]` as typed. Three consequences, each one a function here:
+ * but leaves `argv[1]` as typed. Two consequences, each one a function here:
  *
  *   🔴 `import.meta.url === \`file://${process.argv[1]}\`` — the main guard nine scripts in this
  *      directory used — is `false` through the symlink. NOT an error: the process exits 0 having
- *      done nothing. `ledger.mjs record …` would silently record nothing, `announce.mjs` would
- *      silently announce nothing, and every caller would read success. `isMain()` compares
+ *      done nothing, and every caller reads success. `isMain()` compares
  *      against the REALPATH of `argv[1]` instead, which is true through both routes.
  *
  *   🔴 `resolve(import.meta.dirname, "..", "..", "..", "..")` — the repository root, correct
@@ -48,30 +45,9 @@
  *      by `process.cwd()`, which is the consumer root because every one of those 306 invocations
  *      is `node .claude/skills/…` typed from the repository root. `consumerRoot()`.
  *
- *   🔴 `join(import.meta.dirname, "runs.jsonl")` — the ledger's default home — now points inside
- *      `node_modules`, which `npm ci` deletes. Appending there is SILENT DATA LOSS: the write
- *      succeeds, the rows are real, and they vanish at the next install with no error anywhere.
- *      `ledgerPath()` refuses to return that path at all.
- *
- * ── THE LEDGER, THREE RUNGS ─────────────────────────────────────────────────
- *   1. `PIPELINE_LEDGER` in the environment — always wins. This is what test harnesses set to
- *      keep fixture rows out of real history, so it must outrank a declaration on disk.
- *   2. `{ "ledger": "…" }` in the CONSUMER's root `paperlint.json`, read
- *      from `process.cwd()`, resolved relative to it.
- *   3. `runs.jsonl` beside this file — ONLY when this file is not inside `node_modules`, i.e.
- *      when the package is being developed in its own checkout. Inside `node_modules` with
- *      nothing declared, this THROWS.
- *
- * 🔴 WHY RUNG 3 THROWS RATHER THAN GUESSING. Every other candidate default is worse in the same
- * direction. Writing beside the file loses data at the next `npm ci`. Writing to
- * `<cwd>/runs.jsonl` puts an append-only journal at the top of someone's repository without
- * asking. Writing nowhere makes `record()` a no-op, which is the stored "nothing was wrong" this
- * ledger exists to abolish. A throw is the only one of the four that cannot be mistaken for
- * having worked — and it carries the cure, naming the key and the file to put it in.
- *
- * ⚠️ THE EXAMPLES HERE ARE DELIBERATELY GENERIC (`docs/pipeline-runs.jsonl`). The first
- * consumer's own directory names are absent by the same rule `papers.harness.mjs` part IV
- * enforces for `papers.mjs`: a package that spells out one user's private tree has one user.
+ * ⚠️ THE EXAMPLES HERE ARE DELIBERATELY GENERIC. The first consumer's own directory names are
+ * absent by the same rule `papers.harness.mjs` part IV enforces for `papers.mjs`: a package that
+ * spells out one user's private tree has one user.
  */
 import {
   existsSync,
@@ -246,68 +222,22 @@ function readlinkOr(entry, readlink) {
  * True when `dir` lies inside a `node_modules` directory.
  *
  * Segment-wise, not `includes("node_modules")`: a repository legitimately named
- * `my-node_modules-inspector` is not an installed package, and a substring test would refuse to
- * write its ledger. Cheap to get right, and the failure it prevents is a throw in someone's face.
+ * `my-node_modules-inspector` is not an installed package, and a substring test would refuse it.
+ * Cheap to get right, and the failure it prevents is a throw in someone's face.
  */
 export function insideNodeModules(dir) {
   return dir.split(sep).includes("node_modules");
 }
 
-/**
- * Where the run ledger lives. Three rungs; see the docblock.
- *
- * @param hereDir  the directory of the module that owns the ledger — pass `import.meta.dirname`.
- * @returns an absolute path. Never a path inside `node_modules`.
- */
-export function ledgerPath(
-  hereDir,
-  { env = process.env, cwd = process.cwd() } = {},
-) {
-  // Rung 1 — the environment. Deliberately first: harnesses redirect the ledger BEFORE importing
-  // it, and a declaration on disk that could override that would put fixture rows in real history.
-  if (env.PIPELINE_LEDGER) return resolve(env.PIPELINE_LEDGER);
-
-  // Rung 2 — the consumer's declaration.
-  const root = consumerRoot({ env, cwd });
-  const declared = settingsOf(consumerRoot({ env, cwd }))?.ledger;
-  // 🔴 `declared === undefined`, NOT `declared ?? default` — the same distinction `papersRoot()`
-  // makes and for the same reason: `"ledger": null` is a keystroke, not an absence, and reading
-  // it as "nothing was declared" would silently pick a different file than the one asked for.
-  if (declared !== undefined) {
-    if (typeof declared !== "string" || declared.length === 0)
-      throw new TypeError(
-        `${CONFIG_KEY}: "ledger" must be a non-empty string, got ${JSON.stringify(declared)}`,
-      );
-    return resolve(root, declared);
-  }
-
-  // Rung 3 — beside this file, but only in the package's own checkout.
-  if (insideNodeModules(hereDir))
-    throw new Error(
-      `${CONFIG_KEY}: no ledger location is declared, and the default (a file beside this ` +
-        `module) is inside node_modules, which \`npm ci\` deletes.\n` +
-        `Declare where the ledger lives, in ${join(root, CONFIG_FILE)}:\n` +
-        `  { "ledger": "docs/pipeline-runs.jsonl" }\n` +
-        `or set PIPELINE_LEDGER for a single run.\n` +
-        `This is thrown rather than defaulted on purpose: appending to a path under ` +
-        `node_modules succeeds, so the rows would look recorded right up until the next ` +
-        `install removed them, with no error at any point.`,
-    );
-  return join(hereDir, "runs.jsonl");
-}
-
 // ═════════════════════════════════════════════════════════════════════════════════════════════
-// THE FOURTH CARRIER — WHERE A SKILL'S PROSE NAMES THESE SCRIPTS
+// WHERE A SKILL'S PROSE NAMES THESE SCRIPTS
 //
-// `papersRoot()` answers "where does the consumer keep its papers"; `ledgerPath()` answers
-// "where does the run journal live"; `citeChecks` (read in `run-mechanical.mjs`) answers "where
-// are the consumer's own citation checkers". This answers the fourth: BY WHAT PATH does a skill
-// instruct the model to run `announce.mjs` and `ledger.mjs`.
+// `papersRoot()` answers "where does the consumer keep its papers". This answers: BY WHAT PATH
+// does a skill instruct the model to run this package's scripts.
 //
-// 🔴 IT IS A DIFFERENT KIND OF PATH FROM THE OTHER THREE, and the difference decides the API.
-// The other three are read by CODE and may be absolute. This one is compared against text a
-// human wrote inside a SKILL.md — `node .claude/skills/paper-pipeline/scripts/ledger.mjs record
-// …` — so it must stay relative to the consumer root and spelled with `/`, exactly as the prose
+// 🔴 IT IS A DIFFERENT KIND OF PATH, and the difference decides the API. `papersRoot()` is read by
+// CODE and may be absolute. This one is compared against text a human wrote inside a SKILL.md —
+// `node .claude/skills/paper-pipeline/scripts/<script>.mjs …` — so it must stay relative to the consumer root and spelled with `/`, exactly as the prose
 // spells it. Returning an absolute path here would make every `startsWith` test false and every
 // check that depends on it pass over an empty set.
 //
@@ -346,7 +276,7 @@ export function scriptsRoot({ env = process.env, cwd = process.cwd() } = {}) {
   const root = consumerRoot({ env, cwd });
   const declared = settingsOf(consumerRoot({ env, cwd }))?.scripts;
   // 🔴 `declared === undefined`, NOT `declared ?? DEFAULT` — the same distinction `papersRoot()`
-  // and `ledgerPath()` make, for the same reason: `"scripts": null` is a keystroke, not an
+  // makes, for the same reason: `"scripts": null` is a keystroke, not an
   // absence, and silently substituting the default for it hides a typo behind a working run.
   const rel = declared === undefined ? DEFAULT_SCRIPTS_ROOT : declared;
   if (typeof rel !== "string" || rel.length === 0)
@@ -385,12 +315,11 @@ export function scriptsRoot({ env = process.env, cwd = process.cwd() } = {}) {
 }
 
 // ═════════════════════════════════════════════════════════════════════════════════════════════
-// THE SIXTH CARRIER — WHICH WALL CLOCK THE CONSUMER SCHEDULES AGAINST
+// WHICH WALL CLOCK THE CONSUMER SCHEDULES AGAINST
 //
-// `papersRoot()` answers "where are the papers", `ledgerPath()` "where is the journal",
-// `citeChecks` "where are the consumer's citation checkers", `scriptsRoot()` "by what path does
-// prose name these scripts", `triggerCases` "where are the consumer's own trigger cases". This
-// answers the sixth: IN WHAT TIME ZONE does a deadline anchor get written.
+// `papersRoot()` answers "where are the papers", `scriptsRoot()` "by what path does prose name
+// these scripts", `triggerCases` "where are the consumer's own trigger cases". This answers: IN
+// WHAT TIME ZONE does a deadline anchor get written.
 //
 // 🔴 WHY IT IS A DECLARATION AND NOT A CONSTANT. A deadline is the one quantity in this pipeline
 // that is meaningless without a zone, and the zone belongs to the PERSON, not to the pipeline —
@@ -446,7 +375,7 @@ export function consumerTimezone({
 }
 
 // ═════════════════════════════════════════════════════════════════════════════════════════════
-// THE SEVENTH CARRIER — WHOM THE SCHOLARLY APIs SHOULD CONTACT
+// WHOM THE SCHOLARLY APIs SHOULD CONTACT
 //
 // Crossref and friends run a "polite pool": send a `mailto:` in the User-Agent and you get the
 // faster, more reliable tier, plus a warning by email instead of a silent block if your usage
@@ -485,13 +414,7 @@ export function consumerContactEmail({
   return declared;
 }
 
-/**
- * The individual script paths, derived from one root.
- *
- * 🔴 THE NAMES LIVE HERE, NOT IN THE CONSUMER — the same half that keeps `paperFiles()` honest.
- * `announce.mjs` and `ledger.mjs` are this package's contract; a consumer that spelled them out
- * itself would keep its copy of the list in step by hand, and a hand-kept list rots silently.
- */
+/** The prefix every prose path to this package's scripts starts with, derived from one root. */
 export function pipelineScripts(root) {
   // 🔴 ONE TRAILING SLASH, NOT THE ONE THAT WAS TYPED. `scriptsRoot()` returns the declaration
   // verbatim — it must, the value is compared against prose — so `"scripts": "tools/pipeline/"`
@@ -504,9 +427,5 @@ export function pipelineScripts(root) {
   return {
     /** What every prose path under this root starts with. Trailing slash, for `startsWith`. */
     prefix: `${base}/`,
-    /** Announces that a gate has started. */
-    announce: `${base}/announce.mjs`,
-    /** Appends the verdict row. */
-    ledger: `${base}/ledger.mjs`,
   };
 }

package/skills/paper-pipeline/scripts/generated-code.harness.mjs

@@ -317,9 +317,8 @@ function fixture({ scripts = {}, allow = null, bundle = {}, at = "repro" }) {
 }
 
 // ── 11. the ledger prints on a CLEAN run, and the header states the count ───────────────────────
-// The count matters beyond tidiness: `run-mechanical.mjs` reads this check in `flags` mode, where
-// it prefers a stated count and otherwise COUNTS OUTPUT LINES. The ledger is ~20 lines that are not
-// findings, so without the stated count a clean paper would be recorded as twenty findings.
+// The count matters beyond tidiness: the ledger is ~20 lines that are not findings, so a caller
+// counting output lines would read a clean paper as twenty findings.
 {
   const r = run(
     fixture({

package/skills/paper-pipeline/scripts/population-map.harness.mjs

@@ -11,7 +11,7 @@
  * The findings themselves are planted in `population-map.test.mjs` (vitest; until #52 a
  * self-test script this harness spawned). This file keeps what only the command shows: finding
  * paper.md and repro/populations.tsv, and `--flags-only` staying silent on a clean paper — the
- * wiring the CI step and `run-mechanical.mjs` actually invoke.
+ * wiring the CI step actually invokes.
  */
 import assert from "node:assert/strict";
 import { execFileSync } from "node:child_process";
@@ -107,8 +107,8 @@ const REG = [
 }
 
 // ── 4. KNOWN GAP, asserted so it stays visible ─────────────────────────────────────────
-// 🔴 A paper with NO repro/populations.tsv exits 0 in silence, and `run-mechanical.mjs` records
-// that silence as PASS for draft-paper. So a paper that never declared its populations scores
+// 🔴 A paper with NO repro/populations.tsv exits 0 in silence, which reads as a pass for
+// draft-paper. So a paper that never declared its populations scores
 // identically to one that declared them and tied every one. Absence is invisible again — the same
 // shape artifact-coverage.mjs was written to close for the released bundle.
 //

package/skills/paper-status/SKILL.md

@@ -4,21 +4,10 @@ description: Answer "what's the status of the paper?" in one pass — MEASURE wh
 allowed-tools: [Bash, Read, Grep, Glob]
 ---
 
-<!-- vigiles:sha256:51bc50b2485782e4 compiled from skills/paper-status/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:cdf5e1fcefdb916d compiled from skills/paper-status/SKILL.md.spec.ts -->
 
 # paper-status — state, measured before it is narrated
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs paper-status <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 author asks "what's the status there?" constantly, and the answer keeps coming from the wrong place: my
 memory of the session, which drifts, or a 200-line scorecard he cannot skim. Both fail the same way —
 **they narrate state instead of measuring it.**
@@ -49,18 +38,13 @@ So on any turn that touched a paper, the reply ends with **three lines, unprompt
 Three failures make this a rule rather than a preference, all in one session:
 - I finished a page-fit cut and stopped, so he asked what the status was;
 - I left artifact hosting on his side of the split for a day and a half while the credential to clear
-  it sat in the environment (see `credential-available` in `pipeline-check.mjs`);
+  it sat in the environment;
 - three consecutive panels returned Weak Accept and the ceiling they named was never the next task,
   because nothing turned "here is the score" into "here is what to do about it".
 
 **Never end a paper turn on a completed sub-task alone.** "Fits in 8 pages" is a measurement, not a
 status; the status is what that measurement makes possible next.
 
-**Enforcement leg.** `pipeline-check.mjs` prints its banner **unconditionally**, including when it has
-zero findings — deadline countdown, verdict row, and `➡️ NEXT`. It runs from `paper-status-gates.sh`
-on every edit to a paper source, so the state arrives without anyone pulling it. If that banner and
-this section ever disagree, the banner is a measurement and this is prose: believe the banner.
-
 ## How to run it
 
 ### 1. Measure (no reading yet)
@@ -90,8 +74,6 @@ gate's verdict **does not describe the current paper** — say so explicitly, an
 An accept-probability from a superseded draft is not evidence about this one; carrying it forward is
 the single most common way a status report lies.
 
-If the project ships a checker (`.claude/skills/paper-pipeline/scripts/pipeline-check.mjs`), run it.
-
 ### 3. Read the judgement rows — from BOTH checklists, they answer different questions
 
 The project already carries the checklists this skill should report against. Do not invent a new list
@@ -126,28 +108,6 @@ Short. He is asking because he wants to decide what to do next, not to read a re
 5. **What moved since he last asked**, three lines maximum.
 6. **The deadline, in his timezone**, and what is on the critical path to it.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record paper-status <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record paper-status <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-This skill reports state and does not judge the paper, so what it records is about the **status run**:
-**FINDING** — `<count>` blockers printed, `<report-path>` the status output.
-**ABSTAINED** — `no-witness`: the status run measured everything it can and printed zero blockers.
-`crashed`: the build did not run, so nothing was measured.
-
-🔴 `crashed` is the one outcome that must never be narrated as a status. This skill exists because
-state was being narrated instead of measured; a status report built on a build that did not happen
-is that same failure with a fresh timestamp on it. Under the old vocabulary this was `ERROR`, which
-sat in the same column as a verdict about the paper — it does not any more.
-
-🔴 **There is no PASS**, so "zero blockers" cannot be stored. Print it, and let the reader draw the
-conclusion from an empty blocker list they can see.
-
 ## Rules
 
 - **Never report a gate as run because I intended to run it.** Predicting a background agent's result,

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

@@ -14,17 +14,6 @@ export default experimental_skill({
   body: `
 # paper-status — state, measured before it is narrated
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs paper-status <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 author asks "what's the status there?" constantly, and the answer keeps coming from the wrong place: my
 memory of the session, which drifts, or a 200-line scorecard he cannot skim. Both fail the same way —
 **they narrate state instead of measuring it.**
@@ -55,18 +44,13 @@ So on any turn that touched a paper, the reply ends with **three lines, unprompt
 Three failures make this a rule rather than a preference, all in one session:
 - I finished a page-fit cut and stopped, so he asked what the status was;
 - I left artifact hosting on his side of the split for a day and a half while the credential to clear
-  it sat in the environment (see \`credential-available\` in \`pipeline-check.mjs\`);
+  it sat in the environment;
 - three consecutive panels returned Weak Accept and the ceiling they named was never the next task,
   because nothing turned "here is the score" into "here is what to do about it".
 
 **Never end a paper turn on a completed sub-task alone.** "Fits in 8 pages" is a measurement, not a
 status; the status is what that measurement makes possible next.
 
-**Enforcement leg.** \`pipeline-check.mjs\` prints its banner **unconditionally**, including when it has
-zero findings — deadline countdown, verdict row, and \`➡️ NEXT\`. It runs from \`paper-status-gates.sh\`
-on every edit to a paper source, so the state arrives without anyone pulling it. If that banner and
-this section ever disagree, the banner is a measurement and this is prose: believe the banner.
-
 ## How to run it
 
 ### 1. Measure (no reading yet)
@@ -96,8 +80,6 @@ gate's verdict **does not describe the current paper** — say so explicitly, an
 An accept-probability from a superseded draft is not evidence about this one; carrying it forward is
 the single most common way a status report lies.
 
-If the project ships a checker (\`.claude/skills/paper-pipeline/scripts/pipeline-check.mjs\`), run it.
-
 ### 3. Read the judgement rows — from BOTH checklists, they answer different questions
 
 The project already carries the checklists this skill should report against. Do not invent a new list
@@ -132,28 +114,6 @@ Short. He is asking because he wants to decide what to do next, not to read a re
 5. **What moved since he last asked**, three lines maximum.
 6. **The deadline, in his timezone**, and what is on the critical path to it.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record paper-status <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record paper-status <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-This skill reports state and does not judge the paper, so what it records is about the **status run**:
-**FINDING** — \`<count>\` blockers printed, \`<report-path>\` the status output.
-**ABSTAINED** — \`no-witness\`: the status run measured everything it can and printed zero blockers.
-\`crashed\`: the build did not run, so nothing was measured.
-
-🔴 \`crashed\` is the one outcome that must never be narrated as a status. This skill exists because
-state was being narrated instead of measured; a status report built on a build that did not happen
-is that same failure with a fresh timestamp on it. Under the old vocabulary this was \`ERROR\`, which
-sat in the same column as a verdict about the paper — it does not any more.
-
-🔴 **There is no PASS**, so "zero blockers" cannot be stored. Print it, and let the reader draw the
-conclusion from an empty blocker list they can see.
-
 ## Rules
 
 - **Never report a gate as run because I intended to run it.** Predicting a background agent's result,

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