Name the guarded API in ThrowIfVerifyHasBeenRun

new StackTrace(1, false) already skips the frame for the guard itself, so frame 0
is the API that called it and frame 1 is that API's caller. Reading frame 1 meant
the message named the calling test method as "The API", pointing at the wrong
place to move to a module initializer.

Author: SimonCropp

src/Verify.Tests/ThrowIfVerifyHasBeenRunTests.cs

@@ -0,0 +1,23 @@
+public class ThrowIfVerifyHasBeenRunTests
+{
+    // The message points at the API that must move to a module initializer, so it has to
+    // name that API and not the code that called it
+    [Fact]
+    public void NamesTheApi()
+    {
+        var original = InnerVerifier.verifyHasBeenRun;
+        InnerVerifier.verifyHasBeenRun = true;
+        try
+        {
+            var exception = Assert.Throws<Exception>(
+                () => VerifierSettings.IgnoreMembers<string>("TheMember"));
+
+            Assert.Contains("The API 'VerifyTests.VerifierSettings.IgnoreMembers'", exception.Message);
+            Assert.DoesNotContain(nameof(NamesTheApi), exception.Message);
+        }
+        finally
+        {
+            InnerVerifier.verifyHasBeenRun = original;
+        }
+    }
+}

src/Verify/Verifier/InnerVerifier.cs

@@ -32,8 +32,10 @@ public static void ThrowIfVerifyHasBeenRun()
             return;
         }
 
+        // The frame for this method is already skipped, so frame 0 is the guarded API.
+        // Frame 1 would be the caller of that API, which is the code being told off.
         var stackTrace = new StackTrace(1, false);
-        var method = stackTrace.GetFrame(1)!.GetMethod()!;
+        var method = stackTrace.GetFrame(0)!.GetMethod()!;
         var type = method.DeclaringType;
         throw new($"The API '{type}.{method.Name}' must be called prior to any Verify has run. Usually this is done in a [ModuleInitializer]. Verify run by: {verifyHasBeenRunBy}");
     }

src/todo.md

@@ -56,7 +56,7 @@ All six resolved 2026-08-16 (five fixed here; the inline item resolved as by-des
 - [ ] **`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.**
+- [x] **`ThrowIfVerifyHasBeenRun` blames the caller instead of the API.**
   `Verify/Verifier/InnerVerifier.cs:35-38` — `new StackTrace(1, false)` already skips the guard, so frame 0 is the guarded API; `GetFrame(1)` fetches the API's caller. The message names the user's own method as "The API". Runtime-reproduced (Debug and Release). Fix: `GetFrame(0)`.
 
 ## Minor / edge cases