mr.zeroandClaude Opus 5
c75c5acfe2
The 0.5.1 tag build failed on the stale dummy schema, so nothing was published under that number; the fix landed a commit later. Moving a tag would have been the tidier answer — the gem contents are byte-identical, since spec/ is not in `spec.files` — but deleting the remote tag is not something I can do here, and burning a patch number is the conventional response to a burned tag anyway. 0.5.1 therefore exists in the history and in one lockfile and nowhere else. 0.5.2 is what ships. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>