Why: passwordless activation/recovery must redeem only into a
set-password session; account ops must not create empty stores.
Evidence: SELF go test store/server login-key and OpenExisting cases.
Impact: auth middleware gates; CLI user create defaults to activate key.
Refs: docs/svc-deploy/u4-one-time-login-key.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
login_keysmigration, nullablepassword_hash, sessionscope,OpenExisting*--open-existingreloginRequiredWhy
Implements U4 of svc unified deploy proposal (Dev task
feature/svc-deploy-u4-login-key).Evidence
SELF:
go test ./internal/store/ ./internal/server/ ./internal/app/on HEAD47463a9(also recorded in Dev task card).Impact
U1
svc userconsumes--open-existing. U5 will consume redeem HTTP. Long-livedapi_keyssemantics unchanged.Refs
docs/svc-deploy/u4-one-time-login-key.mdfeature/svc-deploy-u4-login-key,feature/svc-deploy-u1-account-bindingDo not merge — owner double-key.