geneseed 3.14.0 → 3.15.0

package/js/lib/prompt.mjs

@@ -0,0 +1,132 @@
+/**
+ * The line-mode stdin readers — `ask`, `promptLine`, `confirm`, `askChoice` over one `readLine`.
+ *
+ * MOVED OUT OF `js/maintain/setup.mjs`, which is where the Python's own owner (`_harness_setup`)
+ * put them, because two callers that are not the wizard need them: `uninstall`'s `confirm` and
+ * the web server's npm prompt. Importing them from `setup.mjs` dragged the whole wizard closure
+ * — the driver, the doctor, the diff exporter — into `uninstall` and `web` for four functions
+ * whose only dependencies are fd 0, `printOut` and `parseIntStrict`.
+ */
+import { readSync } from 'node:fs';
+
+import { printOut } from './fs.mjs';
+import { parseIntStrict } from './text.mjs';
+
+/**
+ * `_harness_setup._ask` — `input(f"{prompt}{suffix}: ").strip()`, or the default at EOF.
+ *
+ * WHY IT READS A BYTE AT A TIME. Node has no synchronous line read: `readFileSync(0)` blocks
+ * until EOF rather than until Enter, so a wizard built on it would hang on a real terminal
+ * until the user pressed Ctrl-D. Reading fd 0 one byte at a time to the first `\n` is what
+ * `input()` does, and it is the only synchronous shape that stops where Enter stops. The
+ * body arrived in P5h inside `js/maintain/uninstall.mjs`'s `confirm`, moved to `setup` when that
+ * became the second caller, and lives here now that the callers outnumber the wizard;
+ * `confirm` is built on it exactly as `_confirm` is built on `_ask` in the Python.
+ *
+ * The EOF branch is the one a piped caller sees, and it agrees with Python by two different
+ * routes that happen to produce one answer: `input()` RAISES `EOFError` and the `except`
+ * returns the default, while a zero-length read here leaves `line` empty and `|| dflt` does
+ * the same. A partial line with no trailing newline is not EOF to either — Python returns
+ * the characters and so does this.
+ *
+ * `.trim()` is `str.strip()` in every case but U+FEFF, which JS counts as whitespace and
+ * Python does not; that is a standing item of this port and not this function's to settle.
+ */
+export function ask(prompt, dflt = '') {
+  const suffix = dflt ? ` [${dflt}]` : '';
+  // `input()` writes its prompt to stdout with no newline — nothing for `printOut` to
+  // translate, and it must NOT gain one.
+  process.stdout.write(`${prompt}${suffix}: `);
+  // `?? ''` because `readLine` reports EOF-with-nothing-read as null since P6h; `_ask`
+  // catches `EOFError` and returns the default, which is what the empty string produces
+  // here through `|| dflt`. The two routes to one answer are the docblock's own point.
+  const ans = (readLine() ?? '').trim();
+  return ans || dflt;
+}
+
+/**
+ * `input(prompt)` with EOF told apart from an empty line — `null` where Python RAISES.
+ *
+ * `ask` above cannot express that difference and does not need to: its EOF and its empty
+ * answer both mean "take the default". `_web_server.serve`'s npm prompt is the first
+ * caller where they differ, and they differ dangerously — `""` is in its accepted set, so
+ * a port that read EOF as an empty line would answer YES to "run npm install now?" on
+ * every non-interactive run. The reference catches `(EOFError, KeyboardInterrupt)` and
+ * answers "n"; this returns null so the caller can.
+ *
+ * No `.trim()`: `input()` does not strip, and both callers strip for themselves.
+ */
+export function promptLine(prompt) {
+  process.stdout.write(prompt);
+  return readLine();
+}
+
+/**
+ * Fd 0 to the first `\n`, dropping a `\r` before it — the CRLF a Windows console sends.
+ *
+ * THE BYTES ARE COLLECTED AND DECODED ONCE, and that is a fix rather than a style. The
+ * version this arrived as decoded EACH BYTE on its own — `buf.toString('utf8', 0, n)` inside
+ * the loop — which turns every multi-byte character into two or three U+FFFD. It was
+ * invisible for a phase because its only caller was `confirm`, whose answer is `y` or `n`;
+ * the wizard's first non-ASCII answer is what exposed it, and the corpus caught it on the
+ * first run. Scanning for the terminators a byte at a time is still correct: `\n` and `\r`
+ * are ASCII, and no continuation byte of a UTF-8 sequence is below 0x80.
+ */
+function readLine() {
+  const buf = Buffer.alloc(1);
+  const bytes = [];
+  let eof = false;
+  for (;;) {
+    let n = 0;
+    try { n = readSync(0, buf, 0, 1, null); } catch { eof = true; break; }
+    if (n === 0) { eof = true; break; }
+    if (buf[0] === 0x0a) break;
+    if (buf[0] !== 0x0d) bytes.push(buf[0]);
+  }
+  // NULL ONLY FOR THE EMPTY EOF, which is the one case `input()` raises on. A partial line
+  // with no trailing newline is not EOF to Python — it returns the characters — and the
+  // `bytes.length` test is what keeps that arm returning a string here too.
+  if (eof && bytes.length === 0) return null;
+  return Buffer.from(bytes).toString('utf8');
+}
+
+/** `_harness_setup._confirm` — `_ask` with a Y/n suffix; the default on an empty answer. */
+export function confirm(prompt, dflt = true) {
+  const ans = ask(`${prompt} (${dflt ? 'Y/n' : 'y/N'})`).toLowerCase();
+  return ans === '' ? dflt : ans[0] === 'y';
+}
+
+/**
+ * `_harness_setup._ask_choice` — a numbered menu; the chosen KEY, or the default.
+ *
+ * THREE THINGS ABOUT THE FALLBACK ORDER, all of them observable and none of them obvious:
+ *
+ *   * The key match lives in Python's `except ValueError`, so an answer that PARSES as an
+ *     integer never reaches it. `99` against a five-option menu returns the default; it does
+ *     not go looking for an option literally named `99`.
+ *   * An in-range index wins, a parsed out-of-range index falls to the default, and only an
+ *     UNPARSEABLE answer is matched against the keys. `parseIntStrict` is what separates the second
+ *     case from the third, and it is not `Number()` — see its own docblock.
+ *   * A default that is NOT in `options` falls back to option 1. It is reachable — a deployed
+ *     `.geneseed-theme` can name a theme this checkout no longer ships — and it used to throw,
+ *     mirroring the Python reference's `StopIteration`, which crashed `geneseed setup` before
+ *     its first question. The reference is gone, so there is nothing left to fail in step
+ *     with, and returning a key that is not on the menu would hand the build a stale value.
+ */
+export function askChoice(prompt, options, dflt) {
+  if (!options.some(([k]) => k === dflt)) dflt = options[0][0];
+  printOut(`\n${prompt}:\n`);
+  options.forEach(([key, desc], i) => {
+    const label = desc ? `${key} — ${desc}` : key;
+    printOut(`  ${i + 1}) ${label}${key === dflt ? '   (default)' : ''}\n`);
+  });
+  const defaultIdx = options.findIndex(([k]) => k === dflt);
+  const raw = ask('Choose', String(defaultIdx + 1));
+  const idx = parseIntStrict(raw);
+  if (idx !== null) {
+    if (idx >= 1 && idx <= options.length) return options[idx - 1][0];
+  } else {
+    for (const [key] of options) if (raw === key) return key;
+  }
+  return dflt;
+}

