@henols/c64-re-tools 0.2.2 → 0.2.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@henols/c64-re-tools",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Installer that adds the C64 reverse-engineering skills and the VICE emulator MCP server (@henols/vice-mcp) to a project.",
   "type": "module",
   "bin": {
@@ -45,7 +45,7 @@
     "installer"
   ],
   "dependencies": {
-    "@henols/vice-mcp": "0.2.2"
+    "@henols/vice-mcp": "0.2.3"
   },
   "scripts": {
     "sync-skills": "node scripts/sync-skills.mjs",

package/skills/acme-build/SKILL.md

@@ -22,6 +22,13 @@ absent `run` verb is not an omission). It contacts nothing.
 Options: `-o FILE` `--out-dir DIR` `-f FORMAT` `--setpc ADDR` `-DSYM=VAL`
 `-I DIR` `--no-report` `--json`.
 
+`-I DIR` is resolved **workspace-relative** to the project root the host
+broker was launched with — the same resolution `source`/`--out-dir` already
+go through — before it ever reaches the assembler. An absolute or escaping
+`-I` directory is refused by the seam rather than passed to ACME; this is a
+documented contract change from earlier releases, when an absolute include
+reached the assembler unchecked.
+
 ## Build
 
 ```bash
@@ -137,8 +144,7 @@ it lives in the `anno` CLI rather than here.
 
 **Dated withdrawal 2026-08-29, dated return 2026-08-31 — both halves are kept,
 because the withdrawal is the record of why the route is shaped the way it is.**
-Whole-program static disassembly was WITHDRAWN on 2026-08-29 (`D-02`/`D-14`)
-rather than left standing on an unverified reassembly claim: the removed route
+Whole-program static disassembly was WITHDRAWN on 2026-08-29 rather than left standing on an unverified reassembly claim: the removed route
 settled correctness with a transcript parser, and the recorded false pass that
 discipline exists against read `ACME not found in PATH (skipped)` / `All
 roundtrip verifications passed.` / `EXIT=0` — exit zero, an aggregate line
@@ -152,16 +158,19 @@ match on the exporter's own output.
 **The live invocation:**
 
 ```bash
