sqlite3: align -init guard with the no-SQL guard's null check

`options.init` is `string | null`. Using `!== null` (instead of a
truthy check) means `-init ""` actually attempts the read and surfaces
a clear "cannot open" error, matching the no-SQL guard below which
already treats an explicit empty string as "provided".

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: subsetpark

packages/just-bash/src/commands/sqlite3/sqlite3.ts

@@ -540,7 +540,11 @@ export const sqlite3Command: Command = {
     if (options.cmd) {
       sql = options.cmd + (sql ? `; ${sql}` : "");
     }
-    if (options.init) {
+    // `options.init` is `string | null`. Use `!== null` (not falsiness) so
+    // `-init ""` attempts the read and surfaces a clear error, instead of
+    // silently skipping. This matches the no-SQL guard below, which also
+    // treats an explicit empty string as "provided".
+    if (options.init !== null) {
       try {
         const initPath = ctx.fs.resolvePath(ctx.cwd, options.init);
         const initContent = await ctx.fs.readFile(initPath);