login: ask which account, so a bare login can add one

[ale-rinaldi]

A defect in v1.4.0, spotted by the user: "we said you add an account by running dwshell login, but the current flow can't."

The problem

The accounts feature keys an account by the email logged in — an unseen email registers a new account. But dwshell login could never see one. With an account already configured it took that email and asked only for a password:

$ dwshell login
Password:                      # …for which account? It never said.

So adding a second account required knowing to pass --user. Worse, someone typing the new account's password into that prompt would get an authentication failure with nothing pointing at the cause, because the prompt was bound to the old account's email and never named it.

The README documented the flow with --user, which works — but the flow the feature promised did not.

The fix

The email is the account's identity, so it is asked for whenever there is someone to ask, offering the configured account as the answer:

$ dwshell login
User (email) [[email protected]]: [email protected]
Password: …

• Enter accepts the default: refreshing the account you have stays one keystroke.
• Typing another email registers a second account.
• --user still answers up front.
• With no terminal nothing is asked and the default account is used, so scripts behave exactly as before.

Verification

loginUser is separated from the prompt so the decision is testable — flag wins, prompt honoured, empty answer keeps the default, no terminal never asks, nothing configured offers nothing. Then the real thing, driven through a PTY:

	result
bare login, typing a different email	second account registered, default unchanged
bare login, Enter	refreshes the default account
no terminal	no prompt, default account used

gofmt, go vet, go test -race ./... green.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MvidAFW9a2r4hTgHPW9ywG