pi-hashline-edit-pro 1.0.7 → 1.0.8

package/README.md

@@ -90,7 +90,7 @@ Exactly one edit per call, with `hash_range_inclusive` and `content_lines` at th
 | Field | Description |
 | --- | --- |
 | `hash_range_inclusive` | Pair of 3-char hashes from `read` output marking the first and last line of the range to replace (inclusive). |
-| `content_lines` | Replacement content, one string per line. Use `[]` to delete the range. |
+| `content_lines` | Replacement content, one string per line; entries must not contain line breaks. Use `[]` to delete the range. |
 
 Behavior:
 
@@ -155,7 +155,7 @@ Settings live in `~/.config/pi-hashline-edit-pro/config.json`, created automatic
 
 | Code | Meaning |
 | --- | --- |
-| `[E_BAD_SHAPE]` | Request envelope or edit item has unknown, missing, or wrongly-typed fields. |
+| `[E_BAD_SHAPE]` | Request envelope or edit item has unknown, missing, or wrongly-typed fields, or a `content_lines` entry contains a line break. |
 | `[E_BAD_REF]` | An anchor in `hash_range_inclusive` is not a bare 3-char hash. |
 | `[E_STALE_ANCHOR]` | An anchor does not match any line in the current file; call `read` for fresh anchors. |
 | `[E_AMBIGUOUS_ANCHOR]` | An anchor matches multiple lines; call `read` for fresh anchors. |
@@ -183,7 +183,7 @@ The alphabet is sized for an LLM consumer: the model tokenizes rather than squin
 
 - **Stale anchors fail, per line.** A hash mismatch means that line's content changed since the last `read`. The error says so and, when only one anchor of a pair is stale, shows the current lines around the still-valid anchor so the range can be re-located without a full re-read. Mismatched anchors are never silently relocated to a "close enough" line — correctness over convenience.
 - **Autocorrection only when the intent is unambiguous**, and always visible: hash-prefix and diff-row stripping produce a warning; the boundary-duplication fix is silent because the duplicate never reaches the file. Literal content is never silently altered when the intent is ambiguous (numbered deletion rows and unified-diff lines are written verbatim).
-- **Byte-exact preservation.** UTF-8 BOMs, CRLF, LF, and CR-only line endings, file permissions, and trailing newlines survive edits and undo.
+- **Byte-exact preservation.** UTF-8 BOMs, CRLF, LF, and CR-only line endings, file permissions, and trailing newlines survive edits and undo; files with mixed line endings are normalized to a single line ending on edit.
 - **Atomic and ordered writes.** Files are written via temp-file-then-rename; symlink chains are resolved so the target is updated without replacing the symlink; hard-linked files are updated in place; concurrent edits to the same underlying file serialize through a per-target mutation queue.
 - **One edit per call.** The request shape stays `{path, hash_range_inclusive, content_lines}` from schema through validation to application; there is no batching dialect.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-hashline-edit-pro",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "type": "module",
   "description": "Strict hashline read/replace tool for pi-coding-agent with hash-anchored edits (3-char, 62-symbol, perfect hashing)",
   "main": "index.ts",

package/prompts/replace-guidelines.md

@@ -1,3 +1,4 @@
 - `replace`: hash_range_inclusive must use only anchors from the most recent read of the same file.
 - `replace`: content_lines is a native JSON array of strings — never a serialized JSON string. When copying a line from read output, remove its HASH│ prefix and keep the leading whitespace exactly as shown.
-- `replace`: minimize the replaced range — anchor only the lines that actually change; for insertions use a single-line range (e.g. the line after the insertion point) instead of a whole block, so fewer unchanged lines must be reproduced byte-exact.
+- `replace`: minimize the replaced range — anchor only the lines that actually change; for insertions use a single-line range (e.g. the line after the insertion point) instead of a whole block, so fewer unchanged lines must be reproduced byte-exact.
+- `replace`: content_lines entries are single lines — never embed a line break inside an entry; pass each line as its own array entry.

package/src/file-kind.ts

