Report deletes as directory relative paths

docs/exception-message-format.md

@@ -32,6 +32,8 @@ Then zero or more categorized sections, each listing file pairs:
  * **InlineNew** - an [inline snapshot](inline-snapshots.md) with no expected value yet.
  * **InlineNotEqual** - an inline snapshot whose expected value differs from the result.
 
+File paths in these sections are relative to the reported directory, and keep any subdirectory. `UseUniqueDirectory` and `VerifyDirectory` place snapshots in a subdirectory, so combining the reported directory with the listed path is what rebuilds the full path.
+
 Inline entries use a different shape: a `Source:` line with the absolute source file path and 1 based line number (`path:line`), followed by optional absolute staged file paths:
 
 ```
@@ -242,7 +244,7 @@ static Result ParseExceptionMessage(string exceptionMessage)
     return result;
 }
 ```
-<sup><a href='/src/Verify.ExceptionParsing.Tests/ExceptionParsingTests.cs#L291-L311' title='Snippet source file'>snippet source</a> | <a href='#snippet-ExceptionParsing' title='Start of snippet'>anchor</a></sup>
+<sup><a href='/src/Verify.ExceptionParsing.Tests/ExceptionParsingTests.cs#L304-L324' title='Snippet source file'>snippet source</a> | <a href='#snippet-ExceptionParsing' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The `Result` contains:

docs/mdsource/exception-message-format.source.md

@@ -25,6 +25,8 @@ Then zero or more categorized sections, each listing file pairs:
  * **InlineNew** - an [inline snapshot](inline-snapshots.md) with no expected value yet.
  * **InlineNotEqual** - an inline snapshot whose expected value differs from the result.
 
+File paths in these sections are relative to the reported directory, and keep any subdirectory. `UseUniqueDirectory` and `VerifyDirectory` place snapshots in a subdirectory, so combining the reported directory with the listed path is what rebuilds the full path.
+
 Inline entries use a different shape: a `Source:` line with the absolute source file path and 1 based line number (`path:line`), followed by optional absolute staged file paths:
 
 ```

src/Verify.ExceptionParsing.Tests/ExceptionParsingTests.DeleteInSubDirectory.verified.txt

@@ -0,0 +1,12 @@
+{
+  message:
+Directory: {ProjectDirectory}
+Delete:
+  - TheType.TheMethod\old.verified.txt
+,
+  result: {
+    Delete: [
+      {ProjectDirectory}TheType.TheMethod\old.verified.txt
+    ]
+  }
+}

src/Verify.ExceptionParsing.Tests/ExceptionParsingTests.cs

@@ -199,6 +199,19 @@ public Task SingleDelete()
         return ParseVerify([], [], delete, []);
     }
 
+    // UseUniqueDirectory and VerifyDirectory put the verified files in a subdirectory
+    // of the reported directory, so the parse has to give the subdirectory back
+    [Fact]
+    public Task DeleteInSubDirectory()
+    {
+        var delete = new List<string>
+        {
+            Path.Combine(projectDirectory, "TheType.TheMethod", "old.verified.txt")
+        };
+
+        return ParseVerify([], [], delete, []);
+    }
+
     [Fact]
     public Task ParseInlineNew()
     {

src/Verify.ExceptionParsing.Tests/VerifyExceptionMessageBuilderTests.DeleteInSubDirectory.verified.txt

@@ -0,0 +1,3 @@
+Directory: {ProjectDirectory}
+Delete:
+  - TheType.TheMethod\old.verified.txt

src/Verify.ExceptionParsing.Tests/VerifyExceptionMessageBuilderTests.cs

@@ -88,6 +88,16 @@ public Task SingleDelete() =>
             delete: [fakeReceivedTextFile],
             equal: []);
 
+    // UseUniqueDirectory and VerifyDirectory put the verified files in a subdirectory
+    // of the reported directory, which a file name would drop
+    [Fact]
+    public Task DeleteInSubDirectory() =>
+        BuildVerify(
+            @new: [],
+            notEquals: [],
+            delete: [Path.Combine(projectDirectory, "TheType.TheMethod", "old.verified.txt")],
+            equal: []);
+
     [Fact]
     public Task SingleEqual() =>
         BuildVerify(

src/Verify/Verifier/VerifyExceptionMessageBuilder.cs

@@ -59,7 +59,10 @@ public static string Build(
             builder.AppendLineN("Delete:");
             foreach (var file in delete)
             {
-                builder.AppendLineN($"  - {Path.GetFileName(file)}");
+                // directory relative, like the other sections, so the parser can
+                // rebuild the path. UseUniqueDirectory and VerifyDirectory put the
+                // verified files in a subdirectory, which a file name would drop.
+                builder.AppendLineN($"  - {IoHelpers.GetRelativePath(directory, file)}");
             }
         }
 

src/todo.md

@@ -53,7 +53,7 @@ All six resolved 2026-08-16 (five fixed here; the inline item resolved as by-des
 - [ ] **MSTest overloaded test methods resolve to the wrong `MethodInfo`.**
   `Verify.MSTest/TestExecutionContext.cs:24-30` — `FindMethod` returns the first name match, ignoring parameters. With two `[DataRow]` overloads of one name, the parameter-count guard in `Verifier.BuildVerifier` mismatches for one of them → `SetParameters` silently skipped → both overloads collide on one snapshot prefix.
 
-- [ ] **`Delete:` section drops subdirectories, breaking the parse round-trip.**
+- [x] **`Delete:` section drops subdirectories, breaking the parse round-trip.**
   `Verify/Verifier/VerifyExceptionMessageBuilder.cs:62` emits `Path.GetFileName(file)` while the other sections emit directory-relative paths, and `Verify.ExceptionParsing/Parser.cs:109` reconstructs with `Path.Combine(directory, name)`. For `UseUniqueDirectory()`/`VerifyDirectory` tests, a stale `{Directory}\Type.Method\old.verified.txt` parses back as the nonexistent `{Directory}\old.verified.txt`; same-named files in different subdirectories collapse.
 
 - [ ] **`ThrowIfVerifyHasBeenRun` blames the caller instead of the API.**