@r3b1s/pi-repair-layer 0.1.0 → 0.2.1

package/README.md

@@ -41,12 +41,17 @@ Plain-English first, precise meaning after — for readers new to LLM tool-calli
 ## Install
 
 ```bash
-ln -s /home/dev/Local/personal/pi-commandcode-conundrum ~/.pi/agent/extensions/pi-repair-layer
+pi install npm:@r3b1s/pi-repair-layer
 ```
 
-pi auto-discovers `~/.pi/agent/extensions/*/index.ts`. Remove the symlink to
-uninstall. pi's TUI will show a one-time warning that built-in tools were
-overridden — that is this extension working as intended.
+Or from git:
+
+```bash
+pi install git:github.com/r3b1s/pi-repair-layer
+```
+
+pi's TUI will show a one-time warning that built-in tools were overridden —
+that is this extension working as intended.
 
 At runtime pi's extension loader aliases `@earendil-works/pi-coding-agent` and
 `typebox` to the running instance's own modules, so the extension always binds

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@r3b1s/pi-repair-layer",
-  "version": "0.1.0",
+  "version": "0.2.1",
   "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",
@@ -35,8 +35,8 @@
   },
   "devDependencies": {
     "@biomejs/biome": "2.4.8",
-    "@earendil-works/pi-ai": "^0.80.3",
-    "@earendil-works/pi-coding-agent": "0.80.3",
+    "@earendil-works/pi-ai": "^0.80.6",
+    "@earendil-works/pi-coding-agent": "0.80.6",
     "@types/node": "^24.0.0",
     "eslint": "^9.25.1",
     "typescript": "^5.9.3",

package/src/repair-engine.ts

@@ -292,6 +292,14 @@ const wrapBareStringAsArray: IssueRule = (site, toolName) => {
   return `Wrapped your bare string in a single-element array for \`${String(key)}\` in tool "${toolName}". Send an array (e.g. \`["foo"]\`) next time, not a single string.`;
 };
 
+/**
+ * Stage 5 re-collects issue sites after each pass that fired a rule, so
+ * repairs that reveal nested problems (parse a stringified array, then rename
+ * aliased fields inside it) converge instead of failing. Three passes cover
+ * every known two-step combination with one pass of headroom.
+ */
+const MAX_ISSUE_PASSES = 3;
+
 // Order matters: parse before wrap, rename before drop.
 const ISSUE_RULES: readonly [string, IssueRule][] = [
   ["renameAliasedField", renameAliasedField],
@@ -456,16 +464,28 @@ export function repairToolInput(options: {
   }
 
   // Stage 5: per-issue repairs at the strict validator's failure sites.
-  if (!schemaAccepts(schema, current)) {
+  // Iterates because one repair can expose sites the first collection couldn't
+  // see — e.g. parsing a stringified `edits` array surfaces aliased fields
+  // inside the parsed elements. Stops when the value validates or a full pass
+  // fires nothing (each firing rule mutates `current`, so a firing pass always
+  // makes progress); the cap only bounds pathological rule interactions.
+  for (
+    let pass = 0;
+    pass < MAX_ISSUE_PASSES && !schemaAccepts(schema, current);
+    pass++
+  ) {
+    let repairedThisPass = false;
     for (const site of collectIssueSites(schema, current)) {
       for (const [name, rule] of ISSUE_RULES) {
         const note = rule(site, toolName, config);
         if (note !== false) {
           fire(name, note);
+          repairedThisPass = true;
           break;
         }
       }
     }
+    if (!repairedThisPass) break;
   }
 
   // Stage 6: final verdict, now through pi's own pipeline (Convert, then