@@ -39,12 +39,6 @@ function isTextType(mimeType: string): boolean {
   return mimeType.startsWith("text/") || TEXT_TYPES.has(mimeType);
 }
 
-export type FKind =
-  | { kind: "directory" }
-  | { kind: "image"; mimeType: string }
-  | { kind: "text" }
-  | { kind: "binary"; description: string };
-
 export type LFile =
   | { kind: "directory" }
   | { kind: "image"; mimeType: string }
@@ -149,17 +143,3 @@ export async function loadFileKindAndText(
     await fileHandle.close();
   }
 }
-
-export async function classifyFileKind(filePath: string): Promise<FKind> {
-  const loaded = await loadFileKindAndText(filePath);
-  switch (loaded.kind) {
-    case "directory":
-      return loaded;
-    case "image":
-      return loaded;
-    case "binary":
-      return loaded;
-    case "text":
-      return { kind: "text" };
-  }
-}

package/src/fs-write.ts

@@ -9,8 +9,6 @@ import {
 	rm,
 	stat,
 	writeFile,
-	copyFile,
-	chmod,
 } from "fs/promises";
 import { dirname, join, parse, resolve, sep } from "path";
 import { errCode } from "./utils";
@@ -153,20 +151,6 @@ export async function writeAtomic(
     await rename(tempPath, targetPath);
     await syncDir(dir);
   } catch (error: unknown) {
-    if (errCode(error) === "EXDEV") {
-      try {
-        await copyFile(tempPath, targetPath);
-        if (existingStats) {
-          await chmod(targetPath, existingStats.mode & 0o7777);
-        }
-        await rm(tempPath, { force: true });
-        await syncDir(dir);
-        return;
-      } catch {
-        try { await rm(tempPath, { force: true }); } catch {}
-        throw error;
-      }
-    }
     if (process.platform === "win32" && errCode(error) === "EPERM") {
       try {
         await writeFile(targetPath, content, "utf-8");

package/src/hash-store.ts

@@ -324,10 +324,6 @@ export function upsertSnapshot(
   store.stmts.upsert(path, checksum, lineCount, JSON.stringify(hashes), Date.now());
 }
 
-export function deleteSnapshot(store: HashStore, path: string): void {
-  store.stmts.deleteOne(path);
-}
-
 export function upsertUndo(store: HashStore, path: string, entry: UndoRecord): void {
   store.stmts.undoUpsert(
     path,

package/src/hashline/parse.ts

@@ -46,5 +46,11 @@ export function parseText(edit: string[] | string | null): string[] {
   if (typeof edit === "string") {
     throw new Error(CONTENT_LINES_NOT_STRING_MSG);
   }
+  const lineBreakIndex = edit.findIndex((line) => /[\r\n]/.test(line));
+  if (lineBreakIndex >= 0) {
+    throw new Error(
+      `[E_BAD_SHAPE] "content_lines" entry at index ${lineBreakIndex} contains a \\r or \\n line break. Pass each line as its own array entry.`,
+    );
+  }
   return edit;
 }

package/src/replace.ts

@@ -47,7 +47,7 @@ import { loadHashStore, type HashStore } from "./hash-store";
 
 const contentLinesSchema = Type.Array(Type.String(), {
   description:
-    "Replacement content, one string per line. Use [] to delete the range."
+    "Replacement content, one string per line; entries must not contain line breaks. Use [] to delete the range."
 });
 
 const hashRangeInclSchema = Type.Array(
@@ -78,7 +78,6 @@ export type ReplaceDetails = {
   firstChangedLine?: number;
   snapshotId?: string;
   classification?: "noop";
-  structureOutline?: string[];
   metrics?: RMetrics;
 };
 

package/src/validation.ts

@@ -35,8 +35,3 @@ export function valKind(file: LFile, path: string): asserts file is { kind: "tex
 	}
 }
 
-
-export function isText(file: LFile): file is { kind: "text"; text: string; hadUtf8DecodeErrors?: true } {
-	return file.kind === "text";
-}
-