npm - @beryl-so/cli - Versions diffs - 0.32.0 → 0.33.0 - Mend

@beryl-so/cli 0.32.0 → 0.33.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (15) hide show

package/README.md +58 -58
package/dist/commands/accounts.js +6 -6
package/dist/commands/auth.js +5 -5
package/dist/commands/config-vars.js +5 -5
package/dist/commands/environments.js +78 -44
package/dist/commands/explorations.js +3 -3
package/dist/commands/groups.js +2 -2
package/dist/commands/health.js +1 -1
package/dist/commands/init.js +8 -8
package/dist/commands/mailboxes.js +6 -6
package/dist/commands/mcp.js +3 -3
package/dist/commands/projects.js +5 -5
package/dist/commands/runs.js +12 -12
package/dist/commands/tests.js +29 -29
package/package.json +2 -2

package/README.md CHANGED Viewed

@@ -1,18 +1,18 @@
-<!-- GENERATED by `npm run docs` — edit the command registry (src/commands/), not this file. -->
+<!-- GENERATED by `npm run docs`. Edit the command registry (src/commands/), not this file. -->
 # beryl CLI
 Beryl on the command line: create projects, watch the agent explore and author tests,
-trigger runs in CI, manage everything the web app can — plus an MCP server (`beryl mcp`)
+trigger runs in CI, manage everything the web app can, plus an MCP server (`beryl mcp`)
 that exposes every command to coding agents.
-## Quickstart — one command
+## Quickstart: one command
 ```bash
 npx @beryl-so/cli@latest init
 ```
