Login Identifier Follow-Ups

Deferred task

Rename the login form field currently posted as email to a more accurate identifier such as login or identifier.

Do not do this yet.

Handle the missing-username/login-name work first, then come back to this rename.

Why this is deferred

Right now the UI label has been corrected to "Email or username", but the request contract still posts email.

That contract is misleading, but changing it should wait until the username/login-name flow is settled so we do not churn the same path twice.

Known touchpoints for the future rename

• public_html/tpl/login-ajax.php
• public_html/process-login.php
• public_html/tpl/device-login.php
• public_html/device_login_process.php

Related follow-up review points

• Audit any login failure copy that still says "Invalid email or password."
• Review pending-account handoff naming so login_email becomes a more accurate login-identifier field where appropriate.
• Keep login_hint semantics as-is unless we intentionally broaden or rename that separately. It already represents a generic login identifier.

Current state

• Main login label already says Email or username
• Device login label already says Email or username
• Backend contract is still unchanged and still posts email