wood-fired-tasks 2.0.0 → 2.0.1

package/CHANGELOG.md

@@ -13,6 +13,26 @@ vulnerabilities, supply-chain pinning) are always called out under `Security`.
 
 _No changes yet._
 
+## [v2.0.1] - 2026-06-08
+
+### Fixed
+- **`tasks setup` interactive "Remote" selection no longer crashes.** Choosing
+  option **3) Remote** from the interactive setup menu threw
+  `remote onboarding requires a --remote <url> base URL.` because the menu set
+  the mode but never captured the server URL — only the `--remote <url>` flag
+  did. The interactive remote path now prompts for the base URL when it is not
+  supplied as a flag, guarded by a TTY check so non-interactive/CI callers still
+  fail fast with the same clear message instead of hanging on stdin.
+- **DB-path legacy-adopt tests are now hermetic.** `migrate-db-path.test.ts` and
+  `config-path-e2e.test.ts` exercise the "adopt `./data/tasks.db` when the OS
+  app-data DB is absent" precedence, but probed the real filesystem and so
+  failed on any dev machine where the `tasks` CLI had already created
+  `~/.local/share/wood-fired-tasks/tasks.db` (they passed on clean CI by luck).
+  `resolveMigrateDbPath`/`migrateCli` now forward the resolver's existing
+  injectable `exists` seam (default `fs.existsSync`, no behavior change), and the
+  tests inject a probe that hides the app-data DB — making the precedence-2
+  cases deterministic regardless of the developer's local state.
+
 ## [v2.0.0] - 2026-06-07
 
 The **identity auth cutover** — a breaking major. The legacy `X-API-Key`

package/dist/cli/commands/setup.js

@@ -8,7 +8,7 @@ import { resolveAssetPath } from '../../assets/resolve.js';
 import { configDir as defaultConfigDir } from '../../config/paths.js';
 import { resolvePathHint } from '../util/path-hint.js';
 import { buildNpmInvocation } from '../util/npm-spawn.js';
-import { selectFromMenu, promptSecret } from '../util/prompt.js';
+import { selectFromMenu, promptSecret, promptLine } from '../util/prompt.js';
 import { shouldPrompt } from '../prompts/interactive.js';
 import { getServiceBackend } from './service.js';
 import { runDeviceLogin } from './login.js';
@@ -719,7 +719,20 @@ export async function runSetupInteractive(options = {}) {
     // token} without a URL can't get a LOCAL install mislabeled as remote.
     if (mode === 'remote') {
         const hasToken = typeof options.token === 'string' && options.token.length > 0;
-        const hasRemote = typeof options.remote === 'string' && options.remote.length > 0;
+        let hasRemote = typeof options.remote === 'string' && options.remote.length > 0;
+        // Picking "Remote" from the interactive menu sets `mode` but NEVER the base
+        // URL — only the `--remote <url>` flag populates `options.remote`. Without
+        // this prompt the menu selection falls straight into runRemoteOnboarding,
+        // which throws 'remote onboarding requires a --remote <url> base URL.'.
+        // Prompt for it here so the menu path is usable; guarded by isInteractive()
+        // so a non-TTY / programmatic caller never hangs waiting on stdin.
+        if (!hasRemote && isInteractive()) {
+            const url = (await promptLine('Remote server base URL (e.g. http://host:3000): ', options.promptIO)).trim();
+            if (url.length > 0) {
+                options = { ...options, remote: url };
+                hasRemote = true;
+            }
+        }
         if (hasToken && hasRemote) {
             const setup = runSetup(options);
             return { mode: 'remote', oidc: null, method: 'manual-pat', ok: true, setup };

package/dist/db/migrate.d.ts

@@ -23,8 +23,12 @@ export declare function runMigrations(db: Database.Database): Promise<void>;
  * @param env - environment map (defaults to `process.env`).
  * @param cwd - base directory for resolving relative paths and probing the
  *   legacy `./data/tasks.db` (defaults to `process.cwd()`).
+ * @param exists - filesystem existence probe forwarded to the unified resolver
+ *   (defaults to `fs.existsSync`). Injectable so tests can isolate the
+ *   legacy-adopt vs app-data branches without depending on whether the real OS
+ *   app-data DB happens to exist on the dev machine running the suite.
  */
-export declare function resolveMigrateDbPath(env?: NodeJS.ProcessEnv, cwd?: string): string;
+export declare function resolveMigrateDbPath(env?: NodeJS.ProcessEnv, cwd?: string, exists?: (p: string) => boolean): string;
 /**
  * CLI entry point body: resolve the target DB path via the unified resolver
  * (env > legacy-adopt > app-data default), ensure the parent
@@ -32,4 +36,4 @@ export declare function resolveMigrateDbPath(env?: NodeJS.ProcessEnv, cwd?: stri
  *
  * Extracted from the `isMain` guard so it is directly unit-testable.
  */
-export declare function migrateCli(env?: NodeJS.ProcessEnv, cwd?: string): Promise<string>;
+export declare function migrateCli(env?: NodeJS.ProcessEnv, cwd?: string, exists?: (p: string) => boolean): Promise<string>;

package/dist/db/migrate.js

@@ -1,5 +1,6 @@
 import { Umzug } from 'umzug';
 import { mkdir } from 'fs/promises';
+import { existsSync } from 'fs';
 import { dirname, resolve, sep } from 'path';
 import { fileURLToPath, pathToFileURL } from 'url';
 import { initDatabase } from './database.js';
@@ -142,9 +143,13 @@ export async function runMigrations(db) {
  * @param env - environment map (defaults to `process.env`).
  * @param cwd - base directory for resolving relative paths and probing the
  *   legacy `./data/tasks.db` (defaults to `process.cwd()`).
+ * @param exists - filesystem existence probe forwarded to the unified resolver
+ *   (defaults to `fs.existsSync`). Injectable so tests can isolate the
+ *   legacy-adopt vs app-data branches without depending on whether the real OS
+ *   app-data DB happens to exist on the dev machine running the suite.
  */
-export function resolveMigrateDbPath(env = process.env, cwd = process.cwd()) {
-    return resolve(cwd, resolveDbPath(env, cwd));
+export function resolveMigrateDbPath(env = process.env, cwd = process.cwd(), exists = existsSync) {
+    return resolve(cwd, resolveDbPath(env, cwd, exists));
 }
 /**
  * CLI entry point body: resolve the target DB path via the unified resolver
@@ -153,8 +158,8 @@ export function resolveMigrateDbPath(env = process.env, cwd = process.cwd()) {
  *
  * Extracted from the `isMain` guard so it is directly unit-testable.
  */
-export async function migrateCli(env = process.env, cwd = process.cwd()) {
-    const dbPath = resolveMigrateDbPath(env, cwd);
+export async function migrateCli(env = process.env, cwd = process.cwd(), exists = existsSync) {
+    const dbPath = resolveMigrateDbPath(env, cwd, exists);
     // Create the parent directory (e.g. ./data, or a user-supplied path) if
     // it doesn't already exist. `recursive: true` is a no-op when present.
     await mkdir(dirname(dbPath), { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wood-fired-tasks",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "Network-wide task tracking system for Wood Fired Games",
   "keywords": [
     "task-tracker",