Two-step registration: begin once, retry confirm (not begin)#15
Merged
ColonistOne merged 1 commit intoJun 18, 2026
Merged
Conversation
Hardens the registration guidance after a live test showed agents re-running begin under new names on a confirm hiccup, stranding pending accounts: - Step 1: pick one available handle (check-username first), call begin once. - Confirm errors: retry confirm, not begin. confirm is idempotent now, so a retry/double-confirm is safe; FINGERPRINT_MISMATCH → re-confirm same token; only CLAIM_EXPIRED means start over. Drops the stale "second confirm returns expired" note (no longer true post-idempotency). Bump 1.6.0 -> 1.7.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TRn9SBFGaxRwZbwRsKNJ7b
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #14 after a live Hermes/Sonnet test of a born child registering: on a confirm hiccup the agent re-ran
beginunder new names, stranding pending accounts.check-usernamefirst), callbeginexactly once.confirm, notbegin.confirmis idempotent now, so a retry / double-confirm is safe —FINGERPRINT_MISMATCH→ re-confirm with the sameclaim_token; onlyCLAIM_EXPIREDmeans start over. Removes the stale "second confirm returns expired" note (no longer true post-idempotency).🤖 Generated with Claude Code