@beryl-so/cli 0.48.0 → 0.50.0

package/dist/beryl-test-skill.js

@@ -181,19 +181,35 @@ The trade is drift — run 200 has 200 of everything run 1 created. So:
 - **Assert relatively, never absolutely.** "The row I just created is present"
   (\`expect.persisted\` on a \`{{unique}}\`-named row), not "there are 3 rows" — a count
   assertion goes stale by itself.
-- **Own the resource lifecycle, both directions.** Creating? Delete it in \`after\`
-  (runs on pass AND fail, unlike a trailing step inside \`steps\`). Deleting? Create
-  your own victim first — in \`before\` or the opening steps, \`{{unique}}\`-named —
-  then delete it and assert \`gone\`. Never aim a delete at standing data: run 2 would
-  have nothing to delete, and it eats the account's accumulated coverage.
-- **Every test is \`read\` or \`write\`.** \`read\` (the default) only looks. A test
-  that creates, saves, deletes, renames, invites, toggles or uploads anything is
-  \`write\`: bank it with \`--access write\`, and end its \`after\` with an \`expect\`
-  that proves the undo: \`gone\`, \`hidden\`, \`have_count\` or \`count_delta\` for a
-  removal, \`have_text\`, \`have_value\` or \`persisted\` for a restored value.
-  Create refuses a plan that writes without the label and a \`write\` plan
-  without that closing proof; a \`write\` test whose teardown found nothing to remove
-  fails the run. Flip a banked test with \`beryl tests set-access <id> write\`.
+- **Cleanup lives in \`after\`, and it returns the account to the exact state you found
+  it.** \`after\` runs on pass AND fail; a trailing step inside \`steps\` does not, so
+  never put cleanup in \`steps\`.
+  - **Created something?** Delete it in \`after\`.
+  - **Deleting something?** Create your own victim first (in \`before\` or the opening
+    steps, \`{{unique}}\`-named), then delete it and prove \`gone\`; when the deleted thing
+    must persist, re-create it in \`after\` as it was. Never aim a delete at standing data:
+    run 2 has nothing to delete, and it eats the account's accumulated coverage.
+  - **Changed a value (rename, toggle)?** Restore it in \`after\`: set it back to what it
+    was. Capture the original BEFORE you change it with \`capture_text\` (or \`capture_value\`
+    for a form input), banking it under \`capture_as\`, then \`fill {{handle}}\` in \`after\`
+    to put it back.
+- **You label each test \`read\` or \`write\`; Beryl takes your word for it.** Set it with
+  \`--access\` (default \`read\`). Beryl does NOT infer it from your selectors, so YOU
+  decide, by one test: **would the app be different after this test runs?**
+  - **\`write\`** = it leaves a change behind: it creates, edits, deletes, renames, moves,
+    uploads or toggles a record or setting that is still different once the test ends. A
+    \`write\` must undo itself: end \`after\` with an \`expect\` proving the undo: \`gone\`,
+    \`hidden\`, \`have_count\` or \`count_delta\` for a removal, \`have_text\`,
+    \`have_value\` or \`persisted\` for a restore.
+  - **\`read\`** = it only observes: navigating, searching, filtering, sorting, opening a
+    menu or dialog and reading it, or clicking a destructive button and then CANCELLING.
+    Nothing is committed. Opening a confirm dialog and cancelling is a \`read\`; a submit
+    that stays disabled is a \`read\`.
+  A flow that both changes and reads is a \`write\`. Only the \`write\` label is checked
+  (its closing teardown proof, and a \`write\` whose teardown removes nothing fails the
+  run); \`read\` is taken at your word, so a real write you mislabel \`read\` silently
+  drifts the account. Label deliberately, and flip a banked test with
+  \`beryl tests set-access <id> read|write\`.
 
 ### If there is no account yet
 

package/dist/commands/tests.js

@@ -110,8 +110,8 @@ export const testCommands = [
             {
                 name: "access",
                 type: "string",
-                description: "The label the plan will be banked with, read (default) or write; a plan that " +
-                    "creates, edits, deletes or toggles something must be write",
+                description: "The label the plan will be banked with: read (default) or write. It is yours to " +
+                    "set; Beryl does not infer it. Only a write is checked (its closing teardown proof)",
             },
         ],
         examples: [
@@ -580,9 +580,9 @@ export const testCommands = [
     {
         name: "tests set-access",
         summary: "Mark a test read or write",
-        description: "read: the test only reads the app. write: any step creates, edits, renames, deletes " +
-            "or toggles something. The server refuses a plan that writes on a read test, so flip " +
-            "the label before re-authoring such a plan. A write test must clean up in `after`.",
+        description: "read: the test only reads the app. write: it creates, edits, renames, deletes or " +
+            "toggles something that persists. The label is yours to set; Beryl does not infer it " +
+            "from the plan. A write test must clean up in `after`, ending with a proof expect.",
         scope: "project",
         args: [
             { name: "test-id", description: "Test id", required: true },

package/dist/lint.js

@@ -9,9 +9,6 @@ export const MAILBOX_ADDRESS_IN_TEST = "This plan types the standing account's a
     "and rides the account's session; one that needs an address the site can mail cites " +
     "{{inbox_address}}, an alias only this test reads. Only the account's own signup and " +
     "sign-in plans (accounts signup, accounts set-login) may fill {{mailbox_address}}.";
-export const WRITE_NEEDS_LABEL = (label, detail) => `${label} (${detail}) changes the app, so this test must be marked access 'write' ` +
-    "(tests create --access write, or tests set-access <id> write) and clean up in " +
-    "'after'. A 'read' test only reads.";
 export const WRITE_NEEDS_CLOSING_TEARDOWN = (detail) => "A 'write' test must end with an 'after' section that undoes what it changed and " +
     "proves it: the last step of 'after' is an expect with expect_kind 'gone', 'hidden', " +
     "'have_count', 'count_delta' (something removed) or 'have_text', 'have_value', " +
@@ -177,31 +174,6 @@ function identityIssues(plan, provisioning) {
         ? [{ path: "(root)", message: MINTED_IDENTITY_NEEDS_TEARDOWN }]
         : [];
 }
-// Same verb list as the server's write_signal (api/app/ta_shared/schemas.py).
-const WRITE_VERBS_RE = /\b(create|save|delete|remove|rename|revoke|enable|disable|invite|add|publish|archive|restore|quarantine|un-quarantine|turn on|turn off|join|decline)\b/i;
-function writeSignal(plan) {
-    if (typeof plan !== "object" || plan === null)
-        return null;
-    const { before, steps: main, after } = plan;
-    if (steps(after).length > 0)
-        return ["after", "a teardown means something was created"];
-    const sectioned = steps(before).length > 0 || steps(after).length > 0;
-    const label = (section, i) => (sectioned ? `${section}[${i}]` : `step[${i}]`);
-    const all = [
-        ...steps(before).map((s, i) => [label("before", i), s]),
-        ...steps(main).map((s, i) => [label("steps", i), s]),
-    ];
-    for (const [where, s] of all) {
-        if (s.action === "upload")
-            return [where, "upload"];
-        if (s.action === "click" && typeof s.selector === "string") {
-            const hit = WRITE_VERBS_RE.exec(s.selector);
-            if (hit)
-                return [where, `click on '${hit[0]}'`];
-        }
-    }
-    return null;
-}
 const TEARDOWN_PROOF_KINDS = new Set([
     "gone",
     "hidden",
@@ -211,11 +183,11 @@ const TEARDOWN_PROOF_KINDS = new Set([
     "have_value",
     "persisted",
 ]);
+// The read/write label is the author's call; Beryl no longer infers it from the plan.
+// Only a `write` label is checked here: it must close its teardown with a proof.
 function accessIssues(plan, access) {
-    if (access !== "write") {
-        const signal = writeSignal(plan);
-        return signal ? [{ path: "(root)", message: WRITE_NEEDS_LABEL(signal[0], signal[1]) }] : [];
-    }
+    if (access !== "write")
+        return [];
     if (typeof plan !== "object" || plan === null)
         return [];
     const after = steps(plan.after);
@@ -232,7 +204,8 @@ function accessIssues(plan, access) {
 }
 // `provisioning`: the plan is an account's own signup or sign-in plan, the one place
 // {{mailbox_address}} is legal (mirrors the server's validate_editable_plan flag).
-// `access`: the label the plan will be banked with; given, a writing plan needs 'write'.
+// `access`: the label the plan will be banked with. It is the author's call (Beryl no
+// longer infers it from the plan); given, only a `write` is checked, for its closing proof.
 export function lintPlan(plan, opts = {}) {
     const issues = validate(plan, ACTION_PLAN_SCHEMA, ACTION_PLAN_SCHEMA, "");
     // The identity rules read a well-formed plan; a shape error is reported alone.

package/dist/schema.generated.js

@@ -15,6 +15,8 @@ export const ACTION_PLAN_SCHEMA = {
                 "wait_for",
                 "expect",
                 "capture_count",
+                "capture_text",
+                "capture_value",
                 "await_email",
                 "upload",
                 "dialog",
@@ -325,6 +327,62 @@ export const ACTION_PLAN_SCHEMA = {
                         ]
                     }
                 },
+                {
+                    "if": {
+                        "properties": {
+                            "action": {
+                                "const": "capture_text"
+                            }
+                        },
+                        "required": [
+                            "action"
+                        ]
+                    },
+                    "then": {
+                        "properties": {
+                            "capture_as": {
+                                "minLength": 1,
+                                "type": "string"
+                            },
+                            "selector": {
+                                "minLength": 1,
+                                "type": "string"
+                            }
+                        },
+                        "required": [
+                            "capture_as",
+                            "selector"
+                        ]
+                    }
+                },
+                {
+                    "if": {
+                        "properties": {
+                            "action": {
+                                "const": "capture_value"
+                            }
+                        },
+                        "required": [
+                            "action"
+                        ]
+                    },
+                    "then": {
+                        "properties": {
+                            "capture_as": {
+                                "minLength": 1,
+                                "type": "string"
+                            },
+                            "selector": {
+                                "minLength": 1,
+                                "type": "string"
+                            }
+                        },
+                        "required": [
+                            "capture_as",
+                            "selector"
+                        ]
+                    }
+                },
                 {
                     "if": {
                         "properties": {

package/dist/skill-tables.js

@@ -27,6 +27,8 @@ export const ACTION_DOCS = {
     wait_for: "Wait for the `selector` element to appear",
     expect: "Assert — kinds in the expect table below",
     capture_count: "Bank the live count of `selector` matches under `capture_as` for a later `count_delta`",
+    capture_text: "Bank the `selector` element's visible text under `capture_as`, to restore it later via `{{handle}}`",
+    capture_value: "Bank the `selector` input's value under `capture_as`, to restore it later via `{{handle}}`",
     await_email: "Await mail in the run inbox, bank the extracted value under `capture_as` (§5)",
     upload: "Set a file input: `value` names a project config file — see below",
     dialog: "Arm a one-shot accept/dismiss handler for the NEXT step's dialog — see below",

package/package.json

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