Repository navigation
integration.account: the sign-up helper on the server's next step - #27
Merged
Merged
Conversation
…y_after_s on errors, integration.account helper
… fields on verify results by wire name; signup-flow.cases.json conformance
…y, flow fields on client results; amended signup-flow.cases.json; an older server's 429 that names no wait stops
…used for longer; README and CHANGELOG
….3.5, from the contract
…t after a send, at least 1 s, at most 3 in a row; any 429 on a new code goes back to the held code; OtpAttemptsExhaustedError; no retry of a 429 longer than the per-try cap
…fest.sha256 from the contract (review fixes)
…er; any other 4xx to a code stops
…n and manifest.sha256 from the contract (refined action rule)
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
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.
What changes
A sign-up helper for setup wizards and agents, built on the server's new sign-up answers (contract v1 §3.7: every register / recover / rotate-key answer now says the next step).
integration.account:flowOf/actionOf(read an answer and decide the client action by the contract's rule),start/submitCode(one step per call, usable across process runs),run(the whole conversation: ask the person, show the server's sentence, follownext_step),checkKey(validate a pasted key). The person can enter a code, ask for a new code, or cancel; a new code is never sent unasked; waits respect the server (retry_after_s,resend_after_s) with a 1 s floor and at most 3 automatic waits in a row; a refused new-code request goes back to the code the person already holds while it is valid. Older servers are read into the same shape (legacy).register/verify/recover/recover_verifyresults carry the server's flow fields; every error gainsretry_after_s;OTP_ATTEMPTS_EXHAUSTEDis its own non-retryable error class; the HTTP layer no longer retries a 429 whoseRetry-Afteris longer than its per-try cap.conformance/v1/copied byte-identical from the published contract (53 sign-up cases, manual 2.3.5 texts), matchinghttps://agentchat.me/contract/v1/conformance/manifest.sha256.Verification
VALIDATION_ERRORwithparam: email, unknown pending id →EXPIREDwithnext_step: register, malformed code →param: code); the helper itself is checked end to end in the product lab after release.Risk and rollback
New module and additive fields only. The one behaviour change for existing callers: a 429 with a long
Retry-Afternow fails at once instead of after several capped retries. Rollback: revert, or stay on the previous release.