pi-hashline-edit-pro 0.11.1 → 0.11.3

package/README.md

@@ -66,19 +66,14 @@ Replaces using the `HASH│content` anchors from `read` output to target lines p
 {
   "path": "src/main.ts",
   "edits": [
-    { "old_range": ["ve7", "ve7"], "new_lines": ["  console.log('hashline');"] }
+    { "hash_range_incl": ["ve7", "ve7"], "new_lines": ["  console.log('hashline');"] }
   ]
 }
 ```
-
-| Field | Purpose |
-|---|---|
-| `old_range` | Inclusive line range `[start_hash, end_hash]` (required). |
-| `new_lines` | Replacement content (one string per line). Use `[]` to delete. |
+| `hash_range_incl` | Inclusive line range `[start_hash, end_hash]` (required). |
 
 - **Request structure validation.** The request envelope (`path`, `edits`) and individual edit items are validated before any file I/O. Unknown fields, missing required fields, invalid types, and malformed anchors are rejected with `[E_BAD_SHAPE]` or `[E_BAD_REF]`.
-- **Legacy dialect rejected.** The native top-level `oldText`/`newText` (and `old_text`/`new_text`) dialect is rejected with `[E_LEGACY_SHAPE]`. The error message tells the model to call `read` first and send `{old_range: ["<START>", "<END>"], new_lines: [...]}`.
-
+- **Legacy dialect rejected.** The native top-level `oldText`/`newText` (and `old_text`/`new_text`) dialect is rejected with `[E_LEGACY_SHAPE]`. The error message tells the model to call `read` first and send `{hash_range_incl: ["<START>", "<END>"], new_lines: [...]}`.
 All edits in a single call validate against the same pre-edit snapshot and apply bottom-up, so the hashes from a single `read` call remain valid across all edits in the batch.
 
 ### Chained edits
@@ -105,7 +100,7 @@ The post-edit diff (with `+`/`-` markers) is exposed to the host UI via `details
 - **Stale anchors fail.** A hash mismatch means the file has changed since the last `read`. The error tells the model to call `read()` to get fresh anchors, then copy the 3-character HASH from each line into the next replace call.
 - **No fallback relocation.** Mismatched anchors are never silently relocated to a "close enough" line. This trades convenience for correctness.
 - **Strict patch content.** If `new_lines` contains `+HASH│` display prefixes (or `-N   ` diff rows), the edit is rejected with `[E_INVALID_PATCH]`. Bare `HASH│` content (the first 4 chars of a `new_lines` entry looking like 3 base64 chars + `│`) is also rejected with `[E_BARE_HASH_PREFIX]`. When the suspect's prefix happens to match a real file-line anchor, the error message flags that as strong evidence the model copied an anchor from the read output.
