if a rule application is found, do not increase the deletion index

[georghinkel]

Summary by MergeMonkey

• Fixes & Patches:
  • Fixes incorrect deletion index calculation that was causing wrong entries to be removed during rule application list migrations

[mergemonkeyhq]

⚡ Risk Assessment — NEEDS-TESTING

Focus areas: ChangeTracker.cs deletion index calculation · List migration entry correctness

Assessment: Bug fix in core list migration logic that affects rule application tracking.

Walkthrough

The PR fixes a bug in the ChangeTracker where the deletion index was incorrectly calculated during list migrations. When processing rule applications, the code was using 'index + indexOffset' instead of just 'index', causing wrong entries to be marked for removal. The fix corrects this and adds additional logic to handle the edge case when index is 0 and there are prior edits.

Changes

Files	Summary
Core Bug Fix in List Migration Logic AnyText/AnyText.Core/ChangeTracker.cs	Fixes deletion index to use 'index' instead of 'index + indexOffset' when rule applications are found, and adds handling for index==0 with prior edits to properly remove obsoleted entries
Test and Changelog AnyText/Tests/AnyText.Tests/Diffs/DiffParserTests.cs AnyText/AnyText.history	Adds new test file for DiffParser and records the bug fix in the changelog

Sequence Diagram

sequenceDiagram\n    participant Old as Old List\n    participant Calc as CalculateListMigrations\n    participant Fix as Index Calculation\n    participant Result as Migration Entries\n    Old->>Calc: Process rule applications\n    Calc->>Fix: Calculate deletion index\n    Fix-->>Calc: Use 'index' not 'index+indexOffset'\n    Calc->>Result: Add Remove entries with correct index\n    Note over Calc,Fix: Bug fix: was causing wrong entries to be removed

Loading

Dig Deeper With Commands

• /review <file-path> <function-optional>
• /chat <file-path> "<question>"
• /roast <file-path>

Runs only when explicitly triggered.