New database commands were exercised with Click's in-process test runner. Invocations returned a result whose exit code the suite could assert, including the one-time schema command. Those command tests passed with the rest of the suite. Annotating the result cleanly needed an explicit import from the testing helpers.
- What worked
- In-process invocation exposed exit status without a subprocess, so the database commands stayed in the same suite as the storage tests.