pi-hashline-edit-pro 0.17.9 → 0.17.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-hashline-edit-pro",
-  "version": "0.17.9",
+  "version": "0.17.10",
   "type": "module",
   "description": "Strict hashline read/replace tool for pi-coding-agent with hash-anchored edits (3-char, 18-bit, perfect hashing)",
   "main": "index.ts",
@@ -63,6 +63,9 @@
     "vitest": "^4.1.8"
   },
   "allowScripts": {
-    "better-sqlite3@13.0.1": true
+    "better-sqlite3@13.0.1": true,
+    "@google/genai@1.52.0": true,
+    "koffi@2.16.2": true,
+    "protobufjs@7.6.4": true
   }
 }

package/prompts/read-guidelines.md

@@ -1,2 +1 @@
-- Use `read` before `replace` when you do not have current HASH anchors for the file.
-- A HASH may contain `-` as a normal alphabet character.
+- `read`: call before `replace` when you need fresh HASH anchors for a file.

package/prompts/read-snippet.md

@@ -1 +1 @@
-Read a text file and return HASH│content lines
+Read a file; each line returned as HASH│content

package/prompts/read.md

@@ -1,21 +1,3 @@
-Read a text file. Each line is returned as `HASH│content`.
+Read a text file. Each line returned as HASH│content (3-char URL-safe base64 hash). No line numbers — use the 3-char HASH to reference lines in replace calls.
 
-Key rule: line numbers are NOT part of the output. Use the 3-char HASH to reference lines in replace calls. A HASH may change when the line content changes.
-
-HASH format:
-- The HASH is 3 characters from the URL-safe base64 alphabet `A-Za-z0-9-_` (e.g. `aB3`, `4yN`, `-qk`).
-- The content after the `│` separator is the line verbatim.
-- The line number is not part of the output. Use the HASH to reference lines.
-
-Pagination:
-- Large files return a truncated preview with a pagination hint (e.g. `[Showing lines 1-100 of 500. Use offset=101 to continue.]`). Call `read` again with `offset=N` to continue.
-- Default cap: {{DEFAULT_MAX_LINES}} lines or {{DEFAULT_MAX_BYTES}}; output exceeding either is truncated. Pass `limit` to read fewer lines.
-
-File kinds:
-- Text files are returned as `HASH│content` lines.
-- Images (JPEG, PNG, GIF, WebP) are returned as visual attachments.
-- Binary files and directories are rejected with a descriptive error.
-- Empty files are returned as a single empty-line hash (`HASH│`). Use replace on that hash to insert content.
-
-Non-UTF-8 bytes:
-- UTF-8 byte-order marks (BOM) are stripped. Editing a file with a BOM rewrites it without the BOM.
+Text → HASH│content lines. Images → visual attachments. Binary/directory → rejected. Empty → HASH│ (replace to insert). Pageable with offset/limit. BOM stripped; non-UTF-8 shown as U+FFFD.

package/prompts/replace-guidelines.md

@@ -1,6 +1,2 @@
-{{MODE_PREFIX}}
-- After a successful replace, the response shows the change summary. {{AUTO_READ_GUIDANCE}}
-- On [E_STALE_ANCHOR], call read to get fresh anchors, copy the 3-character HASH of the start and end of the range into hash_range_inclusive, and retry.
-- hash_range_inclusive replaces the ENTIRE range inclusively. Every line from the first anchor through the second anchor is deleted. Only put replacement lines in content_lines — do not include lines that already exist outside the range.
-- Preserve leading whitespace exactly. The content after │ in read output includes all leading spaces and tabs — copy them into content_lines unchanged.
-- content_lines must be a native JSON array of strings, not a JSON string.
+- `replace`: Provide hash_range_inclusive [start_hash, end_hash] targeting lines by their 3-char hashes (replaces every line from first anchor through last anchor inclusively), and content_lines as a native JSON array of strings for the replacement text.
+- `replace`: preserve leading whitespace exactly as it appears after │ in read output.

package/prompts/replace.md

