cleanup: drop retired login and auth schema residue #308
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
status:blocked
track:api
track:auto
track:core
track:deploy
track:infra
track:ui
type:cleanup
type:docs
type:epic
type:release
type:research
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/delta#308
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent: #305
Problem
The app login flow is gone, but the active schema and setup scripts still imply password/TOTP/WebAuthn/recovery/session infrastructure.
scripts/setup.shstill asks for a password even though the seed path no longer needs app-login credentials.Current residue
users.passwordHash,totpSecret, andtotpEnabledwebauthn_credentialsrecovery_codessessionsaccountsif it is only a leftover login/OAuth table rather than the Google sync provider modelSolution
Collapse auth to the current single-owner/API-key contract:
Acceptance criteria