package/js/lib/text.mjs

@@ -9,6 +9,8 @@
  * set than `String.trim`'s, `parseIntStrict` accepts what `Number()` does not and rejects what
  * it does, and `percentDecode` leaves a bad escape alone where `decodeURIComponent` throws.
  */
+import path from 'node:path';
+
 /**
  * `len(s)` — CODE POINTS, where `String.length` counts UTF-16 units.
  *
@@ -50,8 +52,10 @@ export const padEndToWidth = (s, width) => s + ' '.repeat(Math.max(0, width - co
  * raw environment value do it — `js/ui/cli.mjs`'s `helpWidth` and `js/web/activity.mjs` wrap
  * the argument in `stripWhitespace` first.
  *
- * Gated by a corpus in `tests/test_pure_function_parity.py` — a primitive reproduction gets
- * one owner and a corpus, never a cell (P5c).
+ * Its own corpus retired with the Python suite — a primitive reproduction gets one owner and
+ * a corpus, never a cell (P5c) — so what reaches it now is only its callers' gates:
+ * `tests/unit/wizard.test.mjs`'s choice corpus and `tests/unit/web_daemon.test.mjs`'s
+ * non-integer port.
  */
 export function parseIntStrict(s) {
   if (typeof s !== 'string' || s === '') return null;
@@ -146,8 +150,8 @@ export function stripWhitespaceEnd(s) {
  * `Buffer.toString('utf-8')` substitutes U+FFFD for an undecodable sequence, which is
  * `errors='replace'`. The two decoders can disagree on HOW MANY replacement characters a
  * truncated multi-byte sequence yields — Python's maximal-subpart rule against WHATWG's —
- * and the corpus in `tests/test_pure_function_parity.py` is where that is measured rather
- * than assumed.
+ * and the former Python corpus is where that was measured rather than assumed; nothing
+ * measures it now.
  */
 const HEX_PAIR = /^[0-9A-Fa-f]{2}$/;
 
@@ -179,3 +183,13 @@ export function percentDecode(s) {
   return res;
 }
 
+/**
+ * `Path.relative_to(base).as_posix()` — `target` relative to `base`, always `/`-separated.
+ *
+ * Here, not in `js/build/emit-common.mjs`, because the hook path (`js/hosts/hooks-context.mjs`)
+ * needs it too and must not pay for the render module to get it; this module imports nothing
+ * but `node:path`. It had been defined four times.
+ */
+export function relPosix(base, target) {
+  return path.relative(base, target).split(path.sep).join('/');
+}

package/js/lib/udiff.mjs

@@ -4,8 +4,9 @@
  * WHY A HAND-WRITTEN MATCHER RATHER THAN A LIBRARY. The diff is the ENTIRE user-visible
  * payload of `geneseed diff`: the hunks in `--full` and in the exported improvements file
  * are this file's output and nothing else's. A generic JS diff would produce a CORRECT diff
- * and a DIFFERENT one, and `tests/__snapshots__/primitives/` compares the hunks character
- * for character, so "also a valid diff" fails every cell. The alignment below IS the
+ * and a DIFFERENT one, and the former Python suite's corpus compared the hunks character for
+ * character, so "also a valid diff" failed every case (today only the `diff/--full-…` CLI cell
+ * compares hunks, and only one; see `js/inspect/diff.mjs`). The alignment below IS the
  * specification of what this tool prints, and three of its choices are choices no other
  * algorithm makes:
  *

package/js/maintain/memory.mjs

@@ -17,12 +17,11 @@
  *     beside the cwd, then the global config dir — with `--memory` as the explicit override.
  *     `status` prints the answer of that same resolver, so the two agree about which store
  *     is "the" store.
- *   * THE RESERVED-NAME CHECK IS CASE-INSENSITIVE, WHICH THE ENDPOINT'S IS NOT. It compares
- *     `MEMORY` and `README` exactly. On a case-insensitive filesystem — which is every
- *     Windows install and the default macOS one — `rm memory` then resolves to the index
- *     file, passes the guard, and deletes the thing the agent reads at session start. This
- *     is a NARROWING of what the endpoint accepts, on a destructive path, and it is the one
- *     divergence in this file that is not about resolution.
+ *   * THE RESERVED-NAME CHECK IS CASE-INSENSITIVE, and the web endpoints use this one. On a
+ *     case-insensitive filesystem — every Windows install and the default macOS one — an
+ *     exact `MEMORY`/`README` compare let `rm memory` resolve to the index file, pass the
+ *     guard, and delete the thing the agent reads at session start. The endpoint once had
+ *     that exact compare; it now calls `memoryDelete` from here.
  *
  * `memoryDropIndex` is the hook module's, not a copy: writing the fact and unwriting its
  * index line are two halves of one format, and the half that writes lives there.

package/js/maintain/migrate.mjs

@@ -3,9 +3,10 @@
  *
  * P10d, AND IT IS NOT A PORT. Every other module here reproduces a Python original byte for
  * byte; this verb is new behaviour on both sides, written twice in the same change so that
- * `tests/harness_golden.py` — a CROSS-IMPLEMENTATION gate — has a reference side at all. A
- * Node-only verb would have nothing to compare against, and `test_every_entry_verb_is_a_real_
- * harness_subcommand` plus `test_the_matrix_covers_every_verb_it_claims` would both fail it.
+ * the former Python CLI matrix — a CROSS-IMPLEMENTATION gate — had a reference side at all. A
+ * Node-only verb would have had nothing to compare against, and that suite's `test_every_entry_
+ * verb_is_a_real_harness_subcommand` plus `test_the_matrix_covers_every_verb_it_claims` would
+ * both have failed it.
  *
  * WHAT IT IS NOT: `rebuild-all`. That was the first answer and it was checked before being
  * discarded, because the re-emit really is the same engine and is reused rather than rewritten

package/js/maintain/setup.mjs

@@ -31,17 +31,17 @@
  * and a cell's stdin is a pipe. So the whole wizard is unreachable from the acceptance
  * matrix in the same way `_confirm` was in P5h — except that here it is not one branch, it
  * is the verb. The `setup/*` cells therefore gate the REFUSAL, absolutely and on both sides,
- * and everything past it is gated as a CORPUS in `tests/test_pure_function_parity.py`.
+ * and everything past it is gated as a CORPUS in `tests/unit/wizard.test.mjs`.
  *
  * The corpus is a new shape and the brief predicted the reason: a corpus over a stdin reader
- * needs a SEEDED FD, not a string. `tests/fixtures/pure_probe.{py,mjs}` are run with stdin
- * redirected from a file of answers and their WHOLE stdout compared — so the prompts, the
+ * needs a SEEDED FD, not a string. `tests/fixtures/pure_probe.mjs` is run with stdin
+ * redirected from a file of answers and its WHOLE stdout compared — so the prompts, the
  * numbered menus, the default markers, the `About to run:` line and the returned selection
  * are all one byte comparison. That is a stricter gate than a cell would have been, because
  * a cell could not have varied the answers at all.
  */
 import { spawnSync } from 'node:child_process';
-import { existsSync, readSync } from 'node:fs';
+import { existsSync } from 'node:fs';
 import path from 'node:path';
 
 import { main as driverMain, resolveOut } from '../build/driver.mjs';
@@ -57,132 +57,10 @@ import {
 } from '../hosts/installs.mjs';
 import { printOut, printErr } from '../lib/fs.mjs';
 import { which } from '../lib/paths.mjs';
+import { ask, askChoice, confirm } from '../lib/prompt.mjs';
 import { parseIntStrict } from '../lib/text.mjs';
 import { NO_WINDOW } from '../lib/proc.mjs';
 
-// --------------------------------------------------------------------------------------
-// the three readers
-// --------------------------------------------------------------------------------------
-
-/**
- * `_harness_setup._ask` — `input(f"{prompt}{suffix}: ").strip()`, or the default at EOF.
- *
- * WHY IT READS A BYTE AT A TIME. Node has no synchronous line read: `readFileSync(0)` blocks
- * until EOF rather than until Enter, so a wizard built on it would hang on a real terminal
- * until the user pressed Ctrl-D. Reading fd 0 one byte at a time to the first `\n` is what
- * `input()` does, and it is the only synchronous shape that stops where Enter stops. The
- * body arrived in P5h inside `js/maintain/uninstall.mjs`'s `confirm`; `setup` is the second caller,
- * so it moved to where the Python's own owner is — `_harness_setup` — and `confirm` is built
- * on it here exactly as `_confirm` is built on `_ask` there.
- *
- * The EOF branch is the one a piped caller sees, and it agrees with Python by two different
- * routes that happen to produce one answer: `input()` RAISES `EOFError` and the `except`
- * returns the default, while a zero-length read here leaves `line` empty and `|| dflt` does
- * the same. A partial line with no trailing newline is not EOF to either — Python returns
- * the characters and so does this.
- *
- * `.trim()` is `str.strip()` in every case but U+FEFF, which JS counts as whitespace and
- * Python does not; that is a standing item of this port and not this function's to settle.
- */
-export function ask(prompt, dflt = '') {
-  const suffix = dflt ? ` [${dflt}]` : '';
-  // `input()` writes its prompt to stdout with no newline — nothing for `printOut` to
-  // translate, and it must NOT gain one.
-  process.stdout.write(`${prompt}${suffix}: `);
-  // `?? ''` because `readLine` reports EOF-with-nothing-read as null since P6h; `_ask`
-  // catches `EOFError` and returns the default, which is what the empty string produces
-  // here through `|| dflt`. The two routes to one answer are the docblock's own point.
-  const ans = (readLine() ?? '').trim();
-  return ans || dflt;
-}
-
-/**
- * `input(prompt)` with EOF told apart from an empty line — `null` where Python RAISES.
- *
- * `ask` above cannot express that difference and does not need to: its EOF and its empty
- * answer both mean "take the default". `_web_server.serve`'s npm prompt is the first
- * caller where they differ, and they differ dangerously — `""` is in its accepted set, so
- * a port that read EOF as an empty line would answer YES to "run npm install now?" on
- * every non-interactive run. The reference catches `(EOFError, KeyboardInterrupt)` and
- * answers "n"; this returns null so the caller can.
- *
- * No `.trim()`: `input()` does not strip, and both callers strip for themselves.
- */
-export function promptLine(prompt) {
-  process.stdout.write(prompt);
-  return readLine();
-}
-
-/**
- * Fd 0 to the first `\n`, dropping a `\r` before it — the CRLF a Windows console sends.
- *
- * THE BYTES ARE COLLECTED AND DECODED ONCE, and that is a fix rather than a style. The
- * version this arrived as decoded EACH BYTE on its own — `buf.toString('utf8', 0, n)` inside
- * the loop — which turns every multi-byte character into two or three U+FFFD. It was
- * invisible for a phase because its only caller was `confirm`, whose answer is `y` or `n`;
- * the wizard's first non-ASCII answer is what exposed it, and the corpus caught it on the
- * first run. Scanning for the terminators a byte at a time is still correct: `\n` and `\r`
- * are ASCII, and no continuation byte of a UTF-8 sequence is below 0x80.
- */
-function readLine() {
-  const buf = Buffer.alloc(1);
-  const bytes = [];
-  let eof = false;
-  for (;;) {
-    let n = 0;
-    try { n = readSync(0, buf, 0, 1, null); } catch { eof = true; break; }
-    if (n === 0) { eof = true; break; }
-    if (buf[0] === 0x0a) break;
-    if (buf[0] !== 0x0d) bytes.push(buf[0]);
-  }
-  // NULL ONLY FOR THE EMPTY EOF, which is the one case `input()` raises on. A partial line
-  // with no trailing newline is not EOF to Python — it returns the characters — and the
-  // `bytes.length` test is what keeps that arm returning a string here too.
-  if (eof && bytes.length === 0) return null;
-  return Buffer.from(bytes).toString('utf8');
-}
-
-/** `_harness_setup._confirm` — `_ask` with a Y/n suffix; the default on an empty answer. */
-export function confirm(prompt, dflt = true) {
-  const ans = ask(`${prompt} (${dflt ? 'Y/n' : 'y/N'})`).toLowerCase();
-  return ans === '' ? dflt : ans[0] === 'y';
-}
-
-/**
- * `_harness_setup._ask_choice` — a numbered menu; the chosen KEY, or the default.
- *
- * THREE THINGS ABOUT THE FALLBACK ORDER, all of them observable and none of them obvious:
- *
- *   * The key match lives in Python's `except ValueError`, so an answer that PARSES as an
- *     integer never reaches it. `99` against a five-option menu returns the default; it does
- *     not go looking for an option literally named `99`.
- *   * An in-range index wins, a parsed out-of-range index falls to the default, and only an
- *     UNPARSEABLE answer is matched against the keys. `parseIntStrict` is what separates the second
- *     case from the third, and it is not `Number()` — see its own docblock.
- *   * The default's index is computed with `next(...)` and no fallback, so a default that is
- *     not in `options` raises `StopIteration` on the reference. That is reachable (a
- *     deployed install can carry a theme this checkout no longer ships) and it is mirrored
- *     as a throw rather than smoothed over: the two implementations must fail in the same
- *     place, and a silent `-1` here would be a divergence dressed as robustness.
- */
-export function askChoice(prompt, options, dflt) {
-  printOut(`\n${prompt}:\n`);
-  options.forEach(([key, desc], i) => {
-    const label = desc ? `${key} — ${desc}` : key;
-    printOut(`  ${i + 1}) ${label}${key === dflt ? '   (default)' : ''}\n`);
-  });
-  const defaultIdx = options.findIndex(([k]) => k === dflt);
-  if (defaultIdx < 0) throw new Error(`StopIteration: no option named ${dflt}`);
-  const raw = ask('Choose', String(defaultIdx + 1));
-  const idx = parseIntStrict(raw);
-  if (idx !== null) {
-    if (idx >= 1 && idx <= options.length) return options[idx - 1][0];
-  } else {
-    for (const [key] of options) if (raw === key) return key;
-  }
-  return dflt;
-}
-
 // --------------------------------------------------------------------------------------
 // the option tables
 // --------------------------------------------------------------------------------------
@@ -372,7 +250,7 @@ export function collectSetupLines() {
   const mode = askChoice('Mode', modeOptions(), inst.mode || defaultMode());
   const doctrines = askDoctrines(inst.doctrines);
   const emit = askChoice('Install mode', EMIT_OPTIONS, inst.emit || 'opencode-global');
-  const footprint = askChoice('Footprint', FOOTPRINT_OPTIONS.map(([k, d]) => [k, d]),
+  const footprint = askChoice('Footprint', FOOTPRINT_OPTIONS,
     inst.footprint || 'lean');
   let out = null;
   let root = null;
@@ -430,8 +308,8 @@ export function javaMajorOk(versionOutput, minimum = 21) {
  * `_harness_setup._lsp_prereqs` — `(label, present, hint)` for what OpenCode cannot install
  * for itself. Today that is a JDK 21+ for `jdtls`; the JS-runtime servers self-download.
  *
- * THE SECOND SPAWN ON THIS ENTRY POINT, and the reason `test_the_cli_reaches_child_process_\
- * only_where_it_is_declared` became a TABLE. `js/inspect/doctor.mjs` was the sole allowed importer
+ * THE SECOND SPAWN ON THIS ENTRY POINT, and the reason `ALLOWED_SPAWNS` in
+ * `tests/unit/hook_cli.test.mjs` became a TABLE. `js/inspect/doctor.mjs` was the sole allowed importer
  * for one binding and one argv; this is the second, and the port's rule is that the second
  * instance of anything turns a special case into a table cross-checked against the source.
  * The argv is asserted literally there, so an allow-list entry cannot be reused to start an
@@ -572,7 +450,7 @@ export function setupSummaryLines(theme, emit, out, root, ok) {
  * command the reader can type, and names one that survives the deletion.
  *
  * `theme_anim.play_line` USED TO BE THE SECOND, and P7c crossed it — `js/ui/anim.mjs`, gated by
- * `_theme_anim_cases()` in `tests/test_pure_function_parity.py`. The bare `catch` around it
+ * the theme-animation jobs in `tests/unit/wizard.test.mjs`. The bare `catch` around it
  * is the reference's own, labelled there "cosmetic only — never block a successful install",
  * and it is kept for the same reason: the animation runs AFTER the build has already
  * succeeded, so nothing it can do may change the exit code.

package/js/maintain/uninstall.mjs

@@ -17,9 +17,9 @@
  * 2. AN EMPTY DIRECTORY WAS INVISIBLE TO EVERY CELL. The ancestor-climb prune is a quarter of
  *    this verb and `_snapshot` could not see it: a port that unlinked the files and left
  *    `skills/<name>/` behind was byte-identical everywhere. Closed by a `<dirs>` column in
- *    `tests/harness_golden.py`'s snapshot rather than a per-cell expectation, because one
- *    entry closes it for all 219 cells written before it existed — `cmdTheme`'s statement
- *    order sat in the same hole. The ABSOLUTE half is a different axis and is the sixth
+ *    the CLI matrix's snapshot (`tests/helpers/cli_golden.mjs`) rather than a per-cell
+ *    expectation, because one entry closes it for all 219 cells written before it existed —
+ *    `cmdTheme`'s statement order sat in the same hole. The ABSOLUTE half is a different axis and is the sixth
  *    expectation kind, `expect_absent_files`.
  * 3. `--archive-memory` TOUCHES THE MEMORY STORE, the one thing here a user cannot rebuild.
  *    It is why `_archive_store` MOVES and never deletes, and why the Python's `memory=delete`
@@ -48,7 +48,7 @@ import {
 import path from 'node:path';
 
 import { hookRunnerEntry } from '../hosts/shim.mjs';
-import { confirm } from './setup.mjs';
+import { confirm } from '../lib/prompt.mjs';
 import {
   claudeCfg, claudeReadManifest, doctrinesOfDir, emitHostScopeOf, excludedRulesOfDir, installKind,
   installState,
@@ -374,7 +374,7 @@ export function installAgentEntry(root, kind) {
  * A cell can only ever observe the entries a seeded `opencode.json` holds, and the shape
  * that separates the two `is_absolute` rules is a Windows ROOTLESS path — which a cell CAN
  * seed but whose answer then only differs on one platform, in one branch, with no other
- * observable effect. `tests/test_pure_function_parity.py` drives the list directly.
+ * observable effect. The former Python corpus drove the list directly; nothing does now.
  */
 export function installAgentEntryOf(instr) {
   if (Array.isArray(instr)) {
@@ -732,9 +732,10 @@ export function cmdUninstall(args) {
 // ALL-OR-NOTHING IS THE PROPERTY, and it is the one a port breaks silently. A move that fails
 // puts every earlier move back and reports, leaving the install fully `active`; a port that
 // merely stopped on the failure would leave a half-gutted config dir that neither state
-// answers for. `tests/web_golden.py`'s `install/a-deactivate-whose-second-move-collides…`
-// drives it: a manifest naming a file AND its parent directory is the only shape a seeded
-// world can use to make the SECOND move collide.
+// answers for. `tests/unit/web_api.test.mjs`'s `deactivate rolls back on a failed move`
+// drives it with a file planted where the stash dir belongs, which fails the FIRST move; the
+// former web matrix's SECOND-move collision (a manifest naming a file AND its parent
+// directory) has no successor.
 
 /**
  * `_harness_mcp._move_tree` — move a file or dir, refusing an existing destination.
@@ -926,7 +927,7 @@ function restoreAll(stash, base, skip = null) {
  * The config edit is the LAST step and the only non-move mutation, so a move failure rolls
  * back cleanly with the `instructions` entry still intact. The prune climbs from each moved
  * file's PARENT so a `skills/<name>/` husk goes too — the half of this function no file
- * snapshot can see, and the reason `tests/web_golden.py` grew a `<dirs>` column in P6i.
+ * snapshot can see, and the reason the former web matrix grew a `<dirs>` column in P6i.
  */
 export function installDeactivate(root, host = 'opencode', scope = 'global') {
   if (CLAUDE_STYLE.includes(host)) return claudeDeactivate(root, scope, host);