-npx -y @henols/vice-mcp anno export-asm game.prg --store game.annostore --out game.a
+npx -y @henols/vice-mcp anno export-asm game.prg --store game.annostore --out game-src
 node <plugin-root>/src/mcp/vice/vice-proxy.ts anno export-asm game.prg --store game.annostore
 ```
 
 `<image>` and `--store` are **two separate arguments and neither is derived from
 the other** — the image supplies the bytes, the store supplies the names, ranges,
-typed regions and comments, and naming one does not name the other. `--out`
-defaults to a `.a` beside the **store**, not beside the image, because the export
-is a generated view of the annotations. An existing destination is refused rather
-than overwritten unless you pass `--force`.
+typed regions and comments, and naming one does not name the other. `--out` names
+a **directory** the whole export is written into, defaulting to the image's
+basename stem beside the **store**, not beside the image, because the export is a
+generated view of the annotations. The directory holds a root file that sources
+the rest, one file per annotation scope, and an `unscoped.a` for anything inside
+no scope. A non-empty destination is refused rather than overwritten unless you
+pass `--force`.
 
 **The verb writes source text and runs no assembler.** Its own second output line
 says so, in as many words:
@@ -186,18 +195,25 @@ history together; it is not restated there.
 
 ## Setup
 
-`acme` on `$PATH` is the **only** requirement. The scaffold that `new` writes
-assembles against a bare install with no standard hardware-register library —
-that's deliberate: neither a plain `~/.local/bin/acme` build nor the Debian
-trixie `apt` candidate ships one, so a scaffold that depended on it would fail
-to assemble on a fresh install (Phase 8.1 FINDING-A1).
-
-`$ACME` and the wrapper's auto-probe (`$ACME`, `/usr/local/share/acme`,
-`/usr/share/acme`, `/usr/lib/acme`, `~/.acme`) still exist and still matter —
-but only for **your own** sources that use angle-bracket includes (see
-"Writing source" above), not for the scaffold. If you have that library
-somewhere, point `$ACME` at its directory and angle-bracket includes work as
-before; if you don't, the scaffold doesn't need it.
+`acme` on `$PATH` — **on the host**, never inside a container — is the **only**
+requirement. The scaffold that `new` writes assembles against a bare install
+with no standard hardware-register library — that's deliberate: neither a
+plain `~/.local/bin/acme` build nor the Debian trixie `apt` candidate ships
+one, so a scaffold that depended on it would fail to assemble on a fresh
+install.
+
+**Route:** `scripts/acme.mjs` never spawns `acme` itself
+and never probes a container PATH for it — a container has no such PATH to
+probe (the project owner's rule of 2026-08-28). The script reaches the
+assembler only through the host-tool execution seam
+(`src/mcp/vice/host-tool.mts`'s `acme.build` allowlist entry), which runs on
+the HOST and probes the library there — the same handful of conventional
+install locations `acme.mts`'s own `findAcmeLib()` names, none of them
+documented a second time here. `$ACME` still matters for **your own** sources
+that use angle-bracket includes (see "Writing source" above), not for the
+scaffold — but set it in the environment the **host** broker process sees, not
+this script's own environment, since the probe now runs host-side inside the
+seam's executor. If you don't have that library, the scaffold doesn't need it.
 
 Re-checked against ACME release 0.97 "Zem" (31 Jan 2021). CI now assembles
 the shipped scaffold on every build with `$ACME` cleared (the "Assemble the
@@ -226,10 +242,10 @@ This one turns source into bytes. It does not restate what the others carry.
 | `scripts/acme.mjs` | The driver. Its comments are the contract for every flag above |
 | `template.a` | The scaffold `new` writes: BASIC stub with a computed `SYS`, five local hardware constants (no library needed), no `!to` |
 
-Findings that make RE faster go in `.planning/RE-FINDINGS.md` **at the moment you
-find them**, graded with `Evidence:` and `Confidence:`. Promote by re-logging with
-the new evidence, never by editing a grade in place. File-changing work enters
-through a GSD command (`/gsd-quick`).
+Record findings that make RE faster in your own project notes **at the moment you
+find them**, graded with `Evidence:` and `Confidence:`. Promote a finding by
+re-logging it with the new evidence, never by editing an old grade in place — the
+grade is only worth anything if it says what was actually known when it was written.
 
 ## Troubleshooting
 

package/skills/acme-build/scripts/acme.mjs

@@ -2,30 +2,114 @@
 // ACME -> C64 assembler driver.  Target is fixed: C64, 6510 CPU, cbm output.
 // Scope is assembling only: source in, .prg + symbol files out.  Running the
 // result on a C64 belongs to the emulator skill.
-import { spawnSync } from "node:child_process";
-import { readFileSync, writeFileSync, existsSync, mkdirSync } from "node:fs";
-import { dirname, join, basename, relative, isAbsolute } from "node:path";
+//
+// The assembler is reached ONLY through the host-tool execution seam -- the
+// project owner's rule of 2026-08-28 is that this script runs container-side,
+// `acme` lives host-side, and there is no container PATH to find it on. This file used to spawn `acme` directly (a synchronous
+// `spawnSync("acme", args, { env })`) and probed FOUR fixed HOST paths
+// (`/usr/local/share/acme`, `/usr/share/acme`, `/usr/lib/acme`, `~/.acme`)
+// for its `<...>`-include library -- both are exactly what the owner's rule
+// says cannot work from inside a container. The spawn and the library probe
+// both moved to `src/mcp/vice/host-tool.mts`'s `acme.build` allowlist entry;
+// this file now only constructs a TYPED request and reads the produced files
+// back off the shared workspace tree.
+//
+// WHAT NOT TO DO: never reintroduce a local child-process call to the
+// assembler as a fallback when the seam is unreachable -- a fallback that
+// works on the developer's own host and silently fails inside a container is
+// the exact failure this seam exists to remove. A seam refusal is reported
+// and the build fails; it is never retried by spawning `acme` here.
+import { readFileSync, writeFileSync, existsSync, mkdirSync, renameSync } from "node:fs";
+import { dirname, join, basename, relative, isAbsolute, resolve, sep } from "node:path";
 import { fileURLToPath } from "node:url";
+import { spawn } from "node:child_process";
+
+import { resolveMcpModule, refusalMessage } from "../../c64-ram-capture/scripts/mcp-module.mjs";
 
 const SELF = fileURLToPath(import.meta.url);
 const HERE = dirname(SELF);
 
-// The ACME library (<cbm/c64/vic.a> and friends) lives wherever the package put
-// it.  Probe instead of assuming; validated by a file we actually include.
-const LIB_MARKER = join("cbm", "c64", "vic.a");
-function findAcmeLib() {
-  const tried = [];
-  for (const c of [
-    process.env.ACME,
-    "/usr/local/share/acme", "/usr/share/acme", "/usr/lib/acme",
-    process.env.HOME && join(process.env.HOME, ".acme"),
-  ].filter(Boolean)) {
-    tried.push(c);
-    if (existsSync(join(c, LIB_MARKER))) return { path: c, tried };
+/** The MCP-side module this script reaches -- never imported statically
+ * (cross-package: this file ships in `@henols/c64-re-tools`, the seam client
+ * ships in `@henols/vice-mcp`), only located via the ladder and invoked with
+ * `process.execPath`, the interpreter already running this script, on an
+ * in-tree module -- not an external host binary. */
+const HOST_TOOL_CLIENT_FILE = "host-tool-client.ts";
+
+/**
+ * Invokes the host-tool execution seam for `tool`/`args`, rooted at
+ * `repoRoot` for THIS invocation's workspace-relative path resolution.
+ * Never rejects: a resolution failure, a spawn failure, or unparseable
+ * output all resolve to `{ ok: false, message }` -- the same shape a tool's
+ * own refusal uses, so a caller never needs a try/catch.
+ */
+function invokeSeam(tool, args, repoRoot) {
+  return new Promise((resolvePromise) => {
+    const resolved = resolveMcpModule(HOST_TOOL_CLIENT_FILE);
+    if (!resolved.ok) {
+      resolvePromise({ ok: false, message: refusalMessage(HOST_TOOL_CLIENT_FILE, resolved.rungs) });
+      return;
+    }
+
+    const cliArgs = [resolved.path, "run", "--tool", tool, "--args", JSON.stringify(args), "--repo-root", repoRoot];
+    let child;
+    try {
+      child = spawn(process.execPath, cliArgs, { stdio: ["ignore", "pipe", "pipe"] });
+    } catch (e) {
+      resolvePromise({ ok: false, message: e instanceof Error ? e.message : String(e) });
+      return;
+    }
+
+    let stdout = "";
+    let stderr = "";
+    child.stdout.on("data", (chunk) => { stdout += chunk.toString("utf8"); });
+    child.stderr.on("data", (chunk) => { stderr += chunk.toString("utf8"); });
+    child.on("error", (err) => resolvePromise({ ok: false, message: err.message }));
+    child.on("close", () => {
+      const lines = stdout.split("\n").filter((line) => line.trim() !== "");
+      const last = lines[lines.length - 1];
+      if (last === undefined) {
+        resolvePromise({ ok: false, message: `host-tool-client.ts produced no output${stderr ? ` (stderr: ${stderr})` : ""}` });
+        return;
+      }
+      try {
+        resolvePromise(JSON.parse(last));
+      } catch {
+        resolvePromise({ ok: false, message: `host-tool-client.ts produced non-JSON output: ${last}` });
+      }
+    });
+  });
+}
+
+/** The smallest common ancestor directory of two absolute paths -- computed,
+ * never a fixed guess, so the request's `--repo-root` for THIS invocation is
+ * always exactly big enough to contain both the source and the output
+ * directory, and no bigger. This is what keeps a build entirely outside this
+ * project's own tree (this repo's `skill-acme-build-cli.test.ts`'s own
+ * scratch directories under the SYSTEM temp dir, and CI's own
+ * `RUNNER_TEMP`-rooted scaffold check) working after the migration: the
+ * seam's `resolveWorkspacePath()` refuses any path outside its given root, so
+ * the root for one invocation is chosen to be wherever that invocation's own
+ * files actually live, never a client-supplied absolute path sent as-is. */
+function commonAncestorDir(a, b) {
+  const partsA = resolve(a).split(sep);
+  const partsB = resolve(b).split(sep);
+  const common = [];
+  for (let i = 0; i < Math.min(partsA.length, partsB.length); i++) {
+    if (partsA[i] === partsB[i]) common.push(partsA[i]);
+    else break;
   }
-  return { path: null, tried };
+  const joined = common.join(sep);
+  return joined === "" ? sep : joined;
+}
+
+/** `path.relative()`, except the "same directory" case yields `"."` rather
+ * than `""` -- the seam's `resolveWorkspacePath()` refuses an empty string,
+ * but accepts `"."` as a no-op relative reference to its own root. */
+function toRel(root, abs) {
+  const r = relative(root, abs);
+  return r === "" ? "." : r;
 }
-const ACME_LIB = findAcmeLib();
 
 // How to refer to this script in hints, from wherever we were run.
 function selfPath() {
@@ -90,54 +174,65 @@ function curateLabels(vsPath, symbols) {
   return { kept: kept.length, dropped };
 }
 
-function build(src, opts) {
+async function build(src, opts) {
   if (!existsSync(src)) die(`no such source file: ${src}`);
+
+  const srcAbs = resolve(src);
   // Side files follow the .prg, not the source: two -DVARIANT builds of one
   // source must not overwrite each other's symbol tables.
-  const prg = opts.out || join(opts.outDir || dirname(src),
-    basename(src).replace(/\.(a|asm|s)$/i, "") + ".prg");
-  const outDir = dirname(prg);
-  if (!existsSync(outDir)) mkdirSync(outDir, { recursive: true });
-  const stem = prg.replace(/\.prg$/i, "");
-
-  const args = [
-    "--cpu", "6510",              // C64: enables the 6510 illegal opcodes
-    "-f", opts.format || "cbm",   // cbm = 2-byte load address, what LOAD wants
-    "-Wtype-mismatch",            // catches a missing '#' on an immediate
-    "--strict-segments",          // overlapping segments are reported as errors
-    "--msvc",                     // machine-parseable diagnostics
-    "-v1",                        // report the address range actually emitted
-    "-o", prg,
-    "-l", `${stem}.sym`,
-    "--vicelabels", `${stem}.vs`,
-  ];
-  if (!opts.noReport) args.push("-r", `${stem}.rep`);
-  for (const d of opts.defines) args.push(`-D${d}`);
-  for (const i of opts.includes) args.push("-I", i);
-  if (opts.setpc) args.push("--setpc", opts.setpc);
-  args.push(src);
-
-  // `<cbm/c64/vic.a>` style includes resolve through the ACME env var, so set
-  // it here rather than depending on the shell environment carrying it.
-  const env = { ...process.env };
-  if (ACME_LIB.path) env.ACME = ACME_LIB.path;
-  const r = spawnSync("acme", args, { encoding: "utf8", env });
-  if (r.error) {
-    die(r.error.code === "ENOENT"
-      ? "install the ACME cross assembler and put `acme` on PATH"
-      : String(r.error));
+  const desiredPrg = opts.out
+    ? resolve(opts.out)
+    : join(resolve(opts.outDir || dirname(src)), basename(src).replace(/\.(a|asm|s)$/i, "") + ".prg");
+  const desiredOutDirAbs = dirname(desiredPrg);
+  if (!existsSync(desiredOutDirAbs)) mkdirSync(desiredOutDirAbs, { recursive: true });
+  const desiredStem = desiredPrg.replace(/\.prg$/i, "");
+
+  // Workspace-relative request construction (A-03): the root for THIS
+  // invocation is the smallest ancestor containing both the source and the
+  // output directory -- see commonAncestorDir()'s own header.
+  const repoRoot = commonAncestorDir(dirname(srcAbs), desiredOutDirAbs);
+  const autoOutDirAbs = dirname(srcAbs); // the executor's own default when outDir is omitted
+
+  const args = { source: toRel(repoRoot, srcAbs) };
+  if (desiredOutDirAbs !== autoOutDirAbs) args.outDir = toRel(repoRoot, desiredOutDirAbs);
+  if (opts.format) args.format = opts.format;
+  if (opts.setpc) args.setpc = opts.setpc;
+  if (opts.defines && opts.defines.length) args.defines = opts.defines;
+  if (opts.includes && opts.includes.length) args.includes = opts.includes;
+  if (opts.noReport) args.noReport = true;
+
+  const response = await invokeSeam("acme.build", args, repoRoot);
+
+  if (!response.ok) {
+    // A seam-level refusal (unresolvable seam, unreachable broker, a bad
+    // request) -- never a local fallback that spawns the assembler itself.
+    die(response.message);
   }
 
-  const diags = parseDiagnostics(((r.stderr || "") + (r.stdout || "")).trim());
-  if (diags.some((d) => /ACME.*environment variable/i.test(d.message))) {
-    diags.push({
-      file: null, line: null, severity: "note", zone: null,
-      message: `for <...> includes, set $ACME to the directory holding ${LIB_MARKER} ` +
-               `(looked in: ${ACME_LIB.tried.join(", ")})`,
-    });
+  // The executor always names outputs after the SOURCE's own basename (never
+  // a caller-chosen stem) -- see host-tool.mts's buildHostToolArgv(). When
+  // `-o`/`--out-dir` asked for a DIFFERENT stem (a rename, not just a
+  // different directory), the produced files are moved here to the exact
+  // requested names -- a workspace file operation, not a second copy of
+  // argv construction.
+  const autoStem = join(desiredOutDirAbs, basename(srcAbs).replace(/\.(a|asm|s)$/i, ""));
+  if (autoStem !== desiredStem) {
+    for (const ext of [".prg", ".sym", ".vs", ".rep"]) {
+      const from = `${autoStem}${ext}`;
+      const to = `${desiredStem}${ext}`;
+      if (existsSync(from) && from !== to) {
+        mkdirSync(dirname(to), { recursive: true });
+        renameSync(from, to);
+      }
+    }
   }
+
+  const stem = desiredStem;
+  const prg = desiredPrg;
+
+  const diags = parseDiagnostics((response.stderrTail || "").trim());
   const errors = diags.filter((d) => d.severity.endsWith("error"));
-  const ok = r.status === 0 && existsSync(prg);
+  const ok = response.exitStatus === 0 && existsSync(prg);
 
   let range = null, size = null, symbols = [], labels = null;
   if (ok) {
@@ -176,16 +271,16 @@ function reportBuild(res, { json }) {
 
 // -------------------------------------------------------------------- verbs
 
-function cmdBuild(argv) {
+async function cmdBuild(argv) {
   const o = parseOpts(argv);
-  const res = build(o.src, o);
+  const res = await build(o.src, o);
   reportBuild(res, o);
   process.exit(res.ok ? 0 : 1);
 }
 
-function cmdSym(argv) {
+async function cmdSym(argv) {
   const o = parseOpts(argv);
-  const res = build(o.src, { ...o, noReport: true });
+  const res = await build(o.src, { ...o, noReport: true });
   if (!res.ok) { reportBuild(res, o); process.exit(1); }
   const used = res.symbols.filter((s) => s.used).sort((a, b) => a.name.localeCompare(b.name));
   if (o.json) { console.log(JSON.stringify(used, null, 2)); return; }
@@ -199,7 +294,7 @@ function cmdNew(argv) {
   if (!path) die("usage: new <file.a>");
   if (existsSync(path)) die(`${path} already exists`);
   // template.a lives at the skill root, one level up from scripts/, by
-  // decision (D-03): only .mjs modules move into scripts/.
+  // decision: only .mjs modules move into scripts/.
   writeFileSync(path, readFileSync(join(HERE, "..", "template.a"), "utf8"));
   console.log(`wrote ${path}`);
   console.log(`next: node ${selfPath()} build ${path}`);
@@ -243,4 +338,4 @@ options: -o FILE  --out-dir DIR  -f FORMAT  --setpc ADDR  -DSYM=VAL  -I DIR
          --no-report  --json`);
   process.exit(cmd ? 1 : 0);
 }
