@userreason/wizard 0.3.1 → 0.3.2

package/README.md

@@ -36,7 +36,7 @@ terminal. The [first survey guide](https://docs.userreason.com/get-started/first
 walks through creating and publishing a survey. Installing the SDK does not
 publish a survey.
 
-In development mode (`--dev`), onboarding opens in the browser by default.
+Onboarding opens in the browser by default in production and development (`--dev`).
 Survey suggestions and the Agent test step are paused in production and development.
 Setup does not prepare or upload application source for recommendations, and it
 neither offers nor creates suggested drafts. The terminal flow skips the
@@ -178,7 +178,8 @@ package builds. With a published package, select the development API:
 npx -y @userreason/wizard@latest --dev
 ```
 
-Production still requires `--browser-setup`. Compatible builds also support:
+Production and development both use browser setup by default. `--browser-setup`
+remains an optional explicit alias. Compatible builds also support:
 
 ```sh
 npx -y @userreason/wizard@latest --browser-setup
@@ -220,11 +221,11 @@ skill never grants ongoing CLI access. Authorize continuing access separately
 with `userreason login --open` when wanted. Standalone CLI survey tools remain
 available outside onboarding.
 
-The production profile for wizard 0.3.1 selects `@userreason/js@0.5.3` and
+The production profile for wizard 0.3.2 selects `@userreason/js@0.5.3` and
 `@userreason/cli@0.2.1`. New installs use those exact versions; an installed
 stable patch in the same release line is reused. Earlier SDK 0.4 and CLI 0.1
-releases are upgraded when installation is selected. Browser setup still
-requires explicit `--browser-setup` and a server advertising the capability.
+releases are upgraded when installation is selected. Browser setup is the default and requires a server advertising the capability.
+Use `--terminal-setup` for the terminal flow.
 
 Browser-guided installation prints package-manager failures in the connected
 terminal, including failed registry requests when npm provides them. Diagnostic

package/dist/bin.js

@@ -97,7 +97,7 @@ var help = `UserReason installation wizard
 
 userreason-wizard [--directory PATH] [--origin URL]
 
---browser-setup (browser-guided setup; default for development onboarding)
+--browser-setup (browser-guided setup; default for onboarding)
 --terminal-setup (use terminal onboarding instead)
 --resume-setup UUID (resume this project's saved browser setup)
 --browser-origin ORIGIN (trusted dashboard origin for a custom API)
@@ -214,7 +214,7 @@ async function main() {
   if (values["resume-setup"]) uuid(values["resume-setup"], "Setup ID");
   const terminalFlags = ["refresh", "dry-run", "install", "skip-install", "integrate", "skip-integrate", "agent-note", "skip-agent-note", "agent-skill", "skip-agent-skill", "global-cli", "skip-global-cli", "cli-access", "skip-cli-access", "workspace", "workspace-name", "site", "site-name", "origin", "environment", "force", "diff", "session-only", "client-id", "credential-store"];
   const hasTerminalFlags = terminalFlags.some((key) => values[key] !== void 0 && values[key] !== false);
-  const browserMode = explicitBrowserMode || developmentApi && !values["terminal-setup"] && !hasTerminalFlags && !values.yes && !values.json;
+  const browserMode = explicitBrowserMode || !values["terminal-setup"] && !hasTerminalFlags && !values.yes && !values.json;
   if (values["browser-origin"]) {
     if (!browserMode) throw new Error("--browser-origin requires browser setup");
     apiUrl(values["browser-origin"], "Browser origin");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@userreason/wizard",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Authenticated UserReason SDK installation wizard",
   "type": "module",
   "license": "UNLICENSED",