@userreason/wizard 0.2.1 → 0.3.1

package/README.md

@@ -36,6 +36,13 @@ 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.
+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
+first-survey offer too. You can create surveys in the dashboard after setup.
+Use `--terminal-setup` to choose terminal onboarding explicitly.
+
 For a different application directory:
 
 ```sh
@@ -137,3 +144,91 @@ locally and is not uploaded to an AI service.
 
 See [troubleshooting](https://docs.userreason.com/get-started/troubleshooting/)
 for help with installation, sign-in, permissions and browser verification.
+
+## Optional installation measurement
+
+The wizard sends bounded step outcomes and durations to the UserReason API to
+help improve setup. It records when initialization, agent guidance, the agent
+skill and CLI access are offered, selected, skipped, already present, applied,
+cancelled or fail. Choosing an option and successfully applying it are separate
+outcomes. The optional choices share one prompt, so its decision time is measured
+once; file and package operations have their own durations. Flow and content
+versions identify the shipped wizard experience. No experiment assignment or
+Statsig integration is included.
+
+These events include framework, package manager, execution mode, rerun status,
+version and known workspace/site scope. Source code, guidance content, file paths,
+project names, email addresses, credentials and raw errors are excluded. Before
+sign-in the wizard uses a random local installation ID. Authenticated events are
+associated with the verified account; queued anonymous events remain anonymous.
+Setup checks do not count as proof that the application has run the SDK.
+
+Disable measurement with `--no-telemetry`, `UR_TELEMETRY_DISABLED=1`,
+`DO_NOT_TRACK=1`, or the shared `userreason telemetry disable` setting. Dry runs
+send and store no analytics. The bounded queue stays outside the project,
+expires after seven days, and retries best-effort uploads with short deadlines.
+Measurement failures never fail an installation.
+
+### Browser-guided setup
+
+Development onboarding uses the browser by default, including local development
+package builds. With a published package, select the development API:
+
+```sh
+npx -y @userreason/wizard@latest --dev
+```
+
+Production still requires `--browser-setup`. Compatible builds also support:
+
+```sh
+npx -y @userreason/wizard@latest --browser-setup
+npx -y @userreason/wizard@latest --resume-setup SETUP_UUID
+```
+
+Run from the same project and use the same `--api-url` or `--api-environment`
+on resume. A custom API also needs its trusted `--browser-origin`.
+Use `--terminal-setup` to choose terminal onboarding explicitly. Scripted runs
+with `--yes` or `--json`, package refresh, dry runs, and explicit terminal
+installation/resource flags retain their existing behavior; an explicit
+`--browser-setup` still rejects incompatible terminal options.
+If a server has not enabled browser setup, a new connection falls back before
+creating a session or local effects.
+Malformed protocol data and already-started setups never fall back silently.
+Server rollout flags remain off by default; publication is a separate release.
+
+The browser owns workspace/site selection, optional choices, local-plan approval,
+finish and cancellation. Source analysis, suggested drafts and the Agent test
+remain implemented but are hidden and skipped while their rollout flags are off. The local runner executes only approved typed effects
+using the separate owner-only setup capability. It does not read or replace
+normal CLI credentials. Stopping the local process leaves the setup resumable;
+cancelling in the browser does not undo completed edits or delete created drafts.
+Terminal results list verified, failed and manual outcomes separately.
+
+Source analysis starts only when the server advertises availability. It is
+currently disabled for production and development onboarding, including resumed
+setups. No onboarding recommendation providers are called.
+
+The optional footer choice defaults to No. `planFooter` preserves the reachable
+host footer and adds a plain `Powered by UserReason` link when placement is
+unambiguous. Missing/ambiguous placement and customized skills are manual outcomes.
+Package managers use fixed allowlisted arguments, disabled scripts and exact
+versions. Lockfiles are declared generated outputs and verified by recorded hashes.
+Interrupted commands reconcile local receipts instead of blindly reinstalling.
+
+The Agent test and terminal first-survey offer are paused. Installing the agent
+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
+`@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.
+
+Browser-guided installation prints package-manager failures in the connected
+terminal, including failed registry requests when npm provides them. Diagnostic
+text is redacted and retained in the private local setup receipt for resume.
+A finished browser session with failed local steps is reported as incomplete and
+the wizard exits unsuccessfully. Project `.npmrc` comments and authentication
+references are preserved; registry configuration only adds the UserReason scope.

package/dist/agent-note.js

@@ -3,12 +3,13 @@ import {
   applyAgentNote,
   offerAgentNote,
   planAgentNote
-} from "./chunk-ULHKVBPD.js";
-import "./chunk-SJVLAYGG.js";
-import "./chunk-5SC2K42Q.js";
-import "./chunk-YMSGDC4B.js";
-import "./chunk-OEGNGGZ2.js";
-import "./chunk-GGARVSPT.js";
+} from "./chunk-7O7H3PIM.js";
+import "./chunk-LEJFE4U5.js";
+import "./chunk-TOID3NYP.js";
+import "./chunk-PJQOSDYS.js";
+import "./chunk-NMHTFC5Q.js";
+import "./chunk-EVNEX5N5.js";
+import "./chunk-7AAH6C4L.js";
 import "./chunk-WL3NOIM6.js";
 export {
   applyAgentNote,

package/dist/agent-skill.js

@@ -3,11 +3,12 @@ import {
   applyAgentSkill,
   offerAgentSkill,
   planAgentSkill
-} from "./chunk-5Z5J6PY5.js";
-import "./chunk-SJVLAYGG.js";
-import "./chunk-YMSGDC4B.js";
-import "./chunk-OEGNGGZ2.js";
-import "./chunk-GGARVSPT.js";
+} from "./chunk-SB3AYQWG.js";
+import "./chunk-TOID3NYP.js";
+import "./chunk-PJQOSDYS.js";
+import "./chunk-NMHTFC5Q.js";
+import "./chunk-EVNEX5N5.js";
+import "./chunk-7AAH6C4L.js";
 import "./chunk-WL3NOIM6.js";
 export {
   applyAgentSkill,

package/dist/analytics.js

@@ -0,0 +1,9 @@
+import { createRequire as createWizardRequire } from 'node:module'; import { fileURLToPath as wizardFileURLToPath } from 'node:url'; import { dirname as wizardDirname } from 'node:path'; const require = createWizardRequire(import.meta.url); const __filename = wizardFileURLToPath(import.meta.url); const __dirname = wizardDirname(__filename);
+import {
+  WizardAnalytics
+} from "./chunk-KF37D5WL.js";
+import "./chunk-7AAH6C4L.js";
+import "./chunk-WL3NOIM6.js";
+export {
+  WizardAnalytics
+};