fix(chunk): auto-accepted stale batch CRCs for previously-touched chunks

- Removed error on stale CRC when a chunk was already modified by an earlier batch op; the model can only know the pre-batch checksum. - `ensure_batch_operation_target_current` now returns `Ok(true)` to signal auto-accept, skipping redundant CRC validation. - Updated prompt to clarify batched line-scoped edits are supported and to require fully qualified chunk paths.
2026-04-07 05:51:21 +02:00
parent 0d8696702f
commit 3944b0f7f5
2 changed files with 28 additions and 35 deletions
@@ -126,8 +126,8 @@ All examples reference this `read` output:
 - **MUST** include a `#CRC` suffix in `target` for every replace or delete edit.
 - **MUST** use updated chunk output from the edit response for follow-up edits.
 - **MUST** use the smallest correct target; do not rewrite siblings unnecessarily.
- **MUST NOT** invent chunk paths. Copy them from `read` output including `fn_*` prefixes. Nesting uses `.`.
+- **MUST** use the **fully qualified** chunk path. Copy the complete path shown in read output — e.g. `fn_handleTerraform.try.if_2`, never just `if_2`. Short/leaf names are ambiguous.
 - For line-scoped replace edits, use file line numbers from the `read` gutter.
- Do NOT batch multiple line-scoped replace edits on the same chunk. Combine them into one wider range or use separate calls.
+- Multiple line-scoped edits on the same chunk in one batch are fine — the engine auto-updates the checksum between operations.
 </critical>
 </output>