paperlint 3.2.0 → 4.1.0

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

@@ -1,12 +1,10 @@
 /**
- * consumer.harness.mjs — every rung of `ledgerPath()`, both directions, plus the two path facts
- * the move into a package depends on.
+ * consumer.harness.mjs — the path facts the move into a package depends on, both directions.
  *
  * `npx vigiles test skills/paper-pipeline/scripts/consumer.harness.mjs`
  *
  * 🔴 WHY THIS FILE IS NOT OPTIONAL. The resolutions in `consumer.mjs` all fail in the SILENT
- * direction when they are wrong: a bad ledger path still accepts appends, a bad main guard still
- * exits 0, a bad root still hashes a missing directory to a stable value. None of them produce an
+ * direction when they are wrong: a bad main guard still exits 0, a bad root still hashes a missing directory to a stable value. None of them produce an
  * error, and every one of them produces a run that reads as success. So each is asserted here in
  * BOTH directions — fires when it should, silent when it should — because an assertion that only
  * ever sees the good case cannot tell a working resolver from a constant.
@@ -38,7 +36,6 @@ import {
   insideNodeModules,
   installedSkills,
   isMain,
-  ledgerPath,
   pipelineScripts,
   scriptsRoot,
   PACKAGE_NAME,
@@ -101,94 +98,6 @@ function installedDir(root) {
   return d;
 }
 
-// ── I. RUNG 1 — the environment wins, and it wins over a declaration ─────────────────────────
-{
-  const root = fakeConsumer({ ledger: "declared/here.jsonl" });
-  const env = { PIPELINE_LEDGER: join(root, "from-env.jsonl") };
-  assert.equal(
-    ledgerPath(installedDir(root), { env, cwd: root }),
-    resolve(join(root, "from-env.jsonl")),
-    "PIPELINE_LEDGER did not win. It must outrank everything: harnesses set it BEFORE importing " +
-      "the ledger precisely so fixture rows cannot reach real history, and a declaration on disk " +
-      "that could override it would put them there.",
-  );
-  // The other direction: with the variable gone, the same call must move to the next rung.
-  assert.equal(
-    ledgerPath(installedDir(root), { env: {}, cwd: root }),
-    resolve(root, "declared/here.jsonl"),
-    "without PIPELINE_LEDGER the declaration must be used — otherwise rung 1 is not a rung, it " +
-      "is the only path, and this assertion pair proves nothing about precedence.",
-  );
-}
-
-// ── II. RUNG 2 — the consumer's declaration, resolved against the consumer root ───────────────
-{
-  const root = fakeConsumer({ ledger: "docs/pipeline-runs.jsonl" });
-  assert.equal(
-    ledgerPath(installedDir(root), { env: {}, cwd: root }),
-    join(root, "docs/pipeline-runs.jsonl"),
-    "a declared relative ledger must resolve against the consumer root, not against the cwd of " +
-      "whatever process happened to start",
-  );
-  // 🔴 `null` is a keystroke, not an absence. `?? DEFAULT` would read it as "nothing declared"
-  // and silently use another file — the same distinction `papersRoot()` makes.
-  assert.throws(
-    () =>
-      ledgerPath(installedDir(root), {
-        env: {},
-        cwd: fakeConsumer({ ledger: null }),
-      }),
-    /must be a non-empty string/,
-    'a `"ledger": null` was accepted. Anything written down must be usable; only ABSENCE may ' +
-      "fall through to the next rung.",
-  );
-  assert.throws(
-    () =>
-      ledgerPath(installedDir(root), {
-        env: {},
-        cwd: fakeConsumer({ ledger: "" }),
-      }),
-    /must be a non-empty string/,
-    "an empty declared ledger was accepted; it resolves to the consumer root itself",
-  );
-}
-
-// ── III. RUNG 3 — beside the file, but NEVER inside node_modules ──────────────────────────────
-{
-  const root = fakeConsumer(undefined);
-  // Developing the package in its own checkout: the default is legitimate.
-  const own = mkdtempSync(join(TMP, "checkout-"));
-  assert.equal(
-    ledgerPath(own, { env: {}, cwd: root }),
-    join(own, "runs.jsonl"),
-    "outside node_modules and with nothing declared, the ledger belongs beside the module",
-  );
-  // Installed as a dependency with nothing declared: refusing is the whole point.
-  let err;
-  try {
-    ledgerPath(installedDir(root), { env: {}, cwd: root });
-  } catch (e) {
-    err = e;
-  }
-  assert.ok(
-    err,
-    "🔴 ledgerPath RETURNED A PATH INSIDE node_modules. Appending there SUCCEEDS, so the rows " +
-      "look recorded until the next `npm ci` deletes them — silent data loss with no error at " +
-      "any point. This must throw.",
-  );
-  assert.match(
-    err.message,
-    /"ledger"/,
-    "the refusal must name the key to declare. An error that states the problem without the cure " +
-      "gets worked around by whoever hits it.",
-  );
-  assert.match(
-    err.message,
-    /paperlint\.json/,
-    "the refusal must name the file the key goes in",
-  );
-}
-
 // ── IV. `insideNodeModules` is SEGMENT-WISE, not a substring ──────────────────────────────────
 assert.equal(
   insideNodeModules(join("a", "node_modules", "b")),
@@ -199,7 +108,7 @@ assert.equal(
   insideNodeModules(join("a", "my-node_modules-inspector", "b")),
   false,
   "a directory whose NAME merely contains `node_modules` was treated as an install — that " +
-    "consumer would be refused its own ledger for a naming coincidence",
+    "consumer would be refused for a naming coincidence",
 );
 assert.equal(
   insideNodeModules(join("a", "b")),
@@ -433,7 +342,7 @@ assert.equal(
   );
 }
 
-// ── X. THE SCRIPT NAMES ARE DERIVED, NOT RESTATED ─────────────────────────────────────────────
+// ── X. THE PREFIX IS DERIVED, NOT RESTATED ─────────────────────────────────────────────
 // The names belong to this package; a consumer that spelled them out would keep its copy in step
 // by hand. The trailing slash on `prefix` is load-bearing: without it the prefix also matches a
 // SIBLING directory whose name merely starts with the root's.
@@ -443,19 +352,17 @@ assert.equal(
   // `assert` aborts at the first failure, and a prefix that lost its slash died on "must end in a
   // separator" — leaving the assertion that states WHY the slash matters unreached and unproven.
   assert.equal(
-    "a/b-other/ledger.mjs".startsWith(s.prefix),
+    "a/b-other/structure.mjs".startsWith(s.prefix),
     false,
     "the prefix matched a sibling directory sharing the root's name — drop the trailing slash " +
       "and every such path is mistaken for a pipeline script",
   );
   assert.equal(
-    "a/b/ledger.mjs".startsWith(s.prefix),
+    "a/b/structure.mjs".startsWith(s.prefix),
     true,
     "the prefix failed on a real member",
   );
   assert.equal(s.prefix, "a/b/", "prefix must end in a separator");
-  assert.equal(s.announce, "a/b/announce.mjs");
-  assert.equal(s.ledger, "a/b/ledger.mjs");
 
   // EXACTLY ONE slash, whatever the consumer typed. `scriptsRoot()` returns the declaration
   // verbatim, so a trailing slash in paperlint.json arrives here intact; `${root}/` would then give
@@ -467,11 +374,6 @@ assert.equal(
     'a declared trailing slash doubled the separator. `"scripts": "tools/pipeline/"` is a normal ' +
       "thing to write, and the doubled prefix matches no instruction at all.",
   );
-  assert.equal(
-    typedSlash.ledger,
-    "a/b/ledger.mjs",
-    "the script paths doubled the separator too",
-  );
 }
 
 // ── XI. WHICH SKILLS ARE INSTALLED — a link counts, a dangling link is REFUSED (paperlint#62) ────────

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,
@@ -81,7 +57,7 @@ import {
   statSync,
 } from "node:fs";
 import { join, resolve, sep } from "node:path";
-import { fileURLToPath, pathToFileURL } from "node:url";
+import { pathToFileURL } from "node:url";
 
 // Re-exported, not re-declared — see the note in `lib/paper-config.mjs`. This file is not a hook
 // and never needed its own copy.
@@ -122,20 +98,6 @@ export function consumerRoot({ env = process.env, cwd = process.cwd() } = {}) {
   return env.CLAUDE_PROJECT_DIR || cwd;
 }
 
-/**
- * The directory of venue TeX files THIS PACKAGE ships — `paper-guards.tex` and each venue's
- * `<venue>.tex` — which a paper's preamble `\input`s and `paperlint build` puts on `TEXINPUTS`.
- *
- * Resolved from this file's own location, never from the caller's cwd: the directory travels
- * with the package, wherever the package is installed (own checkout, `node_modules`, a plugin
- * cache). `import.meta.url` is the realpath, so a symlinked skills directory changes nothing.
- */
-export function packageVenuesDir() {
-  return fileURLToPath(
-    new URL("../../submit-paper/references/venues", import.meta.url),
-  );
-}
-
 /**
  * The package's npm name — the directory it lands in under `node_modules`, and the name Node
  * resolves it by. Every path into the installed package is built from this, never re-spelled;
@@ -246,68 +208,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 +262,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 +301,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 +361,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 +400,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 +413,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,