paperlint 3.2.0 → 4.1.0

package/scripts/check.ts

@@ -34,9 +34,11 @@
  * (no TeX, no network), and the tail names every skip. "I ran check" then means one thing.
  */
 import { spawnSync } from "node:child_process";
-import { existsSync } from "node:fs";
+import { existsSync, readFileSync, rmSync } from "node:fs";
+import { tmpdir } from "node:os";
 import { delimiter, dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
+import { z } from "zod";
 import { isMain } from "../skills/paper-pipeline/scripts/consumer.mjs";
 
 const ROOT = dirname(dirname(fileURLToPath(import.meta.url)));
@@ -72,11 +74,17 @@ type GateCommand =
       readonly script: string;
       readonly run?: undefined;
       readonly inCi?: RunInCi;
+      /**
+       * The script is a vitest run, so its JSON report says how many tests were SKIPPED: a run
+       * whose exit is 0 and whose report counts a skip is a skip, not a pass.
+       */
+      readonly vitest?: true;
     }
   | {
       readonly run: readonly [string, ...string[]];
       readonly script?: undefined;
       readonly inCi?: undefined;
+      readonly vitest?: undefined;
     };
 
 /**
@@ -160,22 +168,14 @@ export const GATES: readonly Gate[] = [
   {
     name: "install e2e — pack, install under npm and pnpm, run the binary",
     job: "gates",
-    run: ["node", "test/e2e/install.ts"],
+    script: "test:e2e:install",
+    vitest: true,
   },
   {
-    name: "build e2e — a real pdflatex, and the PDF's fonts are measured",
+    name: "TeX e2e — real TeX Live: paperlint toolchain, a real pdflatex build of every fixture, the real banal",
     job: "build-e2e",
-    run: ["node", "test/e2e/build.ts"],
-  },
-  {
-    name: "banal e2e — the real banal on pdf.js-written XML gives banal-on-pdftohtml's numbers",
-    job: "build-e2e",
-    run: ["node", "test/e2e/banal.ts"],
-  },
-  {
-    name: "toolchain e2e — real TeX Live into $PAPERLINT_TEXLIVE_DIR, then a build with only it on PATH",
-    job: "build-e2e",
-    run: ["node", "test/e2e/toolchain.ts"],
+    script: "test:e2e:tex",
+    vitest: true,
   },
 ];
 
@@ -205,18 +205,41 @@ export const NOT_COVERED: Readonly<Record<string, string>> = {
 };
 
 /**
- * Exit 77 means "declared skip" — the same code vigiles' runner uses (`SKIP_EXIT_CODE`). The e2e steps exit 77 when a tool they need is
- * absent and --strict is off. Anything else nonzero is a failure.
+ * vitest's JSON report, as far as the verdict reads it: skipped (`pending`) and `todo` tests.
  *
- * 🔴 A SKIP IS A THIRD OUTCOME. Until the Codex review on #45 the e2e steps exited 0 on a skip,
- * this loop counted that as a pass, and `skipped` below was declared and never filled: a machine
- * without pnpm or TeX printed "all gates passed" for runs that never happened.
+ * 🔴 A SKIP IS A THIRD OUTCOME. Until the Codex review on #45 the e2e runs exited 0 on a skip and
+ * this loop counted that as a pass: a machine without pnpm or TeX printed "all gates passed" for
+ * runs that never happened. The count comes from the runner's own report, not from an exit code
+ * the tests would have to agree on.
  */