@@ -1,33 +1 @@
-Replace lines in a text file using HASH anchors from `read`.{{MODE_DESCRIPTION}}
-
-Workflow:
-1. Call `read` to get `HASH│content` lines for the file.
-2. Identify the range to replace using the 3-char hashes from the read output.
-3. Call `replace` with `hash_range_inclusive` (the two hashes) and `content_lines` (the new lines).
-4. On `[E_STALE_ANCHOR]`, call `read` again for fresh anchors, then retry.
-5. On success, call `read` to get fresh anchors for follow-up edits.
-
-Request structure:
-{{MODE_REQUEST_STRUCTURE}}
-
-Fields:
-- content_lines — replacement lines as a JSON array of strings. File content only — no HASH│ prefix.
-- hash_range_inclusive — [start_hash, end_hash] from read output. 3-char base64 hash only — no │ or line content.
-- path — file to edit.
-
-Examples:
-{{MODE_EXAMPLES}}
-
-Rules:
-- Anchors must be 3-char base64 hashes from the most recent read. Stale anchors fail with [E_STALE_ANCHOR].
-- The range is inclusive: every line from start_hash through end_hash is deleted.
-- Those lines are replaced with content_lines — nothing is inserted, nothing is appended.
-- content_lines is literal file content. Never include the HASH│ prefix — that goes in hash_range_inclusive.
-- content_lines must be a native JSON array of strings, not a serialized string.
-- Preserve leading whitespace exactly as it appears after │ in read output.
-- To delete lines, use content_lines: [].
-- If content_lines matches current content, the edit is a noop (file unchanged).
-{{MODE_RULES}}
-On success, the response shows the change summary. {{AUTO_READ_GUIDANCE}}
-
-Recovery: If a replace produces incorrect results, call undo_last_replace with the file path to revert.
+Replace lines in a text file using HASH anchors from read's HASH│content output.

package/prompts/undo-last-replace-guidelines.md

@@ -1,3 +1,2 @@
-- Call `undo_last_replace` with the file path to revert the last replace on that file.
-- After undoing, call `read` to get fresh anchors for a corrected replace.
-- Only the most recent replace per file is tracked — calling undo twice without an intervening replace will produce "no undo history".
+- `undo_last_replace`: call with the file path to revert the last replace on that file.
+- `undo_last_replace`: only the most recent replace per file is tracked.

package/prompts/undo-last-replace.md

@@ -1 +1 @@
-Undo the last replace operation on a file, reverting it to its previous state. Use this when a replace produced incorrect results (e.g., wrong content, duplicated lines, broken syntax). After undoing, call `read` to get fresh anchors for a corrected replace.
+Undo the last replace on a file, reverting it to its previous state. Use when a replace produced incorrect results (e.g., wrong content, duplicated lines, broken syntax).

package/src/fs-write.ts

@@ -120,6 +120,14 @@ export async function writeAtomic(
         throw error;
       }
     }
+    if (process.platform === "win32" && errCode(error) === "EPERM") {
+      try {
+        await writeFile(targetPath, content, "utf-8");
+        return;
+      } finally {
+        try { await rm(tempPath, { force: true }); } catch {}
+      }
+    }
     try { await rm(tempPath, { force: true }); } catch {}
     throw error;
   }

package/src/replace-undo.ts

