Function plan_schema 

pub fn plan_schema(command: Option<&Command>) -> SchemaPlan

Decides whether command may migrate, or must find the schema already current.

There is no third answer. Every command here reads or writes rows, so every one needs the schema; completions and man never reach this, being answered in main.rs before the configuration or the database.

The split exists because migrating used to be a side effect of opening the database, which made acme-proxy audit list an upgrade step. It also raced on SQLite: two processes starting together both ran MIGRATOR::run, and sqlx takes no migration lock there. One owner, named on the command line, removes both.