Repository navigation
feat: schemas for recovery codes, account recovery and staged policy changes - #108
Merged
Merged
Conversation
This was referenced Oct 22, 2026
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.
Closes #105. The shared contract for epic fells-code/seamless-auth-api#386, shipping in the one v0.20 types release with #107.
Decisions (Brandon, 2026-10-22)
RecoverySessionResponseSchemacarriesrecovery: trueandnextStep: 'enroll_passkey'. The API answers403 enrollment_requiredoutside enrollment, recovery codes,/users/meand logout, and the adapters'requireAuthrefuserecovery: trueby default (fells-code/seamless-auth-server, v0.20).config_patchversion, so rollback always works.BREAK_GLASS_EMAILS); types only add thebreak_glass_sign_inevent and the dry-run count.Routes these describe (API side, fells-code/seamless-auth-api#398 #399 #401 #402 #403)
GET /recovery-codesRecoveryCodesStatusPOST /recovery-codesRecoveryCodesGeneratedPOST /recovery-codes/redeemRecoveryCodeRedeemRequestRecoverySessionResponsePOST /recovery/startAccountRecoveryStartRequestAccountRecoveryStartResponsePOST /recovery/verifyAccountRecoveryVerifyRequestAccountRecoveryStatusGET /recovery/statusAccountRecoveryStatusPOST /recovery/cancelAccountRecoveryCancelRequestPOST /recovery/completeRecoverySessionResponseGET /system-config/policyPolicyStateResponsePUT /system-config/policy/draftPolicyDraftSaveRequestPolicyDraftDELETE /system-config/policy/draftPOST /system-config/policy/publishPolicyPublishRequestPolicyVersion(409 ifexpectedVersionis stale)POST /system-config/policy/rollbackPolicyRollbackRequestPolicyVersionGET /system-config/policy/versionsPolicyVersionsResponsePOST /system-config/policy/dry-runPolicyDryRunRequestPolicyDryRunResponseRecovery codes are not a login method, so no
login_methodschange can remove them; they are gated byrecovery_codes.enabledonly.Compatibility
Everything is additive or defaulted: existing payloads parse unchanged, and
PublicSystemConfigResponseSchema's new fields are optional for servers before v0.20. Minor changeset.Checks: typecheck, lint, format:check, vitest (21 files, 323 tests), test:zod-floor (zod 4.5.0, bundler and NodeNext), build, pack (new modules present).