@@ -40,7 +40,7 @@ export function regReplaceUndo(pi: ExtensionAPI): void {
     promptGuidelines: loadGuide("../prompts/undo-last-replace-guidelines.md"),
     parameters: Type.Object({
       path: Type.String({
-        description: "Path to the file to undo the last replace on",
+        description: "Path to the file to undo",
       }),
     }),
 

package/src/replace.ts

@@ -46,13 +46,13 @@ import { loadHashStore, type HashStore } from "./hash-store";
 
 const contentLinesSchema = Type.Array(Type.String(), {
   description:
-    "literal replacement file content, one string per line. Must not include the HASH│ prefix from read output.",
+    "Literal file content, one string per line."
 });
 
 const hashRangeInclSchema = Type.Array(
-  Type.String({ description: "anchor (3-char HASH)" }),
+  Type.String({ description: "A 3-char HASH from read output" }),
   {
-    description: "inclusive hash range to replace [start_hash, end_hash]. Each element must be the 3-character hash anchor only; do not include the │ separator or line content.",
+    description: "Inclusive [start_hash, end_hash] — pair of 3-char hashes from read output.",
     minItems: 2,
     maxItems: 2,
   },
@@ -68,8 +68,8 @@ const changeItemSchema = Type.Object(
 
 export const editToolSchema = Type.Object(
   {
-    changes: Type.Array(changeItemSchema, { description: "changes over $path" }),
-    path: Type.String({ description: "path" }),
+    changes: Type.Array(changeItemSchema, { description: "Array of edits. Each edit pairs content_lines (literal file content, one string per line) with hash_range_inclusive (inclusive [start_hash, end_hash] — pair of 3-char hashes from read output)." }),
+    path: Type.String({ description: "Path to edit" }),
   },
   { additionalProperties: false },
 );
@@ -78,7 +78,7 @@ export const flatEditToolSchema = Type.Object(
   {
     content_lines: contentLinesSchema,
     hash_range_inclusive: hashRangeInclSchema,
-    path: Type.String({ description: "path" }),
+    path: Type.String({ description: "Path to edit" }),
   },
   { additionalProperties: false },
 );
@@ -297,8 +297,7 @@ const MODE_CFG = {
     requestStructure: [
       "Flat mode:", "```json", "{ \"content_lines\": [...], \"hash_range_inclusive\": [\"aB3\", \"xY7\"], \"path\": \"...\" }", "```",
     ].join("\n"),
-    prefix: "one edit per call (flat mode)",
-    guidePrefix: "- Use `replace` with HASH anchors for all file changes. Only one edit per call.",
+    prefix: "performing one edit per call",
   },
   bulk: {
     desc: "\n\nPut all operations on one file in a single `replace` call. Stack every region into the `changes` array, even when they are far apart. Anchors within one call must all come from the same pre-edit read; the runtime applies them atomically against that one snapshot.",
@@ -310,34 +309,21 @@ const MODE_CFG = {
       "Bulk mode (default):", "```json", "{ \"changes\": [{ \"content_lines\": [...], \"hash_range_inclusive\": [\"aB3\", \"xY7\"] }], \"path\": \"...\" }", "```",
     ].join("\n"),
     prefix: "batching all changes to a file in one call",
-    guidePrefix: "- Use `replace` with HASH anchors for all file changes; batch every change to one file into a single `replace` call.",
   },
 } as const;
 
 export function buildToolDef(opts: { flat: boolean; autoRead?: boolean }): ToolDef {
   const autoRead = opts.autoRead ?? false;
-  const readGuidance = autoRead
-    ? "Anchors are provided automatically after write and replace operations when auto-read is enabled."
-    : "Call `read` to get fresh anchors for follow-up edits.";
 
   const cfg = MODE_CFG[opts.flat ? "flat" : "bulk"];
 
-  const E_DESC = loadP("../prompts/replace.md", {
-    MODE_DESCRIPTION: cfg.desc,
-    MODE_EXAMPLES: cfg.examples,
-    MODE_RULES: cfg.rules,
-    MODE_REQUEST_STRUCTURE: cfg.requestStructure,
-    AUTO_READ_GUIDANCE: readGuidance,
-  });
+  const E_DESC = loadP("../prompts/replace.md");
   const E_SNIPPET = loadP("../prompts/replace-snippet.md", {
     MODE_PREFIX: cfg.prefix,
   });
-  const E_GUIDE = loadGuide("../prompts/replace-guidelines.md", {
-    MODE_PREFIX: cfg.guidePrefix,
-    AUTO_READ_GUIDANCE: readGuidance,
-  });
+  const E_GUIDE = loadGuide("../prompts/replace-guidelines.md");
 
-  const parameters = editToolSchema;
+  const parameters = opts.flat ? flatEditToolSchema : editToolSchema;
 
   return {
     name: "replace",