@r3b1s/pi-repair-layer 0.4.1 → 0.4.3

package/README.md

@@ -8,6 +8,12 @@ same repair pipeline to tools in your own extension.
 
 No LLM calls. No network requests. No uploaded telemetry.
 
+### Example: Deepseek v4 Pro
+![deepseek-v4-pro](https://raw.githubusercontent.com/r3b1s/media-assets/refs/heads/main/pi-things/repair-dsv4pro.webp)
+
+### Example: GLM 5.2
+![glm-5.2](https://raw.githubusercontent.com/r3b1s/media-assets/refs/heads/main/pi-things/repair-glm5.2.webp)
+
 ## Contents
 
 - [Why use it?](#why-use-it)

package/docs/research.md

@@ -257,9 +257,19 @@ the requested module:
 
 **Why it matters:** the optional-integration recipe treats an import failure
 as "package absent" only when the code is one of these two values **and** the
-message names `@r3b1s/pi-repair-layer`; anything else rethrows so a broken
-install (a *transitive* module missing) is not silently misread as absent.
-All three observed shapes pass that discrimination.
+message names `@r3b1s/pi-repair-layer` **as a quoted module specifier** —
+matched as an opening quote immediately followed by the name
+(`'@r3b1s/pi-repair-layer`, no trailing quote so both the bare-package and
+`/pi`-subpath forms match); anything else rethrows so a broken install (a
+*transitive* module missing, e.g. `typebox`) is not silently misread as
+absent. The quote anchor matters because the jiti and compiled-binary shapes
+carry the importer path: a present-but-broken install throws
+`Cannot find module 'typebox/value' from '.../node_modules/@r3b1s/pi-repair-layer/...'`,
+which contains `@r3b1s/pi-repair-layer` only as a path segment (preceded by
+`/`, not a quote). A bare-substring match would misread that as absence; the
+quoted-specifier match rethrows it loudly. All three observed absent-package
+shapes still begin with quote-then-name and pass the discrimination.
+(Refined 2026-07-21; matcher verified by unit test against all three shapes.)
 
 ### Claim 12 — Git installs and other scopes do not resolve the shared npm siblings
 

package/docs/tool-owner-integration.md

@@ -191,6 +191,21 @@ const definition: ToolDefinition<typeof parameters> = {
   },
 };
 
+// Opening quote + name, no trailing quote: matches both the bare-package ESM
+// error (`'@r3b1s/pi-repair-layer'`) and the jiti/binary subpath error
+// (`'@r3b1s/pi-repair-layer/pi'`), while a `node_modules/...` path segment
+// (preceded by `/`, not a quote) does not read as absence.
+const REPAIR_PACKAGE_SPECIFIER_QUOTED = "'@r3b1s/pi-repair-layer";
+
+export function isRepairPackageAbsent(error: unknown): boolean {
+  const code = (error as { code?: unknown } | null)?.code;
+  const message = error instanceof Error ? error.message : String(error);
+  return (
+    (code === "MODULE_NOT_FOUND" || code === "ERR_MODULE_NOT_FOUND") &&
+    message.includes(REPAIR_PACKAGE_SPECIFIER_QUOTED)
+  );
+}
+
 async function loadRepairAdapter(): Promise<
   typeof adaptToolDefinition | undefined
 > {
@@ -198,12 +213,7 @@ async function loadRepairAdapter(): Promise<
     const repair = await import("@r3b1s/pi-repair-layer/pi");
     return repair.adaptToolDefinition;
   } catch (error) {
-    const code = (error as { code?: unknown } | null)?.code;
-    const message = error instanceof Error ? error.message : String(error);
-    const packageAbsent =
-      (code === "MODULE_NOT_FOUND" || code === "ERR_MODULE_NOT_FOUND") &&
-      message.includes("@r3b1s/pi-repair-layer");
-    if (!packageAbsent) throw error;
+    if (!isRepairPackageAbsent(error)) throw error;
     return undefined;
   }
 }
@@ -225,12 +235,16 @@ The details are load-bearing:
   `code: "MODULE_NOT_FOUND"` (jiti's require path) or
   `code: "ERR_MODULE_NOT_FOUND"` (native ESM and the compiled pi binary). But
   a *present-but-broken* install — pi-repair-layer resolvable while one of its
-  own transitive modules is not — throws the same codes naming the
-  *transitive* module. Requiring the message to name
-  `@r3b1s/pi-repair-layer` keeps a broken install loud instead of silently
-  running unwrapped while the user believes repairs are active. Match the
-  package name, not the `/pi` subpath: native ESM reports only
-  `Cannot find package '@r3b1s/pi-repair-layer'`.
+  own transitive modules (e.g. `typebox`) is not — throws the same codes
+  naming the *transitive* module, and its message embeds
+  `.../node_modules/@r3b1s/pi-repair-layer/...` as a path segment. Match the
+  package name only where it appears as an imported specifier — an opening
+  quote immediately followed by the name (`'@r3b1s/pi-repair-layer`) — so that
+  path segment does not read as absence. No trailing quote: jiti and the
+  compiled binary name the full subpath (`'@r3b1s/pi-repair-layer/pi'`) while
+  native ESM names the bare package (`'@r3b1s/pi-repair-layer'`); both start
+  with quote-then-name. This keeps a broken install loud (it rethrows) instead
+  of silently running unwrapped while the user believes repairs are active.
 - **Rethrow everything else.** Any other error is a real failure, not
   absence.
 - **Emit one stderr line when falling back.** The two branches differ in
@@ -337,7 +351,11 @@ touches is deliberately small and covered by the compatibility contract in
   current major; documented exports follow semantic versioning.
 - Absence detection semantics are part of the contract: a missing package
   surfaces with `code` `MODULE_NOT_FOUND` or `ERR_MODULE_NOT_FOUND` and a
-  message naming the requested module.
+  message naming the requested module. The recipe matches that name as a
+  quoted specifier (`'@r3b1s/pi-repair-layer`, opening quote + name), not a
+  bare substring, so the package name appearing as a `node_modules` path
+  segment in a present-but-broken install rethrows loudly rather than reading
+  as absence.
 - Unrecognized preprocessor `kind`s are ignored — never fatal, no mutation, no
   claimed change — and results are still schema-validated. Repair options
   written against a newer minor version therefore degrade to the recognized

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@r3b1s/pi-repair-layer",
-  "version": "0.4.1",
+  "version": "0.4.3",
   "description": "Tool-input repair layer for the pi coding agent: validate-then-repair for built-in tool calls, ported from the behavior of commandcode's repair layer",
   "repository": {
     "type": "git",