Put the main rule before the exceptions in "What every command needs"

The README section opened with the commands that need nothing and the
config commands, and reached the requirement that covers most commands
third. It now states that rule first, then lists the commands that
need less. The facts are unchanged; only the order is.

Model: fable-5-1

README.md

@@ -197,26 +197,28 @@ vaultik version
 
 ### What every command needs
 
-`completion` and `version` need nothing. `config init` needs write access to the
-config directory.
-
-These commands need a config file that exists, even an incomplete one:
-
-- `config edit`
-- `config get`
-- `config set`
-
-Every other command needs a config file that loads. See
-[Configuration](#configuration) for the checks.
-
-Every other command except `database delete` also needs these:
+Most commands need these:
 
+- A config file that loads. See [Configuration](#configuration) for the
+  checks.
 - Write access to the local index. The command creates the file, and its
   directory, when they do not exist.
-- For an `rclone://` destination, an rclone config file that defines the remote.
+- For an `rclone://` destination, an rclone config file that defines the
+  remote.
 
 Each command below lists what it needs beyond this.
 
+These commands need less:
+
+- `completion` and `version` need nothing.
+- `config init` needs write access to the config directory.
+- `database delete` needs a config file that loads. It does not open the
+  local index.
+- These need a config file that exists, even an incomplete one:
+    - `config edit`
+    - `config get`
+    - `config set`
+
 No command needs root. A backup can read only what its user can read. A restore
 sets file owners only when it runs as root.