paperlint 3.1.3 → 4.0.0

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

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

package/skills/render-paper/{extract-pdf-facts.harness.mjs → extract-pdf-facts.harness.ts}

@@ -24,7 +24,29 @@ import {
 import { tmpdir } from "node:os";
 import { dirname, join, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
-import { createChecker } from "../../lib/check.mjs";
+import { z } from "zod";
+import { createChecker } from "../../lib/check.ts";
+import type { ScriptResult } from "../../test/support.ts";
+
+/** The facts file, as far as these checks read it. */
+const Facts = z.looseObject({
+  schema: z.unknown().optional(),
+  pdf: z.unknown().optional(),
+  venue: z.unknown().optional(),
+  kind: z.unknown().optional(),
+  geometry_source: z.unknown().optional(),
+  columns: z.unknown().optional(),
+  fonts: z.unknown().optional(),
+});
+const Fonts = z.array(
+  z.looseObject({
+    name: z.unknown().optional(),
+    embedded: z.unknown().optional(),
+    type: z.unknown().optional(),
+  }),
+);
+const readFacts = (file: string) =>
+  Facts.parse(JSON.parse(readFileSync(file, "utf8")));
 
 const HERE = dirname(fileURLToPath(import.meta.url));
 const SHIM = join(HERE, "extract-pdf-facts.mjs");
@@ -37,7 +59,7 @@ const root = realpathSync(mkdtempSync(join(tmpdir(), "paperlint-extract-")));
  * Run the shim from `root`, with no banal anywhere unless `env` names one. `HOME` is the temp root:
  * without it Node falls back to the account's home, where `paperlint toolchain` may have installed banal.
  */
-const shim = (args, env = {}) =>
+const shim = (args: readonly string[], env: Record<string, string> = {}) =>
   spawnSync(process.execPath, [SHIM, ...args], {
     cwd: root,
     encoding: "utf8",
@@ -58,7 +80,8 @@ const shim = (args, env = {}) =>
       ...env,
     },
   });
-const said = (r) => `${r.stdout}${r.stderr}`;
+const said = (r: Pick<ScriptResult, "stdout" | "stderr">) =>
+  `${r.stdout}${r.stderr}`;
 
 try {
   const paper = join(root, "papers", "mixed");
@@ -92,7 +115,9 @@ try {
       /banal not found/.test(local.stderr),
     said(local),
   );
-  const facts = JSON.parse(readFileSync(factsFile, "utf8"));
+  const facts = readFacts(factsFile);
+  const fonts = Fonts.safeParse(facts.fonts);
+  const fontList = fonts.success ? fonts.data : [];
   check(
     "the facts are schema 2, about paper.pdf, for the venue paperlint.json declares",
     facts.schema === 2 &&
@@ -103,10 +128,10 @@ try {
   );
   check(
     "a text PDF has fonts",
-    Array.isArray(facts.fonts) && facts.fonts.length === 4,
+    fonts.success && fontList.length === 4,
     JSON.stringify(facts.fonts),
   );
-  const times = facts.fonts.find((f) => f.name === "Times-Roman");
+  const times = fontList.find((f) => f.name === "Times-Roman");
   check(
     "🔴 Times-Roman — pdffonts `Type 1 Custom no no yes` — is embedded: false (the old reader said true)",
     times?.embedded === false && times.type === "Type 1",
@@ -114,7 +139,7 @@ try {
   );
   check(
     "the Type 3 font keeps poppler's type spelling, which consumers match on",
-    facts.fonts.some((f) => f.type === "Type 3"),
+    fontList.some((f) => f.type === "Type 3"),
   );
 
   const fake = join(root, "banal.pl");
@@ -123,7 +148,7 @@ try {
     `print '{"papersize":[792,612],"columns":2,"bodyfontsize":9,"pages":[{}]}';\n`,
   );
   const withBanal = shim([paper, "--strict"], { BANAL: fake });
-  const g = JSON.parse(readFileSync(factsFile, "utf8"));
+  const g = readFacts(factsFile);
   check(
     "--strict with banal ($BANAL): exit 0, and the geometry is banal's",
     withBanal.status === 0 && g.geometry_source === "banal" && g.columns === 2,
@@ -176,7 +201,7 @@ try {
       direct.stdout.startsWith(
         "✅ draft.pdf → papers/loose/_build/paper.facts.json (",
       ) &&
-      JSON.parse(readFileSync(looseFacts, "utf8")).venue === null,
+      readFacts(looseFacts).venue === null,
     said(direct),
   );
   // The project directory IS the facts file (nonsense, but an environment can say it): the

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

@@ -34,7 +34,7 @@ import { spawnSync } from "node:child_process";
 import { fileURLToPath } from "node:url";
 import { dirname, join } from "node:path";
 import { checkSkill } from "../../lib/skill-checks.mjs";
-import { papersRoot } from "../../eslint-rules/papers.mjs";
+import { papersRoot } from "#eslint-rules/papers";
 import {
   consumerRoot,
   settingsOf,
@@ -44,7 +44,7 @@ await checkSkill("render-paper");
 
 // The TeX package pins that stood here (texlive-fonts-extra, texlive-plain-generic in
 // ensure-toolchain.sh) moved with the list itself: the venue profiles declare the packages, and
-// src/tex-requirements.harness.mjs asserts that every acmart venue declares libertine, inconsolata,
+// src/tex-requirements.harness.ts asserts that every acmart venue declares libertine, inconsolata,
 // newtx, kastrup (binhex.tex) and fancyhdr — each proved by the file whose absence broke a build.
 
 // ── TEXINPUTS: WHERE THE SCRIPTS LOOK FOR `paper-guards.tex` ─────────────────

package/skills/research-ideate/SKILL.md

@@ -1,28 +1,13 @@
 ---
 name: research-ideate
 description: "Decide whether a research idea is worth doing at all — before any work goes into it. Use when someone has an idea and asks: is this worth pursuing, should we take it on, is it a paper or just a blog post, is there a quick minimal result that doesn't need a dramatic finding, will it pull us away from our main line of work. Returns a go / no-go verdict with the sharpest framing, the minimal finding and the kinds of venue that would take it. Judges the idea by what counts in a body of work: a peer-reviewed indexed publication, a reusable method or benchmark rather than a one-off \"tool X is bad\", onward citations rather than GitHub stars, and one connected line rather than scattered topics. Stage: conception, before find-venue and before any draft; hands off to find-venue, build-benchmark, draft-paper."
-allowed-tools: [Read, Write, Grep, Glob, Agent, Skill, 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, Skill]
 ---
 
-<!-- vigiles:sha256:f0ccfb74162bca40 compiled from skills/research-ideate/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:03a0131d306d7ab0 compiled from skills/research-ideate/SKILL.md.spec.ts -->
 
 # research-ideate — is this idea worth a paper, and does the paper earn authorship credit?
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs research-ideate <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 `<dir>` argument is **optional in spirit**: this skill can run before a paper directory exists, so
-pass whichever directory the work lives in, or `.`. The ledger row is written either way, and a plain
-dot is more honest than an invented path.
-
 Runs BEFORE any effort is spent. An idea can be interesting and still be a bad *publication*
 investment — the wrong framing produces something un-publishable or un-citable, which counts for
 nothing toward a body of work. This skill kills those ideas early and reshapes the survivors into the framing
@@ -87,28 +72,6 @@ Emit a compact verdict:
    e.g. "security-of-AI-coding workshop @ a top-tier security conference," "SE-measurement workshop @
    ASE/FSE," "eval/benchmark track." Hand these to `find-venue`.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record research-ideate <dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record research-ideate <dir> ABSTAINED <reason> "<one line>"
-```
-
-🔴 **There is no PASS**, so there is no way to write down "go" as a value. A clean go is the
-absence of findings across the axes, and whoever wants to call it a go says so themselves.
-
-**FINDING** — go with reshaping, where `<count>` is the number of axes that need it and
-`<report-path>` is the output. Add `--blocking` for a no-go: axis (a) is a hard stop, not a weight,
-and a no-go is the loudest finding this skill produces.
-**ABSTAINED** — `no-witness`: all axes were scored and none needed reshaping. `blocked`: the idea
-was too vague to score, which is a different thing from a no-go and must not be recorded as one.
-
-A recorded no-go is the cheapest artifact in this whole pipeline, and the one most often lost: an idea
-killed in conversation comes back three months later wearing a different name, and nothing in the repo
-remembers that it was already judged.
-
 ## Rules
 - Axis (a) is a gate, not a weight — no indexed peer review, no idea. Everything else reshapes.
 - Never justify an idea by GitHub stars, demo virality, or "it'd be a great blog post." Those don't

package/skills/research-ideate/SKILL.md.spec.ts

@@ -10,34 +10,10 @@ export default experimental_skill({
   name: "research-ideate",
   description:
     'Decide whether a research idea is worth doing at all — before any work goes into it. Use when someone has an idea and asks: is this worth pursuing, should we take it on, is it a paper or just a blog post, is there a quick minimal result that doesn\'t need a dramatic finding, will it pull us away from our main line of work. Returns a go / no-go verdict with the sharpest framing, the minimal finding and the kinds of venue that would take it. Judges the idea by what counts in a body of work: a peer-reviewed indexed publication, a reusable method or benchmark rather than a one-off "tool X is bad", onward citations rather than GitHub stars, and one connected line rather than scattered topics. Stage: conception, before find-venue and before any draft; hands off to find-venue, build-benchmark, draft-paper.',
-  tools: [
-    "Read",
-    "Write",
-    "Grep",
-    "Glob",
-    "Agent",
-    "Skill",
-    "Bash(node .claude/skills/paper-pipeline/scripts/announce.mjs:*)",
-    "Bash(node .claude/skills/paper-pipeline/scripts/ledger.mjs:*)",
-  ],
+  tools: ["Read", "Write", "Grep", "Glob", "Agent", "Skill"],
   body: `
 # research-ideate — is this idea worth a paper, and does the paper earn authorship credit?
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs research-ideate <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 \`<dir>\` argument is **optional in spirit**: this skill can run before a paper directory exists, so
-pass whichever directory the work lives in, or \`.\`. The ledger row is written either way, and a plain
-dot is more honest than an invented path.
-
 Runs BEFORE any effort is spent. An idea can be interesting and still be a bad *publication*
 investment — the wrong framing produces something un-publishable or un-citable, which counts for
 nothing toward a body of work. This skill kills those ideas early and reshapes the survivors into the framing
@@ -102,28 +78,6 @@ Emit a compact verdict:
    e.g. "security-of-AI-coding workshop @ a top-tier security conference," "SE-measurement workshop @
    ASE/FSE," "eval/benchmark track." Hand these to \`find-venue\`.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record research-ideate <dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record research-ideate <dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-🔴 **There is no PASS**, so there is no way to write down "go" as a value. A clean go is the
-absence of findings across the axes, and whoever wants to call it a go says so themselves.
-
-**FINDING** — go with reshaping, where \`<count>\` is the number of axes that need it and
-\`<report-path>\` is the output. Add \`--blocking\` for a no-go: axis (a) is a hard stop, not a weight,
-and a no-go is the loudest finding this skill produces.
-**ABSTAINED** — \`no-witness\`: all axes were scored and none needed reshaping. \`blocked\`: the idea
-was too vague to score, which is a different thing from a no-go and must not be recorded as one.
-
-A recorded no-go is the cheapest artifact in this whole pipeline, and the one most often lost: an idea
-killed in conversation comes back three months later wearing a different name, and nothing in the repo
-remembers that it was already judged.
-
 ## Rules
 - Axis (a) is a gate, not a weight — no indexed peer review, no idea. Everything else reshapes.
 - Never justify an idea by GitHub stars, demo virality, or "it'd be a great blog post." Those don't

package/skills/study-accepted-papers/SKILL.md

@@ -5,21 +5,10 @@ context: fork
 allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch, Agent]
 ---
 
-<!-- vigiles:sha256:177ca8805990361e compiled from skills/study-accepted-papers/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:e199b342e4e98338 compiled from skills/study-accepted-papers/SKILL.md.spec.ts -->
 
 # study-accepted-papers — learn the venue's bar from its own accepted corpus, then lever your draft up
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs study-accepted-papers <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.
-
 Reviewers don't score in a vacuum — they score against the papers that got in last cycle. This skill
 makes that reference standard explicit: pull the venue's **actually-accepted** papers of your type,
 extract the concrete properties that separated the strong ones from the weak-accepts, and diff your
@@ -157,28 +146,6 @@ being violated, and the **things previously believed that the corpus disproved**
 valuable lines in the file, because without them the pipeline re-derives the wrong belief). Keep it
 short enough that it survives being loaded into every session.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record study-accepted-papers <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record study-accepted-papers <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `<count>` is the number of levers, `<report-path>` the ranked CHEAP/EXPENSIVE list.
-Add `--blocking` when the draft is missing something the track *requires* (an artifact link, a named
-benchmark, a metric definition): a desk-reject, never a weak accept, and worth the loudest thing
-this skill can say.
-**ABSTAINED** — `no-witness`: the corpus was read and no lever came out of it. `input-missing`: the
-venue publishes no accepted papers to mine.
-
-🔴 **There is no PASS**, and the reason is visible here. "The draft already sits at the venue's bar"
-is only meaningful next to the corpus it was measured against — *33 of 34 accepted papers*, not
-*most of them* — and a stored acquittal carried that denominator nowhere. Put the corpus size in the
-`ABSTAINED` note and in the report; without it the row is an impression with a machine-readable
-label on it.
-
 ## Rules
 - **Fetch real accepted papers.** Never fabricate a title, author, or "what made it strong". Unverifiable → drop or mark VERIFY.
 - **A lever-proposed citation is not written into the `.tex`/bib until `verify-citations` confirms it** (real

package/skills/study-accepted-papers/SKILL.md.spec.ts

@@ -25,17 +25,6 @@ export default experimental_skill({
   body: `
 # study-accepted-papers — learn the venue's bar from its own accepted corpus, then lever your draft up
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs study-accepted-papers <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.
-
 Reviewers don't score in a vacuum — they score against the papers that got in last cycle. This skill
 makes that reference standard explicit: pull the venue's **actually-accepted** papers of your type,
 extract the concrete properties that separated the strong ones from the weak-accepts, and diff your
@@ -173,28 +162,6 @@ being violated, and the **things previously believed that the corpus disproved**
 valuable lines in the file, because without them the pipeline re-derives the wrong belief). Keep it
 short enough that it survives being loaded into every session.
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record study-accepted-papers <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record study-accepted-papers <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-**FINDING** — \`<count>\` is the number of levers, \`<report-path>\` the ranked CHEAP/EXPENSIVE list.
-Add \`--blocking\` when the draft is missing something the track *requires* (an artifact link, a named
-benchmark, a metric definition): a desk-reject, never a weak accept, and worth the loudest thing
-this skill can say.
-**ABSTAINED** — \`no-witness\`: the corpus was read and no lever came out of it. \`input-missing\`: the
-venue publishes no accepted papers to mine.
-
-🔴 **There is no PASS**, and the reason is visible here. "The draft already sits at the venue's bar"
-is only meaningful next to the corpus it was measured against — *33 of 34 accepted papers*, not
-*most of them* — and a stored acquittal carried that denominator nowhere. Put the corpus size in the
-\`ABSTAINED\` note and in the report; without it the row is an impression with a machine-readable
-label on it.
-
 ## Rules
 - **Fetch real accepted papers.** Never fabricate a title, author, or "what made it strong". Unverifiable → drop or mark VERIFY.
 - **A lever-proposed citation is not written into the \`.tex\`/bib until \`verify-citations\` confirms it** (real

package/skills/submit-paper/SKILL.md

@@ -4,21 +4,10 @@ description: End-to-end playbook for submitting a peer-reviewed paper to a doubl
 allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, WebSearch, WebFetch, Skill]
 ---
 
-<!-- vigiles:sha256:4a42424fd18098e5 compiled from skills/submit-paper/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:9e57bcb2ba1fb055 compiled from skills/submit-paper/SKILL.md.spec.ts -->
 
 # submit-paper — get a reviewed paper from "done" to "ready for review"
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs submit-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.
-
 Assumes the paper is already hardened (run `pc-panel-review` — incl. its venue-fit mode — +
 `paper-adversarial-review` first). This skill is the submission mechanics — the part that bit us with
 avoidable friction the first time. Distilled from the AgenticDev 2026 submission.
@@ -155,27 +144,6 @@ the file inside was the wrong build (340 952 B vs the real 352 357 B). It surfac
 cited `L. 166` and there was nothing to resolve the line against. A folder without a checker is a
 convention with no reader.
 
-## 8. Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record submit-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record submit-paper <paper-dir> ABSTAINED <reason> "<one line>"
-```
-
-**FINDING** — `check-deanon.sh` exited non-zero, `access` is not green, the PDF is over the limit, or
-the ready-for-review click never happened; `<count>` is the number of blocking items and
-`<report-path>` names them. Always `--blocking` — every item here stops the submission.
-**ABSTAINED** — `no-witness`: uploaded **and** marked ready for review, with the venue card or the
-submission id in the note. `blocked`: the portal account is not through moderation yet.
-
-🔴 **A saved draft must never be recorded as done — and it now cannot be.** A saved-but-not-submitted
-paper is the one failure this skill's provenance names by hand, and it was invisible to every other
-check in the pipeline. There is no constructor for "submitted"; there is only the absence of blocking
-items, plus a submission id in the note that a human can go and look up. The id IS the witness, and
-recording `no-witness` without one is the same lie in a new vocabulary.
-
 ## Compose with
 - Harden first: `pc-panel-review` (incl. its venue-fit mode), `paper-adversarial-review`, `render-paper`.
 - Publisher mechanics (camera-ready): `references/publishers/<publisher>.md`.

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

@@ -24,17 +24,6 @@ export default experimental_skill({
   body: `
 # submit-paper — get a reviewed paper from "done" to "ready for review"
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs submit-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.
-
 Assumes the paper is already hardened (run \`pc-panel-review\` — incl. its venue-fit mode — +
 \`paper-adversarial-review\` first). This skill is the submission mechanics — the part that bit us with
 avoidable friction the first time. Distilled from the AgenticDev 2026 submission.
@@ -171,27 +160,6 @@ the file inside was the wrong build (340 952 B vs the real 352 357 B). It surfac
 cited \`L. 166\` and there was nothing to resolve the line against. A folder without a checker is a
 convention with no reader.
 
-## 8. Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record submit-paper <paper-dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record submit-paper <paper-dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-**FINDING** — \`check-deanon.sh\` exited non-zero, \`access\` is not green, the PDF is over the limit, or
-the ready-for-review click never happened; \`<count>\` is the number of blocking items and
-\`<report-path>\` names them. Always \`--blocking\` — every item here stops the submission.
-**ABSTAINED** — \`no-witness\`: uploaded **and** marked ready for review, with the venue card or the
-submission id in the note. \`blocked\`: the portal account is not through moderation yet.
-
-🔴 **A saved draft must never be recorded as done — and it now cannot be.** A saved-but-not-submitted
-paper is the one failure this skill's provenance names by hand, and it was invisible to every other
-check in the pipeline. There is no constructor for "submitted"; there is only the absence of blocking
-items, plus a submission id in the note that a human can go and look up. The id IS the witness, and
-recording \`no-witness\` without one is the same lie in a new vocabulary.
-
 ## Compose with
 - Harden first: \`pc-panel-review\` (incl. its venue-fit mode), \`paper-adversarial-review\`, \`render-paper\`.
 - Publisher mechanics (camera-ready): \`references/publishers/<publisher>.md\`.

package/skills/sweep-design-space/SKILL.md

@@ -5,25 +5,10 @@ context: fork
 allowed-tools: [WebSearch, WebFetch, Read, Write, Grep, Glob, Bash, Agent]
 ---
 
-<!-- vigiles:sha256:1822c8c01e352f42 compiled from skills/sweep-design-space/SKILL.md.spec.ts -->
+<!-- vigiles:sha256:46cb38ac1731883d compiled from skills/sweep-design-space/SKILL.md.spec.ts -->
 
 # sweep-design-space — stop circling, sweep
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-```
-node .claude/skills/paper-pipeline/scripts/announce.mjs sweep-design-space <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 `<dir>` argument is **optional in spirit**: this skill can run before a paper directory exists, so
-pass whichever directory the work lives in, or `.`. The ledger row is written either way, and a plain
-dot is more honest than an invented path.
-
 A model asked for "a solution" returns the three designs nearest its training prior, then variations of
 those, then variations of the variations. The user experiences this as *"you are thinking very narrowly"* —
 and they are right. The fix is not to think harder in place; it is to **sweep named source domains on
@@ -214,28 +199,6 @@ assurance levels already exist; the question is whether anyone has carried them
 
 ---
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-```
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record sweep-design-space <dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record sweep-design-space <dir> ABSTAINED <reason> "<one line>"
-```
-
-🔴 **There is no PASS.** A sweep that turns up survivors has not certified anything; it has found
-candidates, and candidates are findings.
-
-**FINDING** — the sweep produced something to act on; `<count>` is the number of survivors and
-`<report-path>` the sweep, including the groups that yielded nothing. Add `--blocking` when the
-whole sweep died on the filters — that is the loudest thing this skill can say.
-**ABSTAINED** — `no-witness`: the sweep ran and neither found a survivor nor established that none
-exists. `blocked`: there was no problem statement to sweep against.
-
-The skill's own rules already say negative results count. The ledger is how that survives the session:
-a recorded finding names the groups that were swept, so the next sweep starts from named constructs
-instead of from memory — which is the failure mode this skill exists to break.
-
 ## Rules
 
 - **Name the forbidden options in the generation brief.** Without an explicit "do not return these"

package/skills/sweep-design-space/SKILL.md.spec.ts

@@ -24,21 +24,6 @@ export default experimental_skill({
   body: `
 # sweep-design-space — stop circling, sweep
 
-## Run me
-
-🔴 FIRST, before any other step:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/announce.mjs sweep-design-space <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 \`<dir>\` argument is **optional in spirit**: this skill can run before a paper directory exists, so
-pass whichever directory the work lives in, or \`.\`. The ledger row is written either way, and a plain
-dot is more honest than an invented path.
-
 A model asked for "a solution" returns the three designs nearest its training prior, then variations of
 those, then variations of the variations. The user experiences this as *"you are thinking very narrowly"* —
 and they are right. The fix is not to think harder in place; it is to **sweep named source domains on
@@ -229,28 +214,6 @@ assurance levels already exist; the question is whether anyone has carried them
 
 ---
 
-## Record the verdict
-
-🔴 LAST step, once the deliverable exists:
-
-\`\`\`
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record sweep-design-space <dir> FINDING <count> <report-path>
-node .claude/skills/paper-pipeline/scripts/ledger.mjs record sweep-design-space <dir> ABSTAINED <reason> "<one line>"
-\`\`\`
-
-🔴 **There is no PASS.** A sweep that turns up survivors has not certified anything; it has found
-candidates, and candidates are findings.
-
-**FINDING** — the sweep produced something to act on; \`<count>\` is the number of survivors and
-\`<report-path>\` the sweep, including the groups that yielded nothing. Add \`--blocking\` when the
-whole sweep died on the filters — that is the loudest thing this skill can say.
-**ABSTAINED** — \`no-witness\`: the sweep ran and neither found a survivor nor established that none
-exists. \`blocked\`: there was no problem statement to sweep against.
-
-The skill's own rules already say negative results count. The ledger is how that survives the session:
-a recorded finding names the groups that were swept, so the next sweep starts from named constructs
-instead of from memory — which is the failure mode this skill exists to break.
-
 ## Rules
 
 - **Name the forbidden options in the generation brief.** Without an explicit "do not return these"