Verify to connect

◐ in progress

Require an OS-native identity check before SQLly opens a connection that deserves extra care.

Require an OS-native identity check before SQLly will even open a connection. Apply it to one sensitive server or an entire client's production environment; the hierarchy does the repetitive part for you.

Where the pause lands

Before the driver dials - so before a login attempt, before the schema cache warms, before the explorer expands anything. A connection you cannot verify for is a connection that was never made, which keeps the server's own audit log clean of half-opened sessions.

# inherits down the tree, override anywhere
client:    Acme Corp   identity=connect
env:       prod        identity=connect
server:    db-01.prod  identity=inherit

When to reach for it

A shared or unattended machine. The gate is about the person, not the statement - it is the only guardrail that helps when someone else is at your keyboard.
A saved production connection you rarely use. Connecting by accident from the explorer becomes impossible rather than merely unlikely.
A customer's environment you are contractually careful with. One switch on the client covers every database filed beneath it.

Deliberately not the default. A gate on your local scratch database is friction with no payoff, and a prompt you dismiss thirty times a day stops being a security control.

In progress: the per-entity setting is stored, edited, and exported today; raising the native Touch ID / Windows Hello prompt at connect time is the remaining work.