Database labels
Tag each stored connection with the database it stands in for — "orders-prod", "billing" — edited in place on the Connections page. Several shadow or replica connections can carry the same label, and the run log and check pages show it. Nothing is read from a connection string; the label is all we hold.
A label is free text on a connection: the production system a set of migrations is meant to reach. Give several shadow or replica connections the same label and the run log and check pages read by what was guarded rather than by which replica happened to answer. Labels already in use are suggested as you type, so a team converges on one spelling without anyone enforcing it.
Nothing is read from a connection string to set one, and labels are never counted: plans scale on stored connections alone.
The CLI is open source and needs no account: npx bolvrk check migration.sql