Watchdog & passcode fallback

○ planned

Use the device passcode or OS sign-in when biometric hardware is unavailable or simply not your thing.

No biometric hardware, a sensor having a bad day, or simply a preference not to use one? SQLly falls back to your device passcode or OS account sign-in. A gate should be a deliberate pause, not a lockout.

The fallback is the same check

Touch ID and Windows Hello are conveniences on top of an OS-level identity check - the password or passcode is the credential underneath. Falling back to it is not a weaker path around the gate; it is the same gate, asked a different way. Which is why a desktop with no fingerprint reader is a first-class case here rather than an unsupported one.

Why the prompt explains itself

A verification prompt that appears with no explanation teaches you to approve prompts. SQLly says which connection and which action asked for it, so approving is a decision about something specific. If a gate ever fires when you were not doing anything, that is information worth having.

Fail closed. If no identity check is available at all - no biometrics, no passcode, an OS that cannot be asked - a gated action does not quietly proceed. The gate exists to stop the action; a broken gate stops it too, and says why.

Watchdog

The platform prompt is a system dialog, and system dialogs occasionally fail to appear. A watchdog bounds the wait: rather than leaving you looking at a frozen tab, SQLly gives up on the prompt, reports that verification could not be completed, and leaves the statement unrun and your editor exactly as it was.

Planned, alongside the native prompts themselves. See Identity gates for what is already in place.