-VERBS[cmd](rest);
+await VERBS[cmd](rest);

package/skills/acme-build/template.a

@@ -6,7 +6,7 @@
 ; No angle-bracket library includes here on purpose. Neither documented ACME
 ; provisioning route ships the standard hardware-register library - a bare
 ; `~/.local/bin/acme` install and the Debian trixie `apt` candidate were both
-; verified to lack it (Phase 8.1 FINDING-A1) - so a scaffold that depends on
+; verified to lack it - so a scaffold that depends on
 ; it fails to assemble on a fresh install. The five constants below are
 ; exactly what this scaffold's body uses, defined locally instead. If you
 ; want the full library for your own sources' angle-bracket includes, set

package/skills/c64-disk-access/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: c64-disk-access
+description: Read a Commodore .d64 disk image's directory, block allocation map, a named file's sector chain, or a named file's raw bytes, using VICE's own c1541 disk tool as the reference implementation, and audit its directory for fabricated or corrupted entries. Use when asked to list what a disk image contains, check a disk's free blocks or block allocation map, trace which sectors a named file occupies on disk, extract a named file's raw bytes from a .d64, or check whether a disk's directory entries are genuine (a cracker-fabricated filename, a corrupted first track/sector, or a cyclic directory chain).
+---
+
+# Reading C64 disk images with c1541
+
+Read-only. Six capabilities, one script, one binary (`c1541`) reached only
+through the host-tool execution seam:
+
+```bash
+S=src/skills/c64-disk-access/scripts/c1541.mjs   # from the repo root
+
+node $S bam   --image path/to/image.d64                    # block allocation map
+node $S dir   --image path/to/image.d64                    # what's on the disk
+node $S entry --image path/to/image.d64 --name FILENAME     # one directory entry's raw fields
+node $S chain --image path/to/image.d64 --name FILENAME     # a named file's sector chain
+node $S read  --image path/to/image.d64 --name FILENAME     # extract a named file's bytes
+node $S audit --image path/to/image.d64                     # find fabricated/corrupted directory entries
+```
+
+The script wraps `c1541` and nothing else — **read-only**. `bam`/`dir`/`audit`
+need only `--image`; `entry`/`chain`/`read` also need `--name`, a CBM
+filename or glob pattern (never a path). No `-format`, `-write`, `-bwrite`
+or `-delete` verb is reachable from here, deliberately: this skill only
+ever reads a disk image, never mutates one.
+
+Options: `--image PATH` `--name CBM-NAME` `--out-dir DIR` `--json`.
+
+`--out-dir` defaults to the image's own directory, exactly like
+`acme-build`'s own `--out-dir` default. Both `--image` and `--out-dir` are
+resolved **workspace-relative** to the smallest ancestor directory
+containing both, before the request ever reaches the seam — the same
+resolution `acme-build`'s `source`/`--out-dir` already go through. `--name`
+is passed straight through, never resolved as a path; a value beginning
+with `-` is refused by the seam before any child process is spawned (it
+would otherwise be read as a flag by `c1541`'s own CLI).
+
+## Directory listing
+
+```bash
+node $S dir --image game.d64 --json
+```
+
+Prints the seam's response verbatim as one line of JSON:
+
+```json
+{"ok":true,"tool":"c1541.dir","exitStatus":0,"results":[{"path":"/abs/path/game.dir.txt","sha256":"...","byteLength":123}],"stderrTail":""}
+```
+
+`results[0].path` names the listing file the seam wrote — `c1541`'s own
+`-dir` output, captured and digested.
+
+## Block allocation map
+
+```bash
+node $S bam --image game.d64 --json
+```
+
+Same response shape as `dir`; `results[0].path` names a file carrying one
+per-sector allocation row per track (a run of `*`/`.` characters, `*` for
+an allocated sector).
+
+## One directory entry's raw fields
+
+```bash
+node $S entry --image game.d64 --name FILENAME --json
+```
+
+`results[0].path` names a file carrying the entry's raw 32-byte directory
+record (as a hex dump) followed by its `T/S: <t>/<s>, <n> blocks` summary
+line. This script ALSO parses that line back and adds `firstTrack`/
+`firstSector` as numeric fields on the JSON response, purely for display —
+the file itself is still the authoritative source.
+
+## A named file's sector chain
+
+```bash
+node $S chain --image game.d64 --name FILENAME --json
+```
+
+`results[0].path` names a file listing every `(track,sector)` hop the file
+occupies, in order. A single-sector file's chain shows one hop with no
+second tuple on the arrow's right side; a multi-sector file's chain repeats
+the tuple at every hop.
+
+## Extracting a named file's bytes
+
+```bash
+node $S read --image game.d64 --name FILENAME --out-dir /scratch --json
+```
+
+Writes the file's raw bytes (unlike the other four capabilities, this one
+is NOT a captured-stdout listing — `c1541` writes the output file itself).
+`results[0]` carries that file's `path`/`sha256`/`byteLength`.
+
+## Auditing for fabricated or corrupted entries
+
+```bash
+node $S audit --image game.d64 --json
+```
+
+Composes `dir` (names and block counts), `bam` (the per-sector allocation
+map), and one `entry` call per name (each file's own claimed first track/
+sector, and its directory sector's "next directory" pointer) into a ported,
+read-only detector — no `-format`/`-write`/mutating verb, and no seventh
+`host_tool` id; this is three existing capabilities composed client-side.
+
+A directory entry is flagged `suspicious`, with **named reasons, never a
+bare boolean**, on any of:
+
+1. its block count is `0`;
+2. its first track/sector lies outside the image's own geometry (there is
+   no such track, or no such sector on that track);
+3. its first **sector** — not merely its whole track — is reported free by
+   the allocation map, meaning the file cannot really start there. This is
+   sharper than checking only whether the whole track is free, because the
+   per-sector map is available.
+
+A cyclic or self-referential directory chain (two entries claiming the same
+first track/sector, or a "next directory" pointer that refers back to a
+sector already seen — including the directory's own starting sector) stops
+being treated as new information and is reported as a top-level
+`chain_error` naming the repeated pointer, rather than looping. Every
+remaining entry is still audited afterward — a chain error on one entry
+never hides another entry's own independent flag.
+
+```json
+{"entries":[{"name":"basicstub","blocks":1,"first_track":17,"first_sector":0,"suspicious":false,"suspicious_reasons":[]}],"chain_error":null}
+```
+
+**A flag is a signal to investigate, not a verdict.** A directory entry a
+cracker fabricated for a file never actually written, a genuinely corrupted
+image, and (rarely) an unusual-but-legitimate disk layout can all produce a
+flag; this command reports what it finds, named, and leaves the
+interpretation to whoever is looking at the disk.
+
+## Failure shape
+
+A nonexistent image, a nonexistent named entry, or any other call `c1541`
+cannot service is reported as `{"ok":false,"message":"..."}` with a
+non-zero exit code — **never** a success envelope over an empty or partial
+result. `c1541` itself exits `0` even on a genuine failure (it prints its
+own `Error - ...` lines to stdout instead); the seam's own classifier, not
+the exit code, is what decides success here.
+
+## What this skill does NOT do
+
+- **No mutating verb.** `-format`/`-write`/`-bwrite`/`-delete` are never
+  reachable from this script, on the wire, or anywhere in this skill's tree
+  — only the six read-only capabilities above are exposed.
+- **No direct binary spawn.** `c1541` runs host-side; this script only ever
+  constructs a typed request and reads the produced files back off the
+  shared workspace tree — the host-tool execution seam is the only route.
+- **No emulator dependency.** This skill names no VICE emulator tool at
+  all — it works entirely on files, never on a running machine, by construction.