-- **Legacy dialect rejected.** The native top-level `oldText`/`newText` (and `old_text`/`new_text`) dialect is rejected with `[E_LEGACY_SHAPE]`. The error message tells the model to call `read` first and send `{old_range: ["<START>", "<END>"], new_lines: [...]}`.
+- **Legacy dialect rejected.** The native top-level `oldText`/`newText` (and `old_text`/`new_text`) dialect is rejected with `[E_LEGACY_SHAPE]`. The error message tells the model to call `read` first and send `{hash_range_incl: ["<START>", "<END>"], new_lines: [...]}`.
 - **Atomic writes.** Files are written via temp-file-then-rename to avoid corruption from interrupted writes. Symlink chains are resolved so the target file is updated without replacing the symlink. Hard-linked files are updated in place to preserve the shared inode. File permissions are preserved across atomic renames.
 - **Per-file mutation queue.** Edits queue by the canonical write target, so concurrent edits through different symlink paths still serialize onto the same underlying file.
 - **Boundary duplication warnings.** When the last line of a replacement matches the next surviving line (or the first line matches the preceding one), a warning is emitted. This catches a common LLM pattern where closing delimiters like `}`, `});`, or `} else {` are accidentally duplicated. The warning includes the surviving line's post-edit hash so the model can reference it in a follow-up edit. No autocorrection is applied — the duplicate stays in the file and the model decides whether to remove it. Raw line comparison (not trimmed) avoids false positives when indentation differs.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-hashline-edit-pro",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "description": "Strict hashline read/replace tool for pi-coding-agent with hash-anchored edits (3-char, 18-bit, perfect hashing)",
   "main": "index.ts",
   "repository": {

package/prompts/replace.md

@@ -7,10 +7,6 @@ How to use:
 1. Call `read` to get HASH anchors:
 ```
 read({ path: "src/main.ts" })
-// Returns:
-// MQX│const x = 1;
-// ZPM│const y = 2;
-// VRW│const z = 3;
 ```
 
 2. Copy the 3-character HASH (before `│`) into `hash_range_incl`:
@@ -92,7 +88,7 @@ Error recovery:
 - `[E_BAD_REF]` — malformed HASH. Re-read and try again.
 - `[E_BAD_OP]` — invalid operation (e.g. start line > end line).
 - `[E_BAD_SHAPE]` — malformed request or edit item (missing fields, wrong types, unknown fields).
-- `[E_LEGACY_SHAPE]` — old `oldText`/`newText` or `old_range` format detected. Use `{hash_range_incl, new_lines}` instead.
+- `[E_LEGACY_SHAPE]` — old `oldText`/`newText` or `old_text`/`new_text` format detected. Use `{hash_range_incl, new_lines}` instead.
 - `[E_EDIT_CONFLICT]` — two edits overlap on the same line range. Make edits non-overlapping.
 - `[E_AMBIGUOUS_ANCHOR]` — hash collision. Call `read` to get fresh anchors.
 - `[E_BARE_HASH_PREFIX]` — a `new_lines` entry starts with `HASH│`. Remove the hash prefix; keep only the literal line content that appears after `│` in `read` output. `hash_range_incl` uses hashes, `new_lines` does not.

package/src/hashline/apply.ts

@@ -256,8 +256,7 @@ export function applyEdits(
 		);
 	}
 
-	const barePrefixWarnings = assertNoBarePrefix(edits, lineIndex.fileLines, fileHashes);
-	warnings.push(...barePrefixWarnings);
+	assertNoBarePrefix(edits, lineIndex.fileLines, fileHashes);
 	warnUnicodeEsc(edits, warnings);
 
 	const orderedSpans = resSpans(

package/src/hashline/resolve.ts

@@ -187,8 +187,7 @@ export function assertNoBarePrefix(
 	edits: HEdit[],
 	fileLines: string[],
 	fileHashes: string[],
-): string[] {
-	assertAligned(fileLines, fileHashes, "assertNoBarePrefix");
+): void {
 	const suspects: { line: string; hash: string; editIndex: number; lineIndex: number }[] = [];
 	for (let editIndex = 0; editIndex < edits.length; editIndex++) {
 		const edit = edits[editIndex]!;
@@ -198,8 +197,7 @@ export function assertNoBarePrefix(
 			if (match) suspects.push({ line, hash: match[1]!, editIndex, lineIndex });
 		}
 	}
-	if (suspects.length === 0) return [];
-
+	if (suspects.length === 0) return;
 	const locations = suspects
 		.map((s) => `edit ${s.editIndex}, new_lines[${s.lineIndex}]`)
 		.join("; ");

package/src/replace-normalize.ts

@@ -31,5 +31,6 @@ export function normReq(input: unknown): unknown {
 		record.edits = coerceEditsArray(record.edits);
 	}
 
+
 	return record;
 }

package/src/replace.ts

@@ -99,7 +99,7 @@ export function assertReq(
 		throw new Error("[E_BAD_SHAPE] Edit request must be an object.");
 	}
 
-	for (const legacyKey of ["oldText", "newText", "old_text", "new_text", "start", "end", "lines", "old_range"]) {
+	for (const legacyKey of ["oldText", "newText", "old_text", "new_text", "old_range", "start", "end", "lines"]) {
 		if (has(request, legacyKey)) {
 			throw new Error(
 				`[E_LEGACY_SHAPE] "${legacyKey}" is not supported. Use {hash_range_incl: ["<START>", "<END>"], new_lines: [...]}.`