@beryl-so/cli 0.35.0 → 0.36.0

package/README.md

@@ -332,7 +332,7 @@ Durable identities on the site under test: what an authenticated test signs in a
 | --- | --- | --- |
 | `beryl accounts list` | List the test accounts an environment's tests sign in as | `accounts_list` |
 | `beryl accounts create` | Add a test account: the customer's own, or one Beryl signs up | `accounts_create` |
-| `beryl accounts provision <account-id>` | Prove a test account can get in, by replaying a plan that ends logged in | `accounts_provision` |
+| `beryl accounts signup <account-id>` | Store a test account's signup plan and sign it up on its environment | `accounts_signup` |
 | `beryl accounts set-login <account-id>` | Store the sign-in plan a run replays once, plus the probe that proves it | `accounts_set_login` |
 | `beryl accounts get-login <account-id>` | Read the stored sign-in plan, its probe, and the hash a safe write must cite | `accounts_get_login` |
 | `beryl accounts check <account-id>` | Sign in now and prove the session survives into a fresh browser | `accounts_check` |

package/dist/beryl-test-skill.js

@@ -154,13 +154,14 @@ An empty \`accounts list\` means nothing is set up. In order of preference:
    \`beryl accounts create --email <email> --password <password>\`. A DEDICATED test
    account only — never a real user's.
 2. **No credentials, but the app has a signup form** → let Beryl make one.
-   \`beryl accounts create --type beryl\`, then prove it with
-   \`beryl accounts provision <id> --file <plan.json>\`. The plan is any ActionPlan that
-   ends LOGGED IN — a signup filling \`{{mailbox_address}}\` and \`{{login_password}}\`
-   for a new account, or a **sign-in** for one that already exists (hand-made, or the
-   record was lost); both prove the same thing. No password sign-in? Pass
-   \`--login-method otp\` (or \`magic_link\`) and let the plan \`await_email\` through —
-   later sign-ins read the same mailbox.
+   \`beryl accounts create --type beryl\`, then sign it up with
+   \`beryl accounts signup <id> --file <signup-plan.json>\`. The plan is the app's own
+   signup form as an ActionPlan, ending LOGGED IN, filling \`{{mailbox_address}}\` and
+   \`{{login_password}}\`. It stays on the account, so a new environment signs the same
+   identity up again by itself. An account that already exists on the site (hand-made,
+   or the record was lost) skips signup: store its sign-in with \`accounts set-login\`.
+   No password sign-in? Pass \`--login-method otp\` (or \`magic_link\`) and let the plan
+   \`await_email\` through; later sign-ins read the same mailbox.
 3. **Neither** → the flow is not testable authenticated. Say so rather than guessing.
 
 A project with no accounts falls back to the \`LOGIN_EMAIL\` variable +

package/dist/commands/accounts.js

@@ -63,7 +63,7 @@ export const testAccountCommands = [
         description: "Two kinds. `--type user_provided` records a dedicated account you already have on " +
             "the site: pass --email and --password, and it is usable immediately. `--type beryl` " +
             "reserves one Beryl will sign up itself, addressed at the project mailbox. It starts " +
-            "`pending` and becomes usable after `beryl accounts provision`. " +
+            "`pending` and becomes usable after `beryl accounts signup`. " +
             "The first account an environment gets is its default whatever you pass.",
         scope: "project",
         flags: [
@@ -111,8 +111,8 @@ export const testAccountCommands = [
                 is_default: flagBool(input, "default"),
             }));
             const next = account.status === "pending"
-                ? yellow(`\nNot proven yet — run:\n  beryl accounts provision ${account.id} --file <plan.json>\n` +
-                    `with a plan that ends logged in (a signup, or a sign-in if it already exists).`)
+                ? yellow(`\nNot signed up yet. Run:\n  beryl accounts signup ${account.id} --file <signup-plan.json>\n` +
+                    `with the app's signup form as a plan that ends logged in.`)
                 : "";
             return {
                 data: account,
@@ -121,15 +121,15 @@ export const testAccountCommands = [
         },
     },
     {
-        name: "accounts provision",
-        summary: "Prove a test account can get in, by replaying a plan that ends logged in",
-        description: "Runs the plan once in a real browser and, if it passes, marks the account ready. " +
-            "The plan is an ordinary ActionPlan that ends logged in: a SIGNUP when the account " +
-            "does not exist yet, or a SIGN-IN when it already does (you created it by hand, or " +
-            "the site already had it). Either proves the same thing, and a sign-in is what every " +
-            "later test will do anyway. Type {{mailbox_address}} into the email field and " +
-            "{{login_password}} into the password field. Both resolve at replay time, and an " +
-            "`await_email` step reads the project mailbox, so a verification code works.",
+        name: "accounts signup",
+        summary: "Store a test account's signup plan and sign it up on its environment",
+        description: "Runs the app's signup form once in a real browser and, if it ends logged in, marks " +
+            "the account ready. The plan is an ordinary ActionPlan of the SIGNUP flow. Type " +
+            "{{mailbox_address}} into the email field and {{login_password}} into the password " +
+            "field. Both resolve at replay time, and an `await_email` step reads the project " +
+            "mailbox, so a verification code works. The plan is kept on the account, so the " +
+            "same identity can be signed up again on a new environment. For an account that " +
+            "already exists on the site, store its sign-in with `accounts set-login` instead.",
         scope: "project",
         args: [{ name: "account-id", description: "Account id from `beryl accounts list`", required: true }],
         flags: [
@@ -137,20 +137,17 @@ export const testAccountCommands = [
                 name: "file",
                 type: "string",
                 required: true,
-                description: "ActionPlan that ends logged in, as JSON (path, or - for stdin)",
+                description: "The signup ActionPlan, ending logged in, as JSON (path, or - for stdin)",
             },
         ],
-        examples: [
-            "beryl accounts provision acc_123 --file signup-plan.json",
-            "beryl accounts provision acc_123 --file signin-plan.json",
-        ],
+        examples: ["beryl accounts signup acc_123 --file signup-plan.json"],
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
-            const account = (await ctx.client.post(`${accountsPath(workspaceId, projectId)}/${arg(input, "account-id")}/provision`, { plan: readJsonFlag(input, "file") }));
+            const account = (await ctx.client.post(`${accountsPath(workspaceId, projectId)}/${arg(input, "account-id")}/signup`, { plan: readJsonFlag(input, "file") }));
             if (account.status !== "ready")
                 return {
                     data: account,
-                    human: `${yellow("The account could not get in")}: ${account.last_error ?? account.status}`,
+                    human: `${yellow("The signup did not get in")}: ${account.last_error ?? account.status}`,
                     exitCode: 1,
                 };
             return {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@beryl-so/cli",
-  "version": "0.35.0",
+  "version": "0.36.0",
   "description": "Beryl on the command line — projects, runs, the exploring agent, and an MCP server over the same commands.",
   "license": "MIT",
   "type": "module",