## What happened

After a single wrong password on the lock screen, the input field is replaced by a red **"Authentication failed (1)"** message with no visible text field, no placeholder, no cursor, and no prompt to type. The screen looks locked out / broken. In fact the input is still active and focused — the field with password dots only reappears once the user starts typing.

I hit this today and initially concluded I could not log in at all ("the text box is red and says authentication failure (1) so I cannot type anything in to login"). Clicking on the box changed nothing. Only when I started typing anyway did the dot field reveal itself and the password worked on the next attempt.

This is likely a contributor to reports of "locked out, had to reboot" (e.g. the random-failure discussion #1469): a user who gets one rejection and then sees a dead-looking red screen may not realize they can just keep typing.

## Expected behaviour

After a failed attempt, the lock screen should remain obviously usable: keep the visible input field (or placeholder text such as "Password") alongside the failure message, so it's clear typing is still accepted.

## Steps to reproduce

1. Lock the screen (`omarchy system lock`, or wait for the idle lock).
2. Type a wrong password and submit.
3. Observe: field disappears, only the red "Authentication failed (1)" message shows, with no affordance indicating input still works.
4. Type anything — the dot field reappears, confirming input was active the whole time.

## Root cause (from reading the packaged source)

In `shell/plugins/lock/LockView.qml` (~line 186), the placeholder `Text` overlays the `TextInput` and is visible whenever `passwordInput.text.length === 0`:

```qml
text: root.authenticatingPassword ? "Checking…" : (root.failureMessage.length > 0 ? root.failureMessage : root.placeholderText)
```

When `failureMessage` is set, the placeholder renders the error *instead of* the normal placeholder, so with an empty field the UI shows only the red error and no "type your password" affordance. Note `onTextChanged` does clear the failure message on the first keystroke (`if (text.length > 0 && root.failureMessage.length > 0) root.clearFailureRequested()`), which is why the field "reappears" on typing — but nothing tells the user that.

## Environment

- Omarchy: 4.0.4-1, quickshell 0.3.1-1
- Kernel 7.2.5-3-omarchy, Intel Arc B390 (xe driver), x86_64
- No fingerprint enrolled (password-only lock); PAM stack stock (`/etc/pam.d/omarchy-lock-password` matches `omarchy-apply-lock` output)
- faillock tally was 1/10 — not a faillock lockout; the same password authenticated successfully on the next attempt

## Suggested fix

Show the failure message above/below the field rather than *in place of* the placeholder, or render both (error text + "Password" placeholder) so the field visibly invites input after a failure.