-export const SKIP_EXIT: number = 77;
-export function outcome(status: number | null): Outcome {
-  if (status === 0) return "pass";
-  if (status === SKIP_EXIT) return "skip";
-  return "fail";
+const VitestReport = z.looseObject({
+  numPendingTests: z.number().int().nonnegative(),
+  numTodoTests: z.number().int().nonnegative(),
+});
+
+/** How many tests a vitest JSON report says were not run, or null when it is not one. */
+export function skippedIn(report: string | null): number | null {
+  if (report === null) return null;
+  try {
+    const r = VitestReport.safeParse(JSON.parse(report));
+    return r.success ? r.data.numPendingTests + r.data.numTodoTests : null;
+  } catch {
+    return null;
+  }
+}
+
+/**
+ * A gate's outcome from its exit status and, for a vitest gate, the skip count its report gave
+ * (`null`: the report is missing or unreadable, which cannot be read as a pass).
+ */
+export function outcome(
+  status: number | null,
+  vitest?: { readonly skipped: number | null },
+): Outcome {
+  if (status !== 0) return "fail";
+  if (vitest === undefined) return "pass";
+  if (vitest.skipped === null) return "fail";
+  return vitest.skipped > 0 ? "skip" : "pass";
 }
 
 /** The gates that did not pass, each as the line the verdict prints, split by outcome. */
@@ -225,11 +248,29 @@ interface NotPassed {
   skipped: string[];
 }
 
+/** A report file's text, read once and removed; null when the run wrote none. */
+export type ReadReport = (file: string) => string | null;
+const readReport: ReadReport = (file) => {
+  if (!existsSync(file)) return null;
+  const text = readFileSync(file, "utf8");
+  rmSync(file, { force: true });
+  return text;
+};
+
+/** The arguments that make a vitest gate write its JSON report to `file`, beside the usual output. */
+export const reportArgs = (file: string): string[] => [
+  "--",
+  "--reporter=default",
+  "--reporter=json",
+  `--outputFile.json=${file}`,
+];
+
 /** Run each gate in order; `write` announces it before it starts. */
 function runEach(
   gates: readonly Gate[],
   spawn: Spawn,
   write: (text: string) => unknown,
+  reportOf: ReadReport,
 ): NotPassed {
   const BIN_FIRST_PATH = [join(ROOT, "node_modules", ".bin"), process.env.PATH]
     .filter(Boolean)
@@ -237,10 +278,14 @@ function runEach(
   const failed: string[] = [];
   const skipped: string[] = [];
 
-  for (const g of gates) {
+  for (const [i, g] of gates.entries()) {
     write(`── ${g.name}\n`);
     const [cmd, ...args] = commandOf(g);
-    const r = spawn(cmd, args, {
+    const file = join(
+      tmpdir(),
+      `paperlint-check-${String(process.pid)}-${String(i)}.json`,
+    );
+    const r = spawn(cmd, g.vitest ? [...args, ...reportArgs(file)] : args, {
       cwd: ROOT,
       stdio: "inherit",
       encoding: "utf8",
@@ -249,12 +294,18 @@ function runEach(
     // 🔴 The exit code is read from the command itself, never from a pipe. `cmd | tail && …`
     // reports the FILTER's status, which is almost always zero — that is how a red harness
     // shipped on 2026-09-16.
-    const o = outcome(r.status);
+    const skips = g.vitest ? { skipped: skippedIn(reportOf(file)) } : undefined;
+    const o = outcome(r.status, skips);
     if (o === "pass") continue;
     const shown = commandOf(g).join(" ");
     if (o === "skip")
-      skipped.push(`${g.name}  (${shown} → ${String(SKIP_EXIT)})`);
-    else failed.push(`${g.name}  (${shown} → ${String(r.status)})`);
+      skipped.push(
+        `${g.name}  (${shown} → ${String(skips?.skipped)} test(s) skipped)`,
+      );
+    else
+      failed.push(
+        `${g.name}  (${shown} → ${r.status === 0 ? "exit 0, but no vitest JSON report to read skips from" : String(r.status)})`,
+      );
   }
   return { failed, skipped };
 }
@@ -299,14 +350,16 @@ export function runGates({
   log = console.log,
   err = console.error,
   write = (s: string) => process.stdout.write(s),
+  reportOf = readReport,
 }: {
   gates?: readonly Gate[];
   spawn?: Spawn;
   log?: (line: string) => void;
   err?: (line: string) => void;
   write?: (text: string) => unknown;
+  reportOf?: ReadReport;
 } = {}): number {
-  const notPassed = runEach(gates, spawn, write);
+  const notPassed = runEach(gates, spawn, write, reportOf);
   report(gates, notPassed, { log, err });
   return notPassed.failed.length ? 1 : 0;
 }

package/scripts/coverage-config.test.ts

@@ -430,7 +430,6 @@ test("the exclude list is exactly the justified set", () => {
     "src/types.ts",
     "src/ports/*.ts",
     "src/domain/page-layout.ts",
-    "src/domain/paths.ts",
     "eslint-rules/rule-context.ts",
   ]);
   assert.deepEqual(CONFIG.evalOnly, [

package/scripts/harness-api.frozen.json

@@ -35,7 +35,6 @@
     "skills/paper-pipeline/scripts/consumer.harness.mjs",
     "skills/paper-pipeline/scripts/extract-ref-facts.harness.mjs",
     "skills/paper-pipeline/scripts/generated-code.harness.mjs",
-    "skills/paper-pipeline/scripts/pipeline-check.harness.mjs",
     "skills/paper-pipeline/scripts/population-map.harness.mjs",
     "skills/paper-pipeline/scripts/provenance.harness.mjs",
     "skills/paper-pipeline/scripts/round-diff.harness.ts",

package/scripts/test.test.ts

@@ -24,7 +24,7 @@ test("a failing vitest does not skip the harnesses, and is named as the failure"
     1,
   );
   assert.deepEqual(calls, [
-    ["vitest", "run"],
+    ["vitest", "run", "--project", "unit"],
     ["vigiles", "test", "--min=1", "--no-skip"],
   ]);
   assert.deepEqual(said, [

package/scripts/test.ts

@@ -46,7 +46,7 @@ export function withSources(env: NodeJS.ProcessEnv): NodeJS.ProcessEnv {
 }
 
 export const SUITES: readonly Suite[] = [
-  { name: "vitest", command: ["vitest", "run"] },
+  { name: "vitest", command: ["vitest", "run", "--project", "unit"] },
   { name: "harnesses", command: ["vigiles", "test", "--min=1"] },
 ];
 

package/skills/analyze-sibling-paper/SKILL.md

@@ -5,24 +5,10 @@ context: fork
 allowed-tools: [WebSearch, WebFetch, Read, Write, Grep, Glob, Bash, Agent]
 ---
 
-<!-- vigiles:sha256:f528cbe9e892d6d0 compiled from skills/analyze-sibling-paper/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:238796152df07749 compiled from skills/analyze-sibling-paper/SKILL.md.spec.ts -->
 
 # analyze-sibling-paper — settle "isn't this just X?" before a reviewer does
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs analyze-sibling-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.
-
-The `<paper-dir>` argument is **your** paper, not the sibling — the row belongs to the paper being
-defended. The sibling is named by `<report-path>` when the verdict is recorded.
-
 When a paper close to yours surfaces, the wrong move is to cite it from its abstract and move on — that
 leaves a scoop risk you can't see and a reviewer can. This skill reads the *actual* competitor, judges
 whether your contribution genuinely differs, and produces a saved analysis with concrete action points
@@ -114,30 +100,6 @@ and the action points (with the exact clause text to add/replace). Per the save-
 analysis that lives only in a chat is lost the moment the session ends — and it's exactly what you'll need
 again at rebuttal. **A close sibling with no file in `<paper-dir>/siblings/` is an unfinished analysis.**
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record analyze-sibling-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record analyze-sibling-paper <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `<count>` is the number of action points the card produced (positioning clauses plus
-*MUST CITE* entries), `<report-path>` is the saved card, which names the sibling. Add `--blocking`
-for a genuine scoop, which the skill already treats as an escalation rather than a clause.
-**ABSTAINED** — `no-witness`: the sibling was read in full and the delta needs no text to change.
-`blocked`: the sibling's full text could not be obtained, so only its abstract was seen — which is
-explicitly not an analysis and must never be recorded as one.
-
-🔴 **There is no PASS.** "The delta is real" read identically whether the sibling had been read
-whole or skimmed, and this skill's own first rule is that an abstract-only delta is not a verdict.
-`no-witness` and `blocked` now say which happened.
-
-One row per sibling analysed, filed under its own `--check=<sibling-slug>`; several finding rows
-against one paper is the normal shape here, not a check that keeps failing. Before 2026-08-10 they
-would have overwritten one another.
-
 ## Rules
 - **Read the paper, not the abstract.** An abstract-only "delta" is not a verdict — and the card must
   say so: `read: abstract` in its frontmatter, and which parts in its `**Read:**` line.

package/skills/analyze-sibling-paper/SKILL.md.spec.ts

@@ -24,20 +24,6 @@ export default experimental_skill({
   body: `
 # analyze-sibling-paper — settle "isn't this just X?" before a reviewer does
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs analyze-sibling-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.
-
-The \`<paper-dir>\` argument is **your** paper, not the sibling — the row belongs to the paper being
-defended. The sibling is named by \`<report-path>\` when the verdict is recorded.
-
 When a paper close to yours surfaces, the wrong move is to cite it from its abstract and move on — that
 leaves a scoop risk you can't see and a reviewer can. This skill reads the *actual* competitor, judges
 whether your contribution genuinely differs, and produces a saved analysis with concrete action points
@@ -129,30 +115,6 @@ and the action points (with the exact clause text to add/replace). Per the save-
 analysis that lives only in a chat is lost the moment the session ends — and it's exactly what you'll need
 again at rebuttal. **A close sibling with no file in \`<paper-dir>/siblings/\` is an unfinished analysis.**
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record analyze-sibling-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record analyze-sibling-paper <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-**FINDING** — \`<count>\` is the number of action points the card produced (positioning clauses plus
-*MUST CITE* entries), \`<report-path>\` is the saved card, which names the sibling. Add \`--blocking\`
-for a genuine scoop, which the skill already treats as an escalation rather than a clause.
-**ABSTAINED** — \`no-witness\`: the sibling was read in full and the delta needs no text to change.
-\`blocked\`: the sibling's full text could not be obtained, so only its abstract was seen — which is
-explicitly not an analysis and must never be recorded as one.
-
-🔴 **There is no PASS.** "The delta is real" read identically whether the sibling had been read
-whole or skimmed, and this skill's own first rule is that an abstract-only delta is not a verdict.
-\`no-witness\` and \`blocked\` now say which happened.
-
-One row per sibling analysed, filed under its own \`--check=<sibling-slug>\`; several finding rows
-against one paper is the normal shape here, not a check that keeps failing. Before 2026-08-10 they
-would have overwritten one another.
-
 ## Rules
 - **Read the paper, not the abstract.** An abstract-only "delta" is not a verdict — and the card must
   say so: \`read: abstract\` in its frontmatter, and which parts in its \`**Read:**\` line.

package/skills/argument-arc/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: argument-arc
 description: Build or repair the paper's argument architecture — the one-sentence-per-section outline, the bottom-up inevitability pass, and the name/number budget. Run it when the reader says the paper throws ideas at them, when a structural objection repeats, or before any large rewrite. Not a prose or length skill.
-allowed-tools: [Read, Write, Grep, Glob, Agent, Bash(node .claude/skills/paper-pipeline/scripts/announce.mjs:*), Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)]
+allowed-tools: [Read, Write, Grep, Glob, Agent]
 ---
 
-<!-- vigiles:sha256:05a1eaa79bb596d5 compiled from skills/argument-arc/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:66be3161e5bde916 compiled from skills/argument-arc/SKILL.md.spec.ts -->
 
 # argument-arc — does the paper carry the reader to one conclusion
 
@@ -14,17 +14,6 @@ allowed-tools: [Read, Write, Grep, Glob, Agent, Bash(node .claude/skills/paper-p
 > whether the argument exists. Run it *before* them — cutting words inside a broken arc is how a
 > session burns a day and ships the same paper.
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs argument-arc <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 failure it exists to catch has a signature: every paragraph is defensible, every number is real,
 and the reader still finishes the section unable to say what it was for. That is not a prose problem
 and no amount of rewriting sentences fixes it.
@@ -48,7 +37,6 @@ came out — which is how a run gets thrown away. That is not hypothetical: it w
 data is collected costs the data. Costs a paragraph; saves a study.**
 
 `build-benchmark` reads this paragraph before designing, and refuses to proceed if `frame` is empty.
-`pipeline-check.mjs` reports a study that ran with no stated claim.
 
 *Added 2026-08-03 alongside the replacement of the numbered stage list — this skill previously existed
 only as a repair, which meant nobody stated the claim while stating it was still cheap.*
@@ -125,28 +113,6 @@ most needs help. This skill does:
   the calendar against it is a category error.
 - **Rebuild produces a new outline through steps 1–4 above, and it too gets shown before editing.**
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record argument-arc <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record argument-arc <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-🔴 **There is no PASS.** "The arc carries the reader" is not a value this pass can write down; it is
-what a reader may conclude from the absence of findings, and the concluding is theirs.
-
-**FINDING** — the arc is broken; `<count>` is the number of sections the new outline moves, merges
-or deletes, and `<report-path>` is that outline. Add `--blocking` when there is no conclusion
-sentence to build an arc from: that refusal is a finding about the draft, not an aborted run, and
-`<report-path>` is the one-line statement of what is missing.
-**ABSTAINED** — `no-witness`: the outline was read end to end and nothing moved. `blocked`: there
-was no outline to read at all.
-
-An `ABSTAINED no-witness` on a draft the author has twice called a pile is a missed finding, and
-`status.mjs` will start asking about a check that has only ever abstained.
-
 ## Rules
 
 - **The arc is judged on the outline, never on the draft.** If you find yourself rereading paragraphs

package/skills/argument-arc/SKILL.md.spec.ts

@@ -10,15 +10,7 @@ export default experimental_skill({
   name: "argument-arc",
   description:
     "Build or repair the paper's argument architecture — the one-sentence-per-section outline, the bottom-up inevitability pass, and the name/number budget. Run it when the reader says the paper throws ideas at them, when a structural objection repeats, or before any large rewrite. Not a prose or length skill.",
-  tools: [
-    "Read",
-    "Write",
-    "Grep",
-    "Glob",
-    "Agent",
-    "Bash(node .claude/skills/paper-pipeline/scripts/announce.mjs:*)",
-    "Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)",
-  ],
+  tools: ["Read", "Write", "Grep", "Glob", "Agent"],
   body: `
 # argument-arc — does the paper carry the reader to one conclusion
 
@@ -28,17 +20,6 @@ export default experimental_skill({
 > whether the argument exists. Run it *before* them — cutting words inside a broken arc is how a
 > session burns a day and ships the same paper.
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs argument-arc <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 failure it exists to catch has a signature: every paragraph is defensible, every number is real,
 and the reader still finishes the section unable to say what it was for. That is not a prose problem
 and no amount of rewriting sentences fixes it.
@@ -62,7 +43,6 @@ came out — which is how a run gets thrown away. That is not hypothetical: it w
 data is collected costs the data. Costs a paragraph; saves a study.**
 
 \`build-benchmark\` reads this paragraph before designing, and refuses to proceed if \`frame\` is empty.
-\`pipeline-check.mjs\` reports a study that ran with no stated claim.
 
 *Added 2026-08-03 alongside the replacement of the numbered stage list — this skill previously existed
 only as a repair, which meant nobody stated the claim while stating it was still cheap.*
@@ -139,28 +119,6 @@ most needs help. This skill does:
   the calendar against it is a category error.
 - **Rebuild produces a new outline through steps 1–4 above, and it too gets shown before editing.**
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record argument-arc <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record argument-arc <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-🔴 **There is no PASS.** "The arc carries the reader" is not a value this pass can write down; it is
-what a reader may conclude from the absence of findings, and the concluding is theirs.
-
-**FINDING** — the arc is broken; \`<count>\` is the number of sections the new outline moves, merges
-or deletes, and \`<report-path>\` is that outline. Add \`--blocking\` when there is no conclusion
-sentence to build an arc from: that refusal is a finding about the draft, not an aborted run, and
-\`<report-path>\` is the one-line statement of what is missing.
-**ABSTAINED** — \`no-witness\`: the outline was read end to end and nothing moved. \`blocked\`: there
-was no outline to read at all.
-
-An \`ABSTAINED no-witness\` on a draft the author has twice called a pile is a missed finding, and
-\`status.mjs\` will start asking about a check that has only ever abstained.
-
 ## Rules
 
 - **The arc is judged on the outline, never on the draft.** If you find yourself rereading paragraphs

package/skills/build-benchmark/SKILL.md

@@ -5,21 +5,10 @@ context: fork
 allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, Agent]
 ---
 
-<!-- vigiles:sha256:067ada6f8aa44d5b compiled from skills/build-benchmark/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:0b91129ca6a6b2a3 compiled from skills/build-benchmark/SKILL.md.spec.ts -->
 
 # build-benchmark — the study + the artifact reviewers can run
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs build-benchmark <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 measurement paper is only as strong as the artifact a reviewer can `cd` into and re-run. This skill
 covers both halves: the study design that makes the finding true, and the self-checking artifact that
 makes it *verifiable*. The contribution is the **method**, not the one tool you happened to test — build
@@ -163,35 +152,6 @@ real-code-through-real-contract execution reveals it.
 Before submitting, verify the artifact you built with the reviewer-side reproduction protocol:
 **`references/adversarial-cold-repro.md`** (cold re-run, three-way reconcile, robustness attacks).
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record build-benchmark <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record build-benchmark <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-🔴 **There is no PASS.** An artifact that recomputes every headline number and exits 0 has produced
-no finding; it has not certified the study. Record the absence, do not name it a success.
-
-**FINDING** — `<count>` numbers did not reproduce, or reproduce only with caveats; `<report-path>`
-is the artifact output. Add `--blocking` for the §0 refusal: `frame` is empty, so the study was not
-designed.
-**ABSTAINED** — `no-witness`: the artifact ran and every number reproduced. `input-missing`: the
-raw data is not in the repo. `crashed`: the harness itself died.
-
-🔴 That §0 refusal is a **finding, not an aborted run** — it is a fact about the work, so it is a
-FINDING and not an abstention. Record it and stop. A study that was never designed leaves exactly
-the same silence as one that is still running, and the difference costs a week to rediscover.
-
-🔴 **THREE MECHANICAL CHECKS FILE UNDER THIS SKILL** and each has its own ledger row:
-`build-benchmark/check-provenance`, `build-benchmark/arm-permutation`,
-`build-benchmark/delivered-pdf` (see `.claude/skills/paper-pipeline/scripts/run-mechanical.mjs`). Until 2026-08-10 the
-ledger keyed on the SKILL, so a clean run of one erased a finding of another from every derived
-view — which is why two of the three sat unwired. This block records the JUDGEMENT pass, under the
-bare key `build-benchmark`; never file a mechanical result here.
-
 ## Compose with
 - **argument-arc (frame mode)** — 🔴 **hard input.** Owns row `frame`, the stated claim. No `frame`, no study.
 - **research-ideate** (upstream) — supplies the contribution and the pitfall to invert; this skill turns

package/skills/build-benchmark/SKILL.md.spec.ts

@@ -15,17 +15,6 @@ export default experimental_skill({
   body: `
 # build-benchmark — the study + the artifact reviewers can run
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs build-benchmark <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 measurement paper is only as strong as the artifact a reviewer can \`cd\` into and re-run. This skill
 covers both halves: the study design that makes the finding true, and the self-checking artifact that
 makes it *verifiable*. The contribution is the **method**, not the one tool you happened to test — build
@@ -169,35 +158,6 @@ real-code-through-real-contract execution reveals it.
 Before submitting, verify the artifact you built with the reviewer-side reproduction protocol:
 **\`references/adversarial-cold-repro.md\`** (cold re-run, three-way reconcile, robustness attacks).
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record build-benchmark <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record build-benchmark <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-🔴 **There is no PASS.** An artifact that recomputes every headline number and exits 0 has produced
-no finding; it has not certified the study. Record the absence, do not name it a success.
-
-**FINDING** — \`<count>\` numbers did not reproduce, or reproduce only with caveats; \`<report-path>\`
-is the artifact output. Add \`--blocking\` for the §0 refusal: \`frame\` is empty, so the study was not
-designed.
-**ABSTAINED** — \`no-witness\`: the artifact ran and every number reproduced. \`input-missing\`: the
-raw data is not in the repo. \`crashed\`: the harness itself died.
-
-🔴 That §0 refusal is a **finding, not an aborted run** — it is a fact about the work, so it is a
-FINDING and not an abstention. Record it and stop. A study that was never designed leaves exactly
-the same silence as one that is still running, and the difference costs a week to rediscover.
-
-🔴 **THREE MECHANICAL CHECKS FILE UNDER THIS SKILL** and each has its own ledger row:
-\`build-benchmark/check-provenance\`, \`build-benchmark/arm-permutation\`,
-\`build-benchmark/delivered-pdf\` (see \`.claude/skills/paper-pipeline/scripts/run-mechanical.mjs\`). Until 2026-08-10 the
-ledger keyed on the SKILL, so a clean run of one erased a finding of another from every derived
-view — which is why two of the three sat unwired. This block records the JUDGEMENT pass, under the
-bare key \`build-benchmark\`; never file a mechanical result here.
-
 ## Compose with
 - **argument-arc (frame mode)** — 🔴 **hard input.** Owns row \`frame\`, the stated claim. No \`frame\`, no study.
 - **research-ideate** (upstream) — supplies the contribution and the pitfall to invert; this skill turns

package/skills/camera-ready/SKILL.md

@@ -4,21 +4,10 @@ description: On acceptance, turn the anonymized-for-review paper into the de-ano
 allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch]
 ---
 
-<!-- vigiles:sha256:8fa0190054cc5314 compiled from skills/camera-ready/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:5c85ef4004c31956 compiled from skills/camera-ready/SKILL.md.spec.ts -->
 
 # camera-ready — de-anonymize an accepted paper into the final proceedings version
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs camera-ready <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 reviewed PDF was anonymized on purpose. Acceptance flips that: the camera-ready carries your
 real name, your real repo, and an archival DOI — and it's the version that gets indexed, so it's the
 actual authorship evidence. This skill is the reverse of the anonymization you did at
@@ -113,28 +102,6 @@ If tight, ACM allows references to spill into the reference-only extra pages.
 - Record the paper's DOI, the artifact DOI, and the ORCID in the paper's HANDOFF — those three IDs are
   the authorship evidence and the anchor the extension (`extend-paper`) builds on.
 
-## 6. Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record camera-ready <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record camera-ready <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `<count>` residual items still open; `<report-path>` names them. Add `--blocking` for
-anything that must not be pushed past: anonymization residue, a dead artifact link, or — on a
-security paper — disclosure not yet complete.
-**ABSTAINED** — `no-witness`: shipped, de-anonymized, DOI live, page limit re-checked, with the DOI
-in the note. `blocked`: the acceptance notice has not arrived, so there is nothing to make ready.
-
-🔴 That blocking finding is the only one in this pipeline whose consequence is **irreversible**. The
-public de-anonymized repo is Google-findable the moment it is pushed, so record it before, not after.
-
-🔴 **There is no PASS**, and on this skill that is not a formality: a stored "shipped" would have
-been the one row in the pipeline that could be true of a repo nobody had looked at. The DOI in the
-note is the witness. Without it there is nothing to check the row against.
-
 ## Compose with
 - **submit-paper** (upstream — this reverses what it anonymized).
 - **paper-pipeline/references/anonymization.md** — the canonical list of anonymization moves; undo each.