diff --git a/.claude/testament/2026-04-13.md b/.claude/testament/2026-04-13.md
index a180bca..a3b2fb9 100644
--- a/.claude/testament/2026-04-13.md
+++ b/.claude/testament/2026-04-13.md
@@ -1,9 +1,7 @@
-# 23:17
+# GitVersion tag-prefix for package-name@version tags
 
-This was a straightforward docs PR. Nothing technical to solve.
+## The trap: next-version conflicts with tag-prefix regex
 
-The prompt ran twice because the first worker's version didn't include the "do not commit" instruction (it was added silently after dispatch). The PM post-mortem is documented in the prompt itself.
+GitVersion applies `tag-prefix` when parsing `next-version` too, not just when matching git tags. Setting `tag-prefix: '.*@'` while `next-version: 1.0.0` is present causes a crash: "Failed to parse 1.0.0 into a Semantic Version" because `1.0.0` has no `@` to match.
 
-The second Phase 1 run found a merge conflict in `.claude/CLAUDE.md` on main that the Supreme Commander had already resolved. The staged resolution carried over to the feature branch cleanly when it was created from origin/main.
-
-No CI surprises expected. The only files changed are `README.md`, `.claude/CLAUDE.md`, and this testament.
+The fix is to remove `next-version` entirely. `next-version` is only meaningful for workflows that don't use tags to track releases. This workflow does. It was never needed.
diff --git a/GitVersion.yml b/GitVersion.yml
index 525c1c6..ee4146a 100644
--- a/GitVersion.yml
+++ b/GitVersion.yml
@@ -1,7 +1,6 @@
-next-version: 1.0.0
 increment: Patch
+tag-prefix: '.*@'
 strategies:
-- ConfiguredNextVersion
 - MergeMessage
 - TrackReleaseBranches
 - VersionInBranchName