-Signs you in (browser approval by default, emailed one-time code as fallback — new
+Signs you in (browser approval by default, emailed one-time code as fallback; new
 emails are signed up on the spot), wires the beryl + playwright MCP servers into Claude
 Code or Cursor, installs the beryl-test authoring skill, and installs Playwright for
 local runs. Safe to re-run.
@@ -27,18 +27,18 @@ npx @beryl-so/cli@latest …    # or run one-off without installing
 From the monorepo (development): `cd cli && npm install && npm run build && npm link`.
 `beryl init` and `beryl mcp` warn (stderr, best-effort) when the running CLI is behind the
-latest npm release — a stale MCP server silently exposes fewer tools. Set
+latest npm release; a stale MCP server silently exposes fewer tools. Set
 `BERYL_NO_UPDATE_CHECK=1` to opt out.
 ## Authenticate
 ```bash
-beryl login                  # opens the browser to approve — press Enter for an emailed code instead
+beryl login                  # opens the browser to approve; press Enter for an emailed code instead
 beryl login --otp            # skip the browser; emailed one-time code (signs up new emails too)
 export BERYL_API_KEY=beryl_pat_…   # CI: use a token from Account → API tokens
 ```
-Config stores your token + API URL only — nothing else persists. Point a command at a
+Config stores your token + API URL only; nothing else persists. Point a command at a
 workspace/project with the `--workspace` / `--project` flags or the `BERYL_WORKSPACE` /
 `BERYL_PROJECT` env vars; with exactly one, the CLI auto-picks it.
 Precedence: flags > `BERYL_*` env > auto-pick-if-one.
@@ -59,18 +59,18 @@ claude mcp add beryl -- beryl mcp                    # or, with the CLI installe
 ```
 Most non-interactive commands below are exposed as an MCP tool with the same name
-(spaces and dashes become underscores) — see the MCP tool column. `—` marks commands
+(spaces and dashes become underscores); see the MCP tool column. `none` marks commands
 kept CLI-only: account/billing/team admin, feedback, and cloud exploration.
 ## Commands
 ### init
-Set up Beryl in this repo — sign in and wire up your coding agent
+Set up Beryl in this repo: sign in and wire up your coding agent
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl init` | Set up Beryl in this repo — sign in and wire up your coding agent | — |
+| `beryl init` | Set up Beryl in this repo: sign in and wire up your coding agent | none |
 ### guide
@@ -86,7 +86,7 @@ Authenticate the CLI with your Beryl account
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl login` | Authenticate the CLI with your Beryl account | — |
+| `beryl login` | Authenticate the CLI with your Beryl account | none |
 ### signup
@@ -143,9 +143,9 @@ Manage who belongs to a workspace and their roles.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl members list` | List workspace members | — |
-| `beryl members set-role <user-id> <role>` | Change a member's role | — |
-| `beryl members remove <user-id>` | Remove a member from the workspace | — |
+| `beryl members list` | List workspace members | none |
+| `beryl members set-role <user-id> <role>` | Change a member's role | none |
+| `beryl members remove <user-id>` | Remove a member from the workspace | none |
 ### invites
@@ -153,16 +153,16 @@ Send, list, and revoke workspace invitations, and accept ones sent to you.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl invites send <email>` | Invite someone to the workspace by email | — |
-| `beryl invites list` | List the workspace's outstanding invitations | — |
-| `beryl invites revoke <invitation-id>` | Revoke a pending invitation | — |
-| `beryl invites mine` | List invitations sent to you | — |
-| `beryl invites accept <invitation>` | Accept an invitation (by id, or by the token from the invite email) | — |
-| `beryl invites decline <invitation-id>` | Decline an invitation | — |
+| `beryl invites send <email>` | Invite someone to the workspace by email | none |
+| `beryl invites list` | List the workspace's outstanding invitations | none |
+| `beryl invites revoke <invitation-id>` | Revoke a pending invitation | none |
+| `beryl invites mine` | List invitations sent to you | none |
+| `beryl invites accept <invitation>` | Accept an invitation (by id, or by the token from the invite email) | none |
+| `beryl invites decline <invitation-id>` | Decline an invitation | none |
 ### projects
-Create and manage projects — a site Beryl explores, authors tests for, and runs.
+Create and manage projects: a site Beryl explores, authors tests for, and runs.
 `beryl projects` with no subcommand runs `projects list`.
@@ -170,16 +170,16 @@ Create and manage projects — a site Beryl explores, authors tests for, and run
 | --- | --- | --- |
 | `beryl projects list` | List projects in the workspace | `projects_list` |
 | `beryl projects get` | Show one project, including its current exploration state | `projects_get` |
-| `beryl projects create [url]` | Create a project — with a URL the agent starts exploring; with just --name an empty one | `projects_create` |
+| `beryl projects create [url]` | Create a project. With a URL the agent starts exploring; with just --name an empty one | `projects_create` |
 | `beryl projects rename <name>` | Rename a project | `projects_rename` |
 | `beryl projects delete` | Delete a project and all its tests and runs | `projects_delete` |
-| `beryl projects re-explore` | Send the agent back in — run/heal existing tests and discover new flows | — |
+| `beryl projects re-explore` | Send the agent back in to run/heal existing tests and discover new flows | none |
 | `beryl projects report` | Aggregate quality report across recent runs (pass rates, flaky tests, trend) | `projects_report` |
 | `beryl projects reusable-auth <url>` | Check whether a saved login can be reused for a URL before creating a project | `projects_reusable_auth` |
 ### envs
-Manage a project's environments — the URLs and auth Beryl runs tests against.
+Manage a project's environments: the URLs and auth Beryl runs tests against.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
@@ -191,18 +191,18 @@ Manage a project's environments — the URLs and auth Beryl runs tests against.
 ### schedule
-View and set the schedule on which Beryl runs a project's tests automatically — the whole project, or one group with --group.
+Manage the schedules on which Beryl runs a project's tests automatically. A project can hold many independent schedules; each has its own cadence (daily or weekly), local run time, timezone, and target groups (none = every active test).
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl schedule get` | Show the project's run schedule and any per-group schedules | `schedule_get` |
-| `beryl schedule set` | Enable scheduled runs (daily, or weekly on a given day) | `schedule_set` |
-| `beryl schedule disable` | Turn scheduled runs off | `schedule_disable` |
-| `beryl schedule remove` | Remove a group's schedule entirely (the group itself stays) | `schedule_remove` |
+| `beryl schedule list` | List the project's schedules | `schedule_list` |
+| `beryl schedule add` | Add a schedule (daily, or weekly on a given day) | `schedule_add` |
+| `beryl schedule update <schedule-id>` | Change a schedule's cadence, time, timezone, or groups | `schedule_update` |
+| `beryl schedule remove <schedule-id>` | Remove a schedule (its tests and groups stay) | `schedule_remove` |
 ### tests
-Author, inspect, version, and heal a project's tests — the checks Beryl runs on each run.
+Author, inspect, version, and heal a project's tests: the checks Beryl runs on each run.
 `beryl tests` with no subcommand runs `tests list`.
@@ -212,7 +212,7 @@ Author, inspect, version, and heal a project's tests — the checks Beryl runs o
 | `beryl tests list` | List the project's tests with their latest result | `tests_list` |
 | `beryl tests get <test-id>` | Show one test | `tests_get` |
 | `beryl tests plan <test-id>` | Print a test's current step plan (JSON) | `tests_plan` |
-| `beryl tests create` | Create a test case from a JSON action plan — for tests authored locally, e.g. by your coding agent | `tests_create` |
+| `beryl tests create` | Create a test case from a JSON action plan (for tests authored locally, e.g. by your coding agent) | `tests_create` |
 | `beryl tests set-plan <test-id>` | Replace a test's step plan from a JSON file (creates a new version) | `tests_set_plan` |
 | `beryl tests rename <test-id> <title>` | Rename a test | `tests_rename` |
 | `beryl tests set-groups <test-id>` | Replace the groups a test belongs to | `tests_set_groups` |
@@ -231,7 +231,7 @@ Author, inspect, version, and heal a project's tests — the checks Beryl runs o
 ### groups
-Manage a project's test groups — labels a test can carry any number of, used to filter, run, or schedule a slice of the suite. Groups are created only here (or in Settings → Groups); assigning a test to an unknown name is an error.
+Manage a project's test groups: labels a test can carry any number of, used to filter, run, or schedule a slice of the suite. Groups are created only here (or in Settings → Groups); assigning a test to an unknown name is an error.
 `beryl groups` with no subcommand runs `groups list`.
@@ -240,7 +240,7 @@ Manage a project's test groups — labels a test can carry any number of, used t
 | `beryl groups list` | List the project's test groups and how many tests each holds | `groups_list` |
 | `beryl groups create <name>` | Create a group | `groups_create` |
 | `beryl groups rename <group> <name>` | Rename a group (tests keep their membership) | `groups_rename` |
-| `beryl groups delete <group>` | Delete a group — its tests stay, its schedule (if any) goes with it | `groups_delete` |
+| `beryl groups delete <group>` | Delete a group: its tests stay; a schedule targeting only this group goes with it | `groups_delete` |
 ### runs
@@ -262,7 +262,7 @@ Trigger a run of a project's tests (e.g. in CI), then watch, inspect, and downlo
 ### health
-Site Health — how your site reads to search engines and visitors: content, speed, mobile, links and security, graded from a real check of your live pages.
+Site Health, or how your site reads to search engines and visitors: content, speed, mobile, links and security, graded from a real check of your live pages.
 `beryl health` with no subcommand runs `health get`.
@@ -273,15 +273,15 @@ Site Health — how your site reads to search engines and visitors: content, spe
 ### explorations
-Inspect the agent's exploration runs — how it crawled a site and authored its tests.
+Inspect the agent's exploration runs: how it crawled a site and authored its tests.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl explorations list` | List the agent's exploration passes for a project | — |
-| `beryl explorations get <exploration-id>` | Show one exploration: authored tests, abandoned flows, coverage, frontier | — |
-| `beryl explorations steps <exploration-id>` | List every step the agent took in an exploration | — |
-| `beryl explorations cancel <exploration-id>` | Cancel an in-flight exploration | — |
-| `beryl explorations watch <exploration-id>` | Stream an exploration live — watch the agent explore and author tests | — |
+| `beryl explorations list` | List the agent's exploration passes for a project | none |
+| `beryl explorations get <exploration-id>` | Show one exploration: authored tests, abandoned flows, coverage, frontier | none |
+| `beryl explorations steps <exploration-id>` | List every step the agent took in an exploration | none |
+| `beryl explorations cancel <exploration-id>` | Cancel an in-flight exploration | none |
+| `beryl explorations watch <exploration-id>` | Stream an exploration live: watch the agent explore and author tests | none |
 ### config
@@ -305,7 +305,7 @@ Manage the variables, secrets, and files the agent can use while exploring and r
 ### mailbox
-The project's standing email addresses — where its tests receive sign-in mail.
+The project's standing email addresses, where its tests receive sign-in mail.
 `beryl mailbox` with no subcommand runs `mailbox get`.
@@ -320,14 +320,14 @@ The project's standing email addresses — where its tests receive sign-in mail.
 ### accounts
-Durable identities on the site under test — what an authenticated test signs in as.
+Durable identities on the site under test: what an authenticated test signs in as.
 `beryl accounts` with no subcommand runs `accounts list`.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
 | `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 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 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` |
@@ -341,9 +341,9 @@ View and update your personal account profile.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl account get` | Show your account profile | — |
-| `beryl account update` | Update your profile | — |
-| `beryl account deletion-preview` | Preview what deleting your account would remove or leave | — |
+| `beryl account get` | Show your account profile | none |
+| `beryl account update` | Update your profile | none |
+| `beryl account deletion-preview` | Preview what deleting your account would remove or leave | none |
 ### feedback
@@ -351,7 +351,7 @@ Send product feedback to the Beryl team.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl feedback send <message>` | Send product feedback to the Beryl team | — |
+| `beryl feedback send <message>` | Send product feedback to the Beryl team | none |
 ### billing
@@ -359,10 +359,10 @@ Review a workspace's plan usage, subscription, and invoices.
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl billing usage` | Show plan usage: monthly cloud run minutes | — |
-| `beryl billing subscription` | Show the workspace's subscription | — |
-| `beryl billing invoices` | List recent invoices | — |
-| `beryl billing portal` | Get a Stripe billing-portal link for the workspace | — |
+| `beryl billing usage` | Show plan usage: monthly cloud run minutes | none |
+| `beryl billing subscription` | Show the workspace's subscription | none |
+| `beryl billing invoices` | List recent invoices | none |
+| `beryl billing portal` | Get a Stripe billing-portal link for the workspace | none |
 ### version
@@ -374,18 +374,18 @@ Show the running CLI version, API URL, and Node version
 ### mcp
-Run the Beryl MCP server (stdio) — every CLI command as an agent tool
+Run the Beryl MCP server (stdio): every CLI command as an agent tool
 | Command | Summary | MCP tool |
 | --- | --- | --- |
-| `beryl mcp` | Run the Beryl MCP server (stdio) — every CLI command as an agent tool | — |
+| `beryl mcp` | Run the Beryl MCP server (stdio): every CLI command as an agent tool | none |
 Run `beryl <command> --help` for flags and examples.
 ## Global flags
-- `-V, --version` — Print the CLI version and exit
-- `--json` — Print machine-readable JSON (NDJSON for streams)
-- `--api-url` — API base URL (default https://api.beryl.so)
-- `--token` — Personal access token (overrides config/BERYL_API_KEY)
-- `-h, --help` — Show help
+- `-V, --version`: Print the CLI version and exit
+- `--json`: Print machine-readable JSON (NDJSON for streams)
+- `--api-url`: API base URL (default https://api.beryl.so)
+- `--token`: Personal access token (overrides config/BERYL_API_KEY)
+- `-h, --help`: Show help

package/dist/commands/accounts.js CHANGED Viewed

@@ -37,7 +37,7 @@ export const testAccountCommands = [
         name: "accounts list",
         summary: "List the test accounts an environment's tests sign in as",
         groupDefault: true,
-        groupSummary: "Durable identities on the site under test — what an authenticated test signs in as.",
+        groupSummary: "Durable identities on the site under test: what an authenticated test signs in as.",
         description: "Every test account on the project, with the identity label a plan's `auth_label` " +
             "names. The row marked * is the default: what a plan gets when it sets " +
             "requires_auth without an auth_label.",
@@ -59,10 +59,10 @@ export const testAccountCommands = [
     },
     {
         name: "accounts create",
-        summary: "Add a test account — the customer's own, or one Beryl signs up",
+        summary: "Add a test account: the customer's own, or one Beryl signs up",
         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 " +
+            "reserves one Beryl will sign up itself, addressed at the project mailbox. It starts " +
             "`pending` and becomes usable after `beryl accounts provision`. " +
             "The first account an environment gets is its default whatever you pass.",
         scope: "project",
@@ -124,11 +124,11 @@ 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 " +
+            "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 " +
+            "{{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.",
         scope: "project",
         args: [{ name: "account-id", description: "Account id from `beryl accounts list`", required: true }],
@@ -170,7 +170,7 @@ export const testAccountCommands = [
             "field; an emailed code or magic link arrives at the account's own address, so an " +
             "`await_email` step reads it with no human involved.\n\n" +
             "--probe is the liveness check: a two-step plan (goto a gated page, then a POSITIVE " +
-            "assertion that only holds when signed in — the account menu, a 'Sign out' control). " +
+            "assertion that only holds when signed in: the account menu, a 'Sign out' control). " +
             "It is replayed in a fresh browser carrying only the captured session. It is " +
             "REQUIRED, and not a formality: assertions like `hidden`, `count 0`, and a URL " +
             "match on a redirect all pass against a logged-out page, so without a positive " +

package/dist/commands/auth.js CHANGED Viewed

@@ -97,7 +97,7 @@ export const authCommands = [
         summary: "Authenticate the CLI with your Beryl account",
         description: "Signs in via your browser (a code you confirm at beryl.so) and stores a personal " +
             "access token in the CLI config. Pass --otp (or --email) to skip the browser and " +
-            "sign in with an emailed one-time code instead — a new email gets an account " +
+            "sign in with an emailed one-time code instead. A new email gets an account " +
             "created automatically. Pass --token to use an existing token from Account → API " +
             "tokens. Pass --email plus --code (the 6 digits from the email, e.g. read from a " +
             "`beryl inbox`) to complete the OTP flow without a prompt. In CI, prefer the " +
@@ -108,18 +108,18 @@ export const authCommands = [
             {
                 name: "otp",
                 type: "boolean",
-                description: "Skip the browser — sign in with an emailed code",
+                description: "Skip the browser and sign in with an emailed code",
             },
             {
                 name: "email",
                 type: "string",
                 description: "Email for the one-time code sign-in (default: your last sign-in, or your git " +
-                    "user.email — offered as the prompt default)",
+                    "user.email, offered as the prompt default)",
             },
             {
                 name: "code",
                 type: "string",
-                description: "The emailed 6-digit code — skips the prompt for non-interactive use " +
+                description: "The emailed 6-digit code. Skips the prompt for non-interactive use " +
                     "(requires --email; also skips sending a fresh code, so pair it with a " +
                     "code already requested via `beryl login`, `beryl signup`, or the API)",
             },
@@ -184,7 +184,7 @@ export const authCommands = [
         name: "signup",
         summary: "Register a new Beryl account (emails a 6-digit verification code)",
         description: "Creates a passwordless account for the email and sends it a 6-digit code. " +
-            "Finish with `beryl login --email <addr> --code <the 6 digits>` — that verifies " +
+            "Finish with `beryl login --email <addr> --code <the 6 digits>`, which verifies " +
             "the account, creates its workspace, and signs the CLI in. With an inbox from " +
             "`beryl inbox create` as the address, an agent can provision a fresh account " +
             "end-to-end with no human at a prompt.",

package/dist/commands/config-vars.js CHANGED Viewed

@@ -57,8 +57,8 @@ export const configCommands = [
     {
         name: "config vars get",
         summary: "Show one config variable",
-        description: "Returns the variable row with its value in plaintext (variables are not secret) — " +
-            "a sensitive value lives in `config secrets`, readable only via `config secrets " +
+        description: "Returns the variable row with its value in plaintext (variables are not secret). " +
+            "A sensitive value lives in `config secrets`, readable only via `config secrets " +
             "get --reveal`.",
         scope: "project",
         args: [{ name: "key", description: "Variable key or id", required: true }],
@@ -116,15 +116,15 @@ export const configCommands = [
     {
         name: "config secrets get",
         summary: "Show one secret's metadata, or reveal its value with --reveal",
-        description: "Returns metadata only by default; --reveal is a logged, member-gated decrypt — " +
-            "unlike `config vars get`, which returns its value in plaintext.",
+        description: "Returns metadata only by default; --reveal is a logged, member-gated decrypt " +
+            "(unlike `config vars get`, which returns its value in plaintext).",
         scope: "project",
         args: [{ name: "key", description: "Secret key or id", required: true }],
         flags: [
             {
                 name: "reveal",
                 type: "boolean",
-                description: "Return the decrypted value — the explicit read that lets the agent drive a " +
+                description: "Return the decrypted value: the explicit read that lets the agent drive a " +
                     "real login while authoring. Member-gated; every reveal is logged",
             },
             {

package/dist/commands/environments.js CHANGED Viewed

@@ -1,12 +1,24 @@
 import { UsageError } from "../errors.js";
 import { arg, findGroup, flagBool, flagNum, flagStr, projectPath } from "./util.js";
-const SCHEDULE_GROUP_FLAG = "Schedule one group (by name or id) instead of the whole project; the run covers the group's active tests at fire time";
+const SCHEDULE_GROUPS_FLAG = "Comma-separated group names or ids the schedule targets (the run covers the union of their active tests at fire time); omit to run every active test";
+const SCHEDULE_CADENCE_FLAGS = [
+    {
+        name: "frequency",
+        type: "string",
+        enum: ["daily", "weekly"],
+        description: "How often (default daily)",
+    },
+    { name: "day", type: "number", description: "Weekly only: day of week, 0=Monday … 6=Sunday" },
+    { name: "hour", type: "number", description: "Hour of day 0-23" },
+    { name: "minute", type: "number", description: "Minute 0-59" },
+    { name: "tz", type: "string", description: "IANA timezone (e.g. America/Los_Angeles)" },
+];
 export const environmentCommands = [
     {
         name: "envs list",
         summary: "List a project's environments",
         scope: "project",
-        groupSummary: "Manage a project's environments — the URLs and auth Beryl runs tests against.",
+        groupSummary: "Manage a project's environments: the URLs and auth Beryl runs tests against.",
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
             return { data: await ctx.client.get(`${projectPath(workspaceId, projectId)}/environments`) };
@@ -92,88 +104,110 @@ export const environmentCommands = [
         },
     },
     {
-        name: "schedule get",
-        summary: "Show the project's run schedule and any per-group schedules",
+        name: "schedule list",
+        summary: "List the project's schedules",
         scope: "project",
-        groupSummary: "View and set the schedule on which Beryl runs a project's tests automatically — the whole project, or one group with --group.",
+        groupSummary: "Manage the schedules on which Beryl runs a project's tests automatically. A project can hold many independent schedules; each has its own cadence (daily or weekly), local run time, timezone, and target groups (none = every active test).",
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
-            return { data: await ctx.client.get(`${projectPath(workspaceId, projectId)}/schedule`) };
+            return { data: await ctx.client.get(`${projectPath(workspaceId, projectId)}/schedules`) };
         },
     },
     {
-        name: "schedule set",
-        summary: "Enable scheduled runs (daily, or weekly on a given day)",
+        name: "schedule add",
+        summary: "Add a schedule (daily, or weekly on a given day)",
         scope: "project",
         flags: [
-            {
-                name: "frequency",
-                type: "string",
-                enum: ["daily", "weekly"],
-                description: "How often (default daily)",
-            },
-            { name: "day", type: "number", description: "Weekly only: day of week, 0=Monday … 6=Sunday" },
-            { name: "hour", type: "number", description: "Hour of day 0-23" },
-            { name: "minute", type: "number", description: "Minute 0-59" },
-            { name: "tz", type: "string", description: "IANA timezone (e.g. America/Los_Angeles)" },
-            { name: "group", type: "string", description: SCHEDULE_GROUP_FLAG },
+            ...SCHEDULE_CADENCE_FLAGS,
+            { name: "groups", type: "string", description: SCHEDULE_GROUPS_FLAG },
         ],
         examples: [
-            "beryl schedule set --frequency daily --hour 6 --tz UTC",
-            "beryl schedule set --group Smoke --frequency weekly --day 0 --hour 9 --tz UTC",
+            "beryl schedule add --frequency daily --hour 6 --tz UTC",
+            'beryl schedule add --groups "Smoke,Checkout" --frequency weekly --day 0 --hour 9 --minute 15 --tz UTC',
         ],
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
             return {
-                data: await ctx.client.put(await schedulePath(ctx, input, workspaceId, projectId), {
-                    enabled: true,
+                data: await ctx.client.post(`${projectPath(workspaceId, projectId)}/schedules`, {
                     frequency: flagStr(input, "frequency") ?? "daily",
                     day_of_week: flagNum(input, "day") ?? null,
                     run_hour: flagNum(input, "hour"),
                     run_minute: flagNum(input, "minute"),
                     timezone: flagStr(input, "tz"),
+                    group_ids: await resolveGroupIds(ctx, input, workspaceId, projectId),
                 }),
             };
         },
     },
     {
-        name: "schedule disable",
-        summary: "Turn scheduled runs off",
+        name: "schedule update",
+        summary: "Change a schedule's cadence, time, timezone, or groups",
         scope: "project",
-        flags: [{ name: "group", type: "string", description: SCHEDULE_GROUP_FLAG }],
+        args: [{ name: "schedule-id", description: "Schedule id (see schedule list)", required: true }],
+        flags: [
+            ...SCHEDULE_CADENCE_FLAGS,
+            { name: "groups", type: "string", description: SCHEDULE_GROUPS_FLAG },
+            {
+                name: "all-tests",
+                type: "boolean",
+                description: "Target every active test (clears the schedule's groups)",
+            },
+        ],
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
+            const scheduleId = arg(input, "schedule-id");
+            const schedules = (await ctx.client.get(`${projectPath(workspaceId, projectId)}/schedules`));
+            const existing = schedules.find((sch) => sch.id === scheduleId);
+            if (!existing)
+                throw new UsageError(`No schedule '${scheduleId}' in this project.`);
+            if (flagBool(input, "all-tests") && flagStr(input, "groups"))
+                throw new UsageError("--all-tests and --groups are mutually exclusive");
+            const groupIds = flagBool(input, "all-tests")
+                ? []
+                : flagStr(input, "groups")
+                    ? await resolveGroupIds(ctx, input, workspaceId, projectId)
+                    : existing.group_ids;
             return {
-                data: await ctx.client.put(await schedulePath(ctx, input, workspaceId, projectId), {
-                    enabled: false,
+                data: await ctx.client.put(`${projectPath(workspaceId, projectId)}/schedules/${scheduleId}`, {
+                    frequency: flagStr(input, "frequency") ?? existing.frequency,
+                    day_of_week: flagNum(input, "day") ?? existing.day_of_week,
+                    run_hour: flagNum(input, "hour") ?? existing.run_hour,
+                    run_minute: flagNum(input, "minute") ?? existing.run_minute,
+                    timezone: flagStr(input, "tz") ?? existing.timezone,
+                    group_ids: groupIds,
                 }),
             };
         },
     },
     {
         name: "schedule remove",
-        summary: "Remove a group's schedule entirely (the group itself stays)",
+        summary: "Remove a schedule (its tests and groups stay)",
         scope: "project",
-        flags: [{ name: "group", type: "string", description: "Group name or id", required: true }],
+        args: [{ name: "schedule-id", description: "Schedule id (see schedule list)", required: true }],
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
-            if (!flagStr(input, "group"))
-                throw new UsageError("--group is required");
-            await ctx.client.del(await schedulePath(ctx, input, workspaceId, projectId));
+            await ctx.client.del(`${projectPath(workspaceId, projectId)}/schedules/${arg(input, "schedule-id")}`);
             return { human: "Removed." };
         },
     },
 ];
-async function schedulePath(ctx, input, workspaceId, projectId) {
-    const base = `${projectPath(workspaceId, projectId)}/schedule`;
-    const ref = flagStr(input, "group");
-    if (!ref)
-        return base;
+async function resolveGroupIds(ctx, input, workspaceId, projectId) {
+    const raw = flagStr(input, "groups");
+    if (!raw)
+        return [];
+    const refs = raw
+        .split(",")
+        .map((r) => r.trim())
+        .filter(Boolean);
+    if (refs.length === 0)
+        return [];
     const groups = (await ctx.client.get(`${projectPath(workspaceId, projectId)}/groups`));
-    const group = findGroup(groups, ref);
-    if (!group) {
-        const names = groups.map((g) => g.name).join(", ") || "none yet";
-        throw new UsageError(`No group '${ref}' in this project (existing: ${names}).`);
-    }
-    return `${projectPath(workspaceId, projectId)}/groups/${group.id}/schedule`;
+    return refs.map((ref) => {
+        const group = findGroup(groups, ref);
+        if (!group) {
+            const names = groups.map((g) => g.name).join(", ") || "none yet";
+            throw new UsageError(`No group '${ref}' in this project (existing: ${names}).`);
+        }
+        return group.id;
+    });
 }

package/dist/commands/explorations.js CHANGED Viewed

@@ -3,7 +3,7 @@ import { watchExploration } from "./watch.js";
 export const explorationCommands = [
     {
         name: "explorations list",
-        groupSummary: "Inspect the agent's exploration runs — how it crawled a site and authored its tests.",
+        groupSummary: "Inspect the agent's exploration runs: how it crawled a site and authored its tests.",
         summary: "List the agent's exploration passes for a project",
         scope: "project",
         async run(ctx, input) {
@@ -38,7 +38,7 @@ export const explorationCommands = [
     {
         name: "explorations cancel",
         summary: "Cancel an in-flight exploration",
-        description: "Stops a running exploration without touching the project or its tests — the " +
+        description: "Stops a running exploration without touching the project or its tests: the " +
             "lever for a runaway/non-convergent pass burning agent budget.",
         scope: "project",
         args: [{ name: "exploration-id", description: "Exploration id", required: true }],
@@ -51,7 +51,7 @@ export const explorationCommands = [
     },
     {
         name: "explorations watch",
-        summary: "Stream an exploration live — watch the agent explore and author tests",
+        summary: "Stream an exploration live: watch the agent explore and author tests",
         description: "Replays every recorded step on connect, then follows live until the exploration " +
             "completes or fails.",
         scope: "project",

package/dist/commands/groups.js CHANGED Viewed

@@ -15,7 +15,7 @@ export const groupCommands = [
         summary: "List the project's test groups and how many tests each holds",
         scope: "project",
         groupDefault: true,
-        groupSummary: "Manage a project's test groups — labels a test can carry any number of, used to filter, run, or schedule a slice of the suite. Groups are created only here (or in Settings → Groups); assigning a test to an unknown name is an error.",
+        groupSummary: "Manage a project's test groups: labels a test can carry any number of, used to filter, run, or schedule a slice of the suite. Groups are created only here (or in Settings → Groups); assigning a test to an unknown name is an error.",
         async run(ctx, input) {
             const { workspaceId, projectId } = await ctx.requireProject(input);
             return { data: await ctx.client.get(`${projectPath(workspaceId, projectId)}/groups`) };
@@ -54,7 +54,7 @@ export const groupCommands = [
     },
     {
         name: "groups delete",
-        summary: "Delete a group — its tests stay, its schedule (if any) goes with it",
+        summary: "Delete a group: its tests stay; a schedule targeting only this group goes with it",
         scope: "project",
         args: [{ name: "group", description: "Group name or id", required: true }],
         flags: [{ name: "force", type: "boolean", description: "Skip the confirmation prompt" }],

package/dist/commands/health.js CHANGED Viewed

@@ -8,7 +8,7 @@ export const healthCommands = [
     {
         name: "health get",
         groupDefault: true,
-        groupSummary: "Site Health — how your site reads to search engines and visitors: content, " +
+        groupSummary: "Site Health, or how your site reads to search engines and visitors: content, " +
             "speed, mobile, links and security, graded from a real check of your live pages.",
         summary: "Show the latest Site Health report for a project environment",
         description: "A check runs automatically when a project or environment gets its URL. While one " +

package/dist/commands/init.js CHANGED Viewed

@@ -147,20 +147,20 @@ async function ensureLocalPlaywright(ctx, cwd) {
 export const initCommands = [
     {
         name: "init",
-        summary: "Set up Beryl in this repo — sign in and wire up your coding agent",
+        summary: "Set up Beryl in this repo: sign in and wire up your coding agent",
         description: "One-command onboarding: signs you in (browser confirm, or an emailed one-time code) " +
             "and wires up your coding " +
-            "agent. Nothing is detected and nothing is conditional — every run wires the beryl AND " +
+            "agent. Nothing is detected and nothing is conditional: every run wires the beryl AND " +
             "playwright MCP servers, writes the authoring skill (user scope: your home " +
             ".agents/skills/ + .claude/skills/, so it follows you into every session; --scope " +
             "project: the repo's own dirs, committed for teammates), and installs @playwright/test " +
-            "+ chromium if missing — browser authoring and local runs depend on it. By default the " +
+            "+ chromium if missing, since browser authoring and local runs depend on it. By default the " +
             "servers are wired per-user (matching where your login token lives) via `claude mcp add " +
             "-s user`; pass --scope project to write a committed .mcp.json for a shared repo " +
-            "instead. No workspace/project pin and no URL prompt — ask Claude to write tests for " +
+            "instead. No workspace/project pin and no URL prompt: ask Claude to write tests for " +
             "your site and it resolves the workspace, project, and URL. Safe to re-run: every run " +
             "refreshes the authoring skill to this CLI's version (overwriting an older or edited " +
-            "copy — `beryl guide` prints the same content), and skips whatever else is already set " +
+            "copy; `beryl guide` prints the same content), and skips whatever else is already set " +
             "up.",
         interactive: true,
         flags: [
@@ -170,7 +170,7 @@ export const initCommands = [
                 enum: ["user", "project"],
                 description: "Where to wire the MCP servers. `user` (default) configures them per-user (matching " +
                     "where your Beryl login token lives) via `claude mcp add -s user`. `project` writes a " +
-                    "committed .mcp.json for a shared repo — every teammate still runs `beryl login` to " +
+                    "committed .mcp.json for a shared repo. Every teammate still runs `beryl login` to " +
                     "authenticate",
             },
             {
@@ -285,8 +285,8 @@ export const initCommands = [
         description: "The full guide to authoring durable, healable tests: the ActionPlan shape, outcome " +
             "assertions, natural-language intent, test accounts and the project mailbox " +
             "({{login_email}}, {{mailbox_address}}, {{inbox_address}} + await_email), and the " +
-            "local run-fix loop. Same content as the beryl-test skill `beryl init` installs — " +
-            `skip if a loaded beryl-test skill states v${cliVersion()}; else call this first ` +
+            "local run-fix loop. Same content as the beryl-test skill `beryl init` installs. " +
+            `Skip if a loaded beryl-test skill states v${cliVersion()}; else call this first ` +
             "(works without logging in).",
         examples: ["beryl guide"],
         async run() {

package/dist/commands/mailboxes.js CHANGED Viewed

@@ -7,10 +7,10 @@ export const mailboxCommands = [
         name: "mailbox get",
         summary: "The project's mailbox address",
         groupDefault: true,
-        groupSummary: "The project's standing email addresses — where its tests receive sign-in mail.",
+        groupSummary: "The project's standing email addresses, where its tests receive sign-in mail.",
         description: "Returns the address {{mailbox_address}} resolves to, creating it on first ask. " +
             "Every test that reads mail receives here. A test needing an address the site has " +
-            "never seen cites {{inbox_address}} instead — that renders a `+tag` alias of this " +
+            "never seen cites {{inbox_address}} instead. That renders a `+tag` alias of this " +
             "same mailbox, so a signup stays repeatable without a second address to manage.",
         scope: "project",
         async run(ctx, input) {
@@ -46,7 +46,7 @@ export const mailboxCommands = [
         name: "mailbox create",
         summary: "Add a second mailbox to the project",
         description: "Only needed when a flow requires two genuinely separate inboxes at the same time " +
-            "— both sides of an invite handshake. For an address the site has not seen before, " +
+            "(both sides of an invite handshake). For an address the site has not seen before, " +
             "cite {{inbox_address}} in the plan instead: it aliases the existing mailbox and " +
             "costs nothing to manage.",
         scope: "project",
@@ -88,12 +88,12 @@ export const mailboxCommands = [
         name: "mailbox read",
         summary: "Read the latest email in a mailbox (waits for one to arrive)",
         description: "Waits up to --timeout-s for a matching email and returns it (one blocking request; " +
-            "the server caps the wait at 50s — re-run to keep waiting). With --extract-code, " +
+            "the server caps the wait at 50s, so re-run to keep waiting). With --extract-code, " +
             "also asks the server to pull the one-time code out of the email (AI-assisted when " +
             "the email is ambiguous; `code` is null if none was found). Use " +
             "--recipient-contains to read only one `+tag` alias's mail when several identities " +
             "share the mailbox. Exits non-zero if nothing arrives before the timeout. Waits for " +
-            "and returns ONE latest matching email — `mailbox emails` lists what has already " +
+            "and returns ONE latest matching email. `mailbox emails` lists what has already " +
             "arrived, without waiting.",
         scope: "project",
         args: [{ name: "mailbox-id", description: "Mailbox id from `beryl mailbox list`", required: true }],
@@ -154,7 +154,7 @@ export const mailboxCommands = [
     {
         name: "mailbox emails",
         summary: "List the emails a mailbox has received",
-        description: "Returns the already-received emails without waiting — `mailbox read` blocks for " +
+        description: "Returns the already-received emails without waiting. `mailbox read` blocks for " +
             "a matching one and returns just it.",
         scope: "project",
         args: [{ name: "mailbox-id", description: "Mailbox id from `beryl mailbox list`", required: true }],

package/dist/commands/mcp.js CHANGED Viewed

@@ -3,9 +3,9 @@ export const mcpCommands = [
     {
         name: "version",
         summary: "Show the running CLI version, API URL, and Node version",
-        description: "Answers \"which build am I actually talking to?\" — the one question a long-lived " +
+        description: "Answers \"which build am I actually talking to?\" (the one question a long-lived " +
             "`beryl mcp` process can't otherwise answer, since it loads source at spawn and never " +
-            "hot-reloads. Needs no login, so it still works when a token is missing or broken. " +
+            "hot-reloads). Needs no login, so it still works when a token is missing or broken. " +
             "Also reports whether the running build is behind npm's `latest` (best-effort: " +
             "`update_available` is null when the registry can't be reached, and the check is " +
             "skipped entirely under BERYL_NO_UPDATE_CHECK).",
@@ -26,7 +26,7 @@ export const mcpCommands = [
     },
     {
         name: "mcp",
-        summary: "Run the Beryl MCP server (stdio) — every CLI command as an agent tool",
+        summary: "Run the Beryl MCP server (stdio): every CLI command as an agent tool",
         description: "Exposes the CLI's commands as MCP tools over stdio, so coding agents (Claude Code, " +
             "Cursor, …) can create projects, trigger runs, watch the agent, and edit tests. " +
             "Authenticate via BERYL_API_KEY or a prior `beryl login`.",

package/dist/commands/projects.js CHANGED Viewed

@@ -37,7 +37,7 @@ export const projectCommands = [
         summary: "List projects in the workspace",
         scope: "workspace",
         groupDefault: true,
-        groupSummary: "Create and manage projects — a site Beryl explores, authors tests for, and runs.",
+        groupSummary: "Create and manage projects: a site Beryl explores, authors tests for, and runs.",
         async run(ctx, input) {
             const ws = await ctx.requireWorkspace(input);
             const rows = (await ctx.client.get(`/workspaces/${ws}/projects`));
@@ -70,7 +70,7 @@ export const projectCommands = [
     },
     {
         name: "projects create",
-        summary: "Create a project — with a URL the agent starts exploring; with just --name an empty one",
+        summary: "Create a project. With a URL the agent starts exploring; with just --name an empty one",
         scope: "workspace",
         args: [
             {
@@ -91,13 +91,13 @@ export const projectCommands = [
                 type: "string",
                 enum: ["public", "gated"],
                 description: "Whether the site needs a login (gated) or not (public). Default: detected from the " +
-                    "site — only asked when detection is genuinely unsure",
+                    "site, and only asked when detection is genuinely unsure",
             },
             { name: "force-new-login", type: "boolean", description: "Ignore any reusable saved login" },
             {
                 name: "no-explore",
                 type: "boolean",
-                description: "Create the project without starting the cloud exploration — author tests yourself " +
+                description: "Create the project without starting the cloud exploration. Author tests yourself " +
                     "via `beryl tests create` or your coding agent over MCP",
             },
             { name: "watch", type: "boolean", description: "Stream the agent's exploration live" },
@@ -190,7 +190,7 @@ export const projectCommands = [
     },
     {
         name: "projects re-explore",
-        summary: "Send the agent back in — run/heal existing tests and discover new flows",
+        summary: "Send the agent back in to run/heal existing tests and discover new flows",
         scope: "project",
         flags: [
             { name: "watch", type: "boolean", description: "Stream the agent's exploration live" },

package/dist/commands/runs.js CHANGED Viewed

@@ -50,7 +50,7 @@ export const runCommands = [
         name: "runs trigger",
         summary: "Trigger a test run (whole suite, a subset, or one environment)",
         description: "Runs execute in Beryl's cloud. With --watch the CLI streams live progress and " +
-            "exits 0 only if every test passed — wire it straight into CI. A run with a " +
+            "exits 0 only if every test passed, so wire it straight into CI. A run with a " +
             "heal-eligible failure completes only after Beryl has tried to heal it: a repaired " +
             "test is re-run inside the same run and counts as passed (reported as `healed`), so " +
             "the final counts, the report and the completion email all reflect the repair.",
@@ -60,7 +60,7 @@ export const runCommands = [
             {
                 name: "group",
                 type: "string",
-                description: "Run only the active tests in this group (by name) — resolved to ids before the run, " +
+                description: "Run only the active tests in this group (by name), resolved to ids before the run, " +
                     "so the run records exactly what it ran. Cannot be combined with --test.",
             },
             { name: "env", type: "string", description: "Environment id to run against" },
@@ -116,7 +116,7 @@ export const runCommands = [
     {
         name: "runs local",
         summary: "Run tests on your machine with your own Playwright; results sync to Beryl",
-        description: "Unlike `runs trigger`, the browser runs on YOUR machine — each test's rendered spec is " +
+        description: "Unlike `runs trigger`, the browser runs on YOUR machine: each test's rendered spec is " +
             "fetched and run with your local @playwright/test and the Chromium binary it drives. " +
             "Both are checked once before any spec is fetched, so a machine that can't run tests " +
             "says so once instead of failing every test (on a terminal the CLI offers to install " +
@@ -129,12 +129,12 @@ export const runCommands = [
             "does, and scrubbed from any error text or DOM snapshot before results upload; a test " +
             "whose account has no stored password is skipped with the exact fix-it command. When the " +
             "run finishes, the results and replay artifacts are imported into Beryl as a normal run " +
-            "(trigger source `local`) — history, replay, and reports all work; pass --no-sync to " +
+            "(trigger source `local`), so history, replay, and reports all work; pass --no-sync to " +
             "keep a run entirely off the record while iterating. Session-mode tests behave as " +
             "in the cloud: their account signs in once per invocation and every session-mode " +
             "test rides that session; a failed sign-in fails those tests with the same " +
             "SESSION_* reason a cloud run reports. Only a test that depends on a session Beryl " +
-            "captured server-side is skipped, with a note — run those with `runs trigger`. Point " +
+            "captured server-side is skipped, with a note. Run those with `runs trigger`. Point " +
             "--url-override at a local dev server or preview, and --dir to keep specs, artifacts, " +
             "and reports on disk. Exits 0 only if every executed test passed.",
         scope: "project",
@@ -164,7 +164,7 @@ export const runCommands = [
             {
                 name: "env",
                 type: "string",
-                description: "Environment id to run against and attach the imported run to — use for a " +
+                description: "Environment id to run against and attach the imported run to. Use for a " +
                     "standing environment; --url-override is for a throwaway host",
             },
             {
@@ -531,8 +531,8 @@ export const runCommands = [
         summary: "Show one run with its per-test results",
         description: "Over MCP the failure screenshots come back as viewable image content, so an agent can " +
             "look at the page that broke instead of guessing from the error string. Set screenshots " +
-            "to false to skip fetching them. Ignored outside MCP — the terminal cannot show an image. " +
-            "Returns the run row with its per-test results — `runs report` returns the generated " +
+            "to false to skip fetching them. Ignored outside MCP (the terminal cannot show an image). " +
+            "Returns the run row with its per-test results. `runs report` returns the generated " +
             "report document, `runs explain` an AI explanation of one failed result.",
         scope: "project",
         args: [{ name: "run-id", description: "Run id", required: true }],
@@ -585,7 +585,7 @@ export const runCommands = [
     {
         name: "runs report",
         summary: "Show the generated report for a run",
-        description: "Returns the run's stored generated report (404 until it has been generated) — " +
+        description: "Returns the run's stored generated report (404 until it has been generated). " +
             "`runs get` returns the raw run row with per-test results.",
         scope: "project",
         args: [{ name: "run-id", description: "Run id", required: true }],
@@ -599,8 +599,8 @@ export const runCommands = [
     {
         name: "runs download",
         summary: "Download a run's results, with its artifacts, to disk",
-        description: "With --dir, fetches the artifact bytes — screenshots, DOM snapshots, the Playwright " +
-            "trace zip, and the filmstrip frames of the failing tests — into <dir>/<test-result-id>/ " +
+        description: "With --dir, fetches the artifact bytes (screenshots, DOM snapshots, the Playwright " +
+            "trace zip, and the filmstrip frames of the failing tests) into <dir>/<test-result-id>/ " +
             "alongside a run.json manifest. Artifact URLs are short-lived, so download rather than " +
             "stash them. With --out (or neither), writes only the JSON manifest.",
         scope: "project",
@@ -667,7 +667,7 @@ export const runCommands = [
         name: "runs explain",
         summary: "Explain, with AI, why a test result failed",
         description: "Takes a single test-RESULT id (not a run id) and returns an AI failure " +
-            "explanation for that result — `runs get` lists a run's results and their ids.",
+            "explanation for that result. `runs get` lists a run's results and their ids.",
         scope: "project",
         args: [{ name: "result-id", description: "Test result id (from `beryl runs get`)", required: true }],
         async run(ctx, input) {

package/dist/commands/tests.js CHANGED Viewed

@@ -80,7 +80,7 @@ export const testCommands = [
     {
         name: "tests lint",
         summary: "Validate a plan JSON file offline, before sending it to the server",
-        description: "Checks a plan against the published ActionPlan JSON Schema — every action's required " +
+        description: "Checks a plan against the published ActionPlan JSON Schema: every action's required " +
             "fields, plus the two structural rules (the first EXECUTED step must be a goto, and at " +
             "least one step across before + steps must be an expect). Runs entirely locally, so a " +
             "malformed plan fails here instead of costing a server round-trip. " +
@@ -110,7 +110,7 @@ export const testCommands = [
             "unless --page is given; pass --page to walk a large project a slice at a time.",
         scope: "project",
         groupDefault: true,
-        groupSummary: "Author, inspect, version, and heal a project's tests — the checks Beryl runs on each run.",
+        groupSummary: "Author, inspect, version, and heal a project's tests: the checks Beryl runs on each run.",
         flags: [
             { name: "env", type: "string", description: "Filter by environment id" },
             {
@@ -172,7 +172,7 @@ export const testCommands = [
         name: "tests get",
         summary: "Show one test",
         description: "Returns the test's metadata row (status, flags, per-environment last result), not " +
-            "the plan — `tests plan` prints the stored JSON plan, `tests script` the rendered " +
+            "the plan. `tests plan` prints the stored JSON plan, `tests script` the rendered " +
             "Playwright spec.",
         scope: "project",
         args: [{ name: "test-id", description: "Test id", required: true }],
@@ -184,7 +184,7 @@ export const testCommands = [
     {
         name: "tests plan",
         summary: "Print a test's current step plan (JSON)",
-        description: "Returns the stored json_plan of the test's current version — `tests get` returns " +
+        description: "Returns the stored json_plan of the test's current version. `tests get` returns " +
             "the metadata row, `tests script` the rendered Playwright spec.",
         scope: "project",
         args: [{ name: "test-id", description: "Test id", required: true }],
@@ -198,30 +198,30 @@ export const testCommands = [
     },
     {
         name: "tests create",
-        summary: "Create a test case from a JSON action plan — for tests authored locally, e.g. by your coding agent",
+        summary: "Create a test case from a JSON action plan (for tests authored locally, e.g. by your coding agent)",
         description: "The plan is a JSON object whose steps are {action, selector, url, value, ...}: the first " +
             "EXECUTED step must be a goto, and at least one step must be an expect. Before anything is " +
             "banked, the plan is proven by replaying it in a browser ON YOUR MACHINE with your local " +
-            "@playwright/test: the server renders the spec (`tests/compile`), the CLI runs it — minting " +
+            "@playwright/test: the server renders the spec (`tests/compile`), the CLI runs it (minting " +
             "a run inbox for await_email steps and resolving the saved login exactly as a cloud run " +
-            "would — and only a green replay creates the test (bound to the replayed plan by its hash). " +
+            "would), and only a green replay creates the test (bound to the replayed plan by its hash). " +
             "This holds over MCP too: the replay runs on the machine hosting the MCP server, never on " +
             "Beryl's; if @playwright/test is missing there the tool returns the install commands (on a " +
             "terminal the CLI offers to install it). " +
             "A red replay banks NOTHING: the failure evidence comes back (over MCP the screenshot is " +
             "image content), you fix the plan file and re-run. The proving run is imported as the " +
             "test's first run (--no-sync to skip). A plan that signs in with a session Beryl captured " +
-            "server-side cannot replay locally (that session never leaves Beryl's cloud) — it falls " +
+            "server-side cannot replay locally (that session never leaves Beryl's cloud). It falls " +
             "back to server-side verification automatically, and says so. A session-mode plan replays locally " +
             "fine: the server renders it with its account's stored sign-in steps in front, so " +
             "the same identity is exercised on your machine. Optional `before` and `after` arrays hold setup and teardown " +
             "steps: `after` runs even when a main step fails, which is how a create/update/delete test " +
             "cleans up the record it made on the runs that go red. " +
-            "Recovery: a 409 `duplicate_title` carries existing_test_id + existing_plan_hash — " +
+            "Recovery: a 409 `duplicate_title` carries existing_test_id + existing_plan_hash, so " +
             "reconcile with that test (`tests get` / `tests set-plan`), don't rename-and-retry; a " +
             "409 `plan_hash_mismatch` means the submitted plan is not the bytes that were replayed " +
-            "— re-run `tests create`; a 429 with Retry-After 30 means the verify slots are " +
-            "saturated — wait and retry.",
+            "(re-run `tests create`); a 429 with Retry-After 30 means the verify slots are " +
+            "saturated (wait and retry).",
         scope: "project",
         flags: [
             { name: "title", type: "string", required: true, description: "Title for the new test" },
@@ -229,26 +229,26 @@ export const testCommands = [
             {
                 name: "description",
                 type: "string",
-                description: "1–3 sentences stating what this test proves — the immutable outcome Beryl's healing " +
+                description: "One to three sentences stating what this test proves: the immutable outcome Beryl's healing " +
                     "checks against. State the purpose, not the steps; the one observable signal that's true " +
                     "only if the flow worked.",
             },
             {
                 name: "no-verify",
                 type: "boolean",
-                description: "Skip verification entirely — bank the authored plan as-is, unproven",
+                description: "Skip verification entirely: bank the authored plan as-is, unproven",
             },
             {
                 name: "url-override",
                 type: "string",
                 description: "Replay against this base URL instead of the environment's (e.g. http://localhost:3000). " +
-                    "The banked test is then unproven against its real environment — the CLI says so.",
+                    "The banked test is then unproven against its real environment, and the CLI says so.",
             },
             {
                 name: "group",
                 type: "strings",
                 description: "Put the test in an existing project group (by name), repeatable. An unknown " +
-                    "name is an error — create groups with `beryl groups create`. Omit for no group.",
+                    "name is an error (create groups with `beryl groups create`). Omit for no group.",
             },
             { name: "env", type: "string", description: "Environment id to compile and prove against" },
             {
@@ -480,9 +480,9 @@ export const testCommands = [
         name: "tests set-plan",
         summary: "Replace a test's step plan from a JSON file (creates a new version)",
         description: "Accepts the same plan shape as `tests create`, including the optional `before` and " +
-            "`after` sections — `after` runs on pass and on fail, so cleanup happens even when the " +
+            "`after` sections. `after` runs on pass and on fail, so cleanup happens even when the " +
             "test goes red. Pass `--description` when the re-authored plan changes what the test " +
-            "proves; omit it to keep the test's existing intent. Saves the edit with NO replay — " +
+            "proves; omit it to keep the test's existing intent. Saves the edit with NO replay: " +
             "it rides into the next run unproven; `tests recompile` is the verify-first " +
             "alternative.",
         scope: "project",
@@ -492,7 +492,7 @@ export const testCommands = [
             {
                 name: "description",
                 type: "string",
-                description: "1–3 sentences stating what this test proves — the immutable outcome Beryl's healing " +
+                description: "One to three sentences stating what this test proves: the immutable outcome Beryl's healing " +
                     "checks against. State the purpose, not the steps; the one observable signal that's true " +
                     "only if the flow worked. Omit to keep the test's existing intent.",
             },
@@ -527,7 +527,7 @@ export const testCommands = [
         name: "tests set-groups",
         summary: "Replace the groups a test belongs to",
         description: "Groups are project-defined labels used to filter, run, or schedule a slice of the " +
-            "suite (`beryl runs trigger --group <name>`). This REPLACES the whole set — pass every " +
+            "suite (`beryl runs trigger --group <name>`). This REPLACES the whole set: pass every " +
             "group you want, or none to clear it. Names must already exist in the project " +
             "(`beryl groups list`); an unknown name is an error, never a new group.",
         scope: "project",
@@ -555,13 +555,13 @@ export const testCommands = [
     {
         name: "tests quarantine",
         summary: "Mute a flaky test: it keeps running, but its failures stop failing the run",
-        description: "A quarantined test still executes and its result is still recorded and visible — its " +
+        description: "A quarantined test still executes and its result is still recorded and visible. Its " +
             "red lands in the run's quarantined_count and gates neither the run's verdict nor exit " +
             "codes, so it can't red-light a deploy. Use " +
             "it on a persistently flaky test instead of deleting it (which destroys the history) or " +
             "asking support to deactivate it (which stops it running at all). After 5 consecutive " +
-            "clean passes the test reports rehab_ready — advisory only, nothing un-quarantines " +
-            "itself. `off` un-quarantines.",
+            "clean passes the test reports rehab_ready (advisory only, nothing un-quarantines " +
+            "itself). `off` un-quarantines.",
         scope: "project",
         args: [
             { name: "test-id", description: "Test id", required: true },
@@ -598,11 +598,11 @@ export const testCommands = [
         summary: "Validate + verify an edited plan against the live site before persisting",
         description: "Unlike `tests set-plan` (which saves the edit and lets it ride into the next run), " +
             "this replays the edited plan against the live site before anything persists. A " +
-            "deterministic replay failure (verdict `drop`) REJECTS the edit — persisted:false, " +
-            "the prior plan stays live — and returns the failure evidence (over MCP the " +
+            "deterministic replay failure (verdict `drop`) REJECTS the edit (persisted:false, " +
+            "the prior plan stays live) and returns the failure evidence (over MCP the " +
             "screenshot is image content). Verdict `flag` (the runner errored, no verdict on " +
             "the flow) persists the plan but reports it unverified. Returns 429 with " +
-            "Retry-After 30 when the 2 inline-verify slots are saturated — wait and retry.",
+            "Retry-After 30 when the 2 inline-verify slots are saturated (wait and retry).",
         scope: "project",
         args: [{ name: "test-id", description: "Test id", required: true }],
         flags: [
@@ -671,7 +671,7 @@ export const testCommands = [
     {
         name: "tests restore",
         summary: "Restore a test to an earlier version",
-        description: "Copies the named older version's plan forward as a NEW head version — unlike " +
+        description: "Copies the named older version's plan forward as a NEW head version, unlike " +
             "`tests reset`, which flips authored_by back to `system` and leaves the plan " +
             "untouched.",
         scope: "project",
@@ -690,7 +690,7 @@ export const testCommands = [
         name: "tests reset",
         summary: "Discard user edits and return the test to its latest system-authored version",
         description: "Flips authored_by back to `system` WITHOUT changing the plan (the next " +
-            "regeneration overwrites it) — unlike `tests restore`, which copies an older " +
+            "regeneration overwrites it), unlike `tests restore`, which copies an older " +
             "version's plan forward as a new version.",
         scope: "project",
         args: [{ name: "test-id", description: "Test id", required: true }],
@@ -739,9 +739,9 @@ export const testCommands = [
         name: "tests script",
         summary: "Print the rendered Playwright spec for a test (or an unbanked plan file)",
         description: "With a test id, fetches the banked test's rendered .spec.ts. With --file, compiles a " +
-            "plan JSON that has NOT been banked yet — the same render `tests create` proves locally — " +
+            "plan JSON that has NOT been banked yet (the same render `tests create` proves locally) " +
             "so you can inspect exactly what would run before creating anything. This returns the " +
-            "executable spec — `tests plan` returns the stored JSON plan it is rendered from, " +
+            "executable spec. `tests plan` returns the stored JSON plan it is rendered from, " +
             "`tests get` the metadata row.",
         scope: "project",
         args: [{ name: "test-id", description: "Test id (omit when passing --file)" }],

package/package.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
   "name": "@beryl-so/cli",
-  "version": "0.32.0",
-  "description": "Beryl on the command line — projects, runs, the exploring agent, and an MCP server over the same commands.",
+  "version": "0.33.0",
+  "description": "Beryl on the command line \u2014 projects, runs, the exploring agent, and an MCP server over the same commands.",
   "license": "MIT",
   "type": "module",
   "homepage": "https://beryl.so/docs/cli",