stably 4.12.3 → 4.12.4

package/dist/stably-plugin-cli/skills/playwright-config-auth/SKILL.md

@@ -54,7 +54,7 @@ Check if the target project's `testMatch` pattern will cover your new test file:
 2. If your new file won't match (e.g., `testMatch: ['**/seed.spec.ts']` won't match `my-test.spec.ts`):
    - Either update `testMatch` to include the new file (e.g., `['**/seed.spec.ts', '**/my-test.spec.ts']`)
    - Or use a broader pattern (e.g., `tests/isolated/*.spec.ts` and place files there)
-3. After editing config: clear cache and verify with `playwright-cli run-test`
+3. After editing config: clear cache and verify with `stably-browser run-test`
 
 ### Adding an Isolated Project (REQUIRED for No-Auth Tests)
 
@@ -81,10 +81,10 @@ Common patterns: `**/seed.spec.ts`, `**/setup.spec.ts`, or `tests/isolated/*.spe
 
 1. Clear Playwright cache: `rm -rf /tmp/playwright-transform-cache-* 2>/dev/null || true`
 2. Restart MCP servers to pick up the config change
-3. **Verify your test runs under the correct project** with `playwright-cli run-test <file> --project=<project>`
+3. **Verify your test runs under the correct project** with `stably-browser run-test <file> --project=<project>`
 4. If your test runs under a project with auth dependencies (e.g., `all`), do NOT proceed - fix the project matching first
 5. **If test runs under multiple projects**, add `testIgnore` to the unintended projects to exclude your test file
-6. Use the new project: `playwright-cli run-test <file> --project=isolated`
+6. Use the new project: `stably-browser run-test <file> --project=isolated`
 
 ### If Setup Takes Too Long or Runs Auth Unexpectedly
 
@@ -110,7 +110,7 @@ When the repository uses authentication via project dependencies (a common patte
 
 ### The Solution
 
-1. **Specify a project with auth dependencies**: When running `playwright-cli run-test`, explicitly specify a project that has `dependencies: ["auth"]` (e.g., `--project=chromium`, `--project=mobile-safari`)
+1. **Specify a project with auth dependencies**: When running `stably-browser run-test`, explicitly specify a project that has `dependencies: ["auth"]` (e.g., `--project=chromium`, `--project=mobile-safari`)
 
 2. **Check for auth skip conditions**: If auth tests are being skipped, inspect auth test file (e.g., `*.auth.ts`) and related setup files for skip conditions. Look for environment variables or configuration that forces re-authentication.
 
@@ -121,7 +121,7 @@ When the repository uses authentication via project dependencies (a common patte
 1. Read `playwright.config.ts` and identify projects with `dependencies: ["auth"]` (e.g., `chromium`, `mobile-safari`)
 2. Check auth test files for skip conditions or environment variables
 3. Create test file using repository's normal auth pattern (via storageState from fixtures)
-4. Run `playwright-cli run-test <file> --project=chromium`
+4. Run `stably-browser run-test <file> --project=chromium`
 5. Auth project runs automatically as dependency -> creates auth files -> test runs authenticated
 
 ### What NOT to Do
@@ -135,7 +135,7 @@ When the repository uses authentication via project dependencies (a common patte
 If config has auth project dependencies (e.g., `chromium` with `dependencies: ["auth"]`), you MUST specify that project when running tests.
 
 ```bash
-playwright-cli run-test tests/my-test.spec.ts --project=chromium
+stably-browser run-test tests/my-test.spec.ts --project=chromium
 ```
 
 **Do NOT omit the `--project` flag** - auth will not run without specifying a project that has auth dependencies.
@@ -170,7 +170,7 @@ schedules:
 
 ## Test Execution Project Selection (CRITICAL)
 
-This section covers how to select the right project when running tests with `playwright-cli run-test`.
+This section covers how to select the right project when running tests with `stably-browser run-test`.
 
 ### Rule 1: Add an Isolated Project for Independent Tests
 
@@ -179,7 +179,7 @@ When running tests that DON'T need auth or other project dependencies (e.g., tes
 1. Add an isolated project to `playwright.config.ts` with NO dependencies (see "Adding an Isolated Project" above)
 2. Use that project:
    ```
-   playwright-cli run-test tests/my-test.spec.ts --project=isolated
+   stably-browser run-test tests/my-test.spec.ts --project=isolated
    ```
 
 **Why**: Playwright runs tests under ALL matching projects, not just one. If your test matches a project with `dependencies: ['setup-xyz']`, auth/setup flows will run unexpectedly.

package/dist/stably-plugin-cli/skills/{playwright-cli → stably-browser}/SKILL.md

@@ -1,26 +1,26 @@
 ---
-name: playwright-cli
+name: stably-browser
 description: Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
-allowed-tools: Bash(playwright-cli:*)
+allowed-tools: Bash(stably-browser:*)
 ---
 
-# Browser Automation with playwright-cli
+# Browser Automation with stably-browser
 
 ## Quick start
 
 ```bash
 # open new browser
-playwright-cli open
+stably-browser open
 # navigate to a page
-playwright-cli goto https://playwright.dev
+stably-browser goto https://playwright.dev
 # interact with the page using refs from the snapshot
-playwright-cli click e15
-playwright-cli type "page.click"
-playwright-cli press Enter
+stably-browser click e15
+stably-browser type "page.click"
+stably-browser press Enter
 # take a screenshot (rarely used, as snapshot is more common)
-playwright-cli screenshot
+stably-browser screenshot
 # close the browser
-playwright-cli close
+stably-browser close
 ```
 
 ## Commands
@@ -28,155 +28,155 @@ playwright-cli close
 ### Core
 
 ```bash
-playwright-cli open
+stably-browser open
 # open and navigate right away
-playwright-cli open https://example.com/
-playwright-cli goto https://playwright.dev
-playwright-cli type "search query"
-playwright-cli click e3
-playwright-cli dblclick e7
-playwright-cli fill e5 "user@example.com"
-playwright-cli drag e2 e8
-playwright-cli hover e4
-playwright-cli select e9 "option-value"
-playwright-cli upload ./document.pdf
-playwright-cli check e12
-playwright-cli uncheck e12
-playwright-cli snapshot
-playwright-cli snapshot --filename=after-click.yaml
-playwright-cli eval "document.title"
-playwright-cli eval "el => el.textContent" e5
-playwright-cli dialog-accept
-playwright-cli dialog-accept "confirmation text"
-playwright-cli dialog-dismiss
-playwright-cli resize 1920 1080
-playwright-cli close
+stably-browser open https://example.com/
+stably-browser goto https://playwright.dev
+stably-browser type "search query"
+stably-browser click e3
+stably-browser dblclick e7
+stably-browser fill e5 "user@example.com"
+stably-browser drag e2 e8
+stably-browser hover e4
+stably-browser select e9 "option-value"
+stably-browser upload ./document.pdf
+stably-browser check e12
+stably-browser uncheck e12
+stably-browser snapshot
+stably-browser snapshot --filename=after-click.yaml
+stably-browser eval "document.title"
+stably-browser eval "el => el.textContent" e5
+stably-browser dialog-accept
+stably-browser dialog-accept "confirmation text"
+stably-browser dialog-dismiss
+stably-browser resize 1920 1080
+stably-browser close
 ```
 
 ### Navigation
 
 ```bash
-playwright-cli go-back
-playwright-cli go-forward
-playwright-cli reload
+stably-browser go-back
+stably-browser go-forward
+stably-browser reload
 ```
 
 ### Keyboard
 
 ```bash
-playwright-cli press Enter
-playwright-cli press ArrowDown
-playwright-cli keydown Shift
-playwright-cli keyup Shift
+stably-browser press Enter
+stably-browser press ArrowDown
+stably-browser keydown Shift
+stably-browser keyup Shift
 ```
 
 ### Mouse
 
 ```bash
-playwright-cli mousemove 150 300
-playwright-cli mousedown
-playwright-cli mousedown right
-playwright-cli mouseup
-playwright-cli mouseup right
-playwright-cli mousewheel 0 100
+stably-browser mousemove 150 300
+stably-browser mousedown
+stably-browser mousedown right
+stably-browser mouseup
+stably-browser mouseup right
+stably-browser mousewheel 0 100
 ```
 
 ### Save as
 
 ```bash
-playwright-cli screenshot
-playwright-cli screenshot e5
-playwright-cli screenshot --filename=page.png
-playwright-cli pdf --filename=page.pdf
+stably-browser screenshot
+stably-browser screenshot e5
+stably-browser screenshot --filename=page.png
+stably-browser pdf --filename=page.pdf
 ```
 
 ### Tabs
 
 ```bash
-playwright-cli tab-list
-playwright-cli tab-new
-playwright-cli tab-new https://example.com/page
-playwright-cli tab-close
-playwright-cli tab-close 2
-playwright-cli tab-select 0
+stably-browser tab-list
+stably-browser tab-new
+stably-browser tab-new https://example.com/page
+stably-browser tab-close
+stably-browser tab-close 2
+stably-browser tab-select 0
 ```
 
 ### Storage
 
 ```bash
-playwright-cli state-save
-playwright-cli state-save auth.json
-playwright-cli state-load auth.json
+stably-browser state-save
+stably-browser state-save auth.json
+stably-browser state-load auth.json
 
 # Cookies
-playwright-cli cookie-list
-playwright-cli cookie-list --domain=example.com
-playwright-cli cookie-get session_id
-playwright-cli cookie-set session_id abc123
-playwright-cli cookie-set session_id abc123 --domain=example.com --httpOnly --secure
-playwright-cli cookie-delete session_id
-playwright-cli cookie-clear
+stably-browser cookie-list
+stably-browser cookie-list --domain=example.com
+stably-browser cookie-get session_id
+stably-browser cookie-set session_id abc123
+stably-browser cookie-set session_id abc123 --domain=example.com --httpOnly --secure
+stably-browser cookie-delete session_id
+stably-browser cookie-clear
 
 # LocalStorage
-playwright-cli localstorage-list
-playwright-cli localstorage-get theme
-playwright-cli localstorage-set theme dark
-playwright-cli localstorage-delete theme
-playwright-cli localstorage-clear
+stably-browser localstorage-list
+stably-browser localstorage-get theme
+stably-browser localstorage-set theme dark
+stably-browser localstorage-delete theme
+stably-browser localstorage-clear
 
 # SessionStorage
-playwright-cli sessionstorage-list
-playwright-cli sessionstorage-get step
-playwright-cli sessionstorage-set step 3
-playwright-cli sessionstorage-delete step
-playwright-cli sessionstorage-clear
+stably-browser sessionstorage-list
+stably-browser sessionstorage-get step
+stably-browser sessionstorage-set step 3
+stably-browser sessionstorage-delete step
+stably-browser sessionstorage-clear
 ```
 
 ### Network
 
 ```bash
-playwright-cli route "**/*.jpg" --status=404
-playwright-cli route "https://api.example.com/**" --body='{"mock": true}'
-playwright-cli route-list
-playwright-cli unroute "**/*.jpg"
-playwright-cli unroute
+stably-browser route "**/*.jpg" --status=404
+stably-browser route "https://api.example.com/**" --body='{"mock": true}'
+stably-browser route-list
+stably-browser unroute "**/*.jpg"
+stably-browser unroute
 ```
 
 ### DevTools
 
 ```bash
-playwright-cli console
-playwright-cli console warning
-playwright-cli network
-playwright-cli run-code "async page => await page.context().grantPermissions(['geolocation'])"
-playwright-cli tracing-start
-playwright-cli tracing-stop
-playwright-cli video-start
-playwright-cli video-stop video.webm
+stably-browser console
+stably-browser console warning
+stably-browser network
+stably-browser run-code "async page => await page.context().grantPermissions(['geolocation'])"
+stably-browser tracing-start
+stably-browser tracing-stop
+stably-browser video-start
+stably-browser video-stop video.webm
 ```
 
 ## Open parameters
 ```bash
 # Use specific browser when creating session
-playwright-cli open --browser=chrome
-playwright-cli open --browser=firefox
-playwright-cli open --browser=webkit
-playwright-cli open --browser=msedge
+stably-browser open --browser=chrome
+stably-browser open --browser=firefox
+stably-browser open --browser=webkit
+stably-browser open --browser=msedge
 # Connect to browser via extension
-playwright-cli open --extension
+stably-browser open --extension
 
 # Use persistent profile (by default profile is in-memory)
-playwright-cli open --persistent
+stably-browser open --persistent
 # Use persistent profile with custom directory
-playwright-cli open --profile=/path/to/profile
+stably-browser open --profile=/path/to/profile
 
 # Start with config file
-playwright-cli open --config=my-config.json
+stably-browser open --config=my-config.json
 
 # Close the browser
-playwright-cli close
+stably-browser close
 # Delete user data for the default session
-playwright-cli delete-data
+stably-browser delete-data
 ```
 
 ## Snapshots
@@ -184,15 +184,15 @@ playwright-cli delete-data
 Every command that changes page state (`open`, `goto`, `click`, `fill`, `run-test`, etc.) returns a snapshot with the current page refs. **Use refs from the most recent command output immediately — never reuse refs from a previous command's snapshot.**
 
 ```bash
-> playwright-cli goto https://example.com
+> stably-browser goto https://example.com
 ### Page
 - Page URL: https://example.com/
 - Page Title: Example Domain
 ### Snapshot
-[Snapshot](.playwright-cli/page-2026-02-14T19-22-42-679Z.yml)
+[Snapshot](.stably-browser/page-2026-02-14T19-22-42-679Z.yml)
 ```
 
-**Avoid redundant snapshots.** After `playwright-cli open <url>` or `playwright-cli goto <url>`, the snapshot is already returned in the command output — Read that snapshot file directly instead of calling `playwright-cli snapshot` again. Only use `playwright-cli snapshot` when you need to re-inspect the page without performing any action.
+**Avoid redundant snapshots.** After `stably-browser open <url>` or `stably-browser goto <url>`, the snapshot is already returned in the command output — Read that snapshot file directly instead of calling `stably-browser snapshot` again. Only use `stably-browser snapshot` when you need to re-inspect the page without performing any action.
 
 If `--filename` is not provided, a new snapshot file is created with a timestamp. Default to automatic file naming, use `--filename=` when artifact is a part of the workflow result.
 
@@ -200,27 +200,27 @@ If `--filename` is not provided, a new snapshot file is created with a timestamp
 
 Complex pages (e.g., Bing, large dashboards) can produce snapshot `.yml` files that are too large for the Read tool. When a snapshot is large, the Read tool may truncate it to a persisted output path outside the workspace (e.g., `/root/.claude/...`). Do NOT try to Read or Grep that external path — it will be blocked by the workspace sandbox.
 
-Instead, **Grep the original `.yml` file** in the `.playwright-cli/` directory to search for specific elements (e.g., `Grep` for `button`, `combobox`, or a text label).
+Instead, **Grep the original `.yml` file** in the `.stably-browser/` directory to search for specific elements (e.g., `Grep` for `button`, `combobox`, or a text label).
 
 ## Running Tests
 
-Use `playwright-cli run-test` to execute Playwright tests connected to the managed browser via CDP. If no browser session is open, one is started automatically.
+Use `stably-browser run-test` to execute Playwright tests connected to the managed browser via CDP. If no browser session is open, one is started automatically.
 
 ```bash
 # Run a specific test file (auto-starts browser if needed)
-playwright-cli run-test tests/login.spec.ts
+stably-browser run-test tests/login.spec.ts
 
 # Run tests matching a filter
-playwright-cli run-test "login"
+stably-browser run-test "login"
 
 # Run with a specific project (use = syntax)
-playwright-cli run-test --project=chromium tests/login.spec.ts
+stably-browser run-test --project=chromium tests/login.spec.ts
 
 # Run with a visible browser window
-playwright-cli run-test --headed tests/login.spec.ts
+stably-browser run-test --headed tests/login.spec.ts
 
 # Show help
-playwright-cli run-test --help
+stably-browser run-test --help
 ```
 
 ### How run-test Works
@@ -237,35 +237,35 @@ playwright-cli run-test --help
 
 This applies when you are running separate test files to check they pass — not when intentionally using `run-test` as a setup/seed mechanism (see "Use run-test as a Setup/Seed Mechanism" above).
 
-**IMPORTANT: `playwright-cli close` must be its own separate Bash call.** Do NOT chain it with other commands (e.g., `playwright-cli close; playwright-cli run-test ...`). The browser is only fully terminated after the Bash command finishes, so chaining means the next command runs on the old browser with stale state.
+**IMPORTANT: `stably-browser close` must be its own separate Bash call.** Do NOT chain it with other commands (e.g., `stably-browser close; stably-browser run-test ...`). The browser is only fully terminated after the Bash command finishes, so chaining means the next command runs on the old browser with stale state.
 
 ```bash
 # CORRECT: Each command is a separate Bash call
-playwright-cli run-test tests/login.spec.ts
-playwright-cli close
-playwright-cli run-test tests/checkout.spec.ts
-playwright-cli close
-playwright-cli run-test tests/settings.spec.ts
+stably-browser run-test tests/login.spec.ts
+stably-browser close
+stably-browser run-test tests/checkout.spec.ts
+stably-browser close
+stably-browser run-test tests/settings.spec.ts
 ```
 
 ```bash
 # WRONG: Chaining close with run-test in one command
-playwright-cli close; playwright-cli run-test tests/checkout.spec.ts  # ← run-test hits old browser
-playwright-cli close && playwright-cli run-test tests/settings.spec.ts  # ← same problem
+stably-browser close; stably-browser run-test tests/checkout.spec.ts  # ← run-test hits old browser
+stably-browser close && stably-browser run-test tests/settings.spec.ts  # ← same problem
 ```
 
 ```bash
 # WRONG: Running independent tests without resetting — causes cascading failures
-playwright-cli run-test tests/login.spec.ts
-playwright-cli run-test tests/checkout.spec.ts   # ← may fail: browser still has login state from test 1
-playwright-cli run-test tests/settings.spec.ts   # ← may fail: stale cookies/auth from previous tests
+stably-browser run-test tests/login.spec.ts
+stably-browser run-test tests/checkout.spec.ts   # ← may fail: browser still has login state from test 1
+stably-browser run-test tests/settings.spec.ts   # ← may fail: stale cookies/auth from previous tests
 ```
 
-**Why this matters:** The browser is a cloud VM that persists across commands. `playwright-cli close` terminates it, but only after the Bash call returns. If you chain `close; run-test`, the test runs on the old browser before it's terminated. Running `close` as its own Bash call ensures the old browser is fully gone before the next test starts with a fresh one.
+**Why this matters:** The browser is a cloud VM that persists across commands. `stably-browser close` terminates it, but only after the Bash call returns. If you chain `close; run-test`, the test runs on the old browser before it's terminated. Running `close` as its own Bash call ensures the old browser is fully gone before the next test starts with a fresh one.
 
 ### Key Differences from `npx playwright test`
 
-| Feature | `playwright-cli run-test` | `npx playwright test` |
+| Feature | `stably-browser run-test` | `npx playwright test` |
 |---------|--------------------------|----------------------|
 | Browser | Auto-starts and connects to managed browser via CDP | Launches its own browser |
 | State after run | Browser and pages preserved | Browser closed |
@@ -284,7 +284,7 @@ Your environment may enforce a single-session browser policy. When active:
 - Always use the default session — do not use `-s=<name>`.
 - Close the current browser before opening a new one.
 - If the user asks to "open a new browser", close the existing one first.
-- Do not use `playwright-cli list` — there is at most one session.
+- Do not use `stably-browser list` — there is at most one session.
 
 When multi-session is allowed, you may use named sessions as documented below.
 
@@ -292,72 +292,72 @@ When multi-session is allowed, you may use named sessions as documented below.
 
 ```bash
 # create new browser session named "mysession" with persistent profile
-playwright-cli -s=mysession open example.com --persistent
+stably-browser -s=mysession open example.com --persistent
 # same with manually specified profile directory (use when requested explicitly)
-playwright-cli -s=mysession open example.com --profile=/path/to/profile
-playwright-cli -s=mysession click e6
-playwright-cli -s=mysession close  # stop a named browser
-playwright-cli -s=mysession delete-data  # delete user data for persistent session
+stably-browser -s=mysession open example.com --profile=/path/to/profile
+stably-browser -s=mysession click e6
+stably-browser -s=mysession close  # stop a named browser
+stably-browser -s=mysession delete-data  # delete user data for persistent session
 
-playwright-cli list
+stably-browser list
 # Close all browsers
-playwright-cli close-all
+stably-browser close-all
 # Forcefully kill all browser processes
-playwright-cli kill-all
+stably-browser kill-all
 ```
 
 ## Local installation
 
-In some cases user might want to install playwright-cli locally. If running globally available `playwright-cli` binary fails, use `npx playwright-cli` to run the commands. For example:
+In some cases user might want to install stably-browser locally. If running globally available `stably-browser` binary fails, use `npx stably-browser` to run the commands. For example:
 
 ```bash
-npx playwright-cli open https://example.com
-npx playwright-cli click e1
+npx stably-browser open https://example.com
+npx stably-browser click e1
 ```
 
 ## Example: Form submission
 
 ```bash
-playwright-cli open https://example.com/form
+stably-browser open https://example.com/form
 # Read the snapshot file from open's output — no need for a separate snapshot command
 # Use refs (e1, e2, e3) from that snapshot immediately
 
-playwright-cli fill e1 "user@example.com"
-playwright-cli fill e2 "password123"
-playwright-cli click e3
+stably-browser fill e1 "user@example.com"
+stably-browser fill e2 "password123"
+stably-browser click e3
 # click returns a new snapshot — read it to verify the form was submitted
-playwright-cli close
+stably-browser close
 ```
 
 ## Example: Multi-tab workflow
 
 ```bash
-playwright-cli open https://example.com
-playwright-cli tab-new https://example.com/other
-playwright-cli tab-list
-playwright-cli tab-select 0
-playwright-cli snapshot
-playwright-cli close
+stably-browser open https://example.com
+stably-browser tab-new https://example.com/other
+stably-browser tab-list
+stably-browser tab-select 0
+stably-browser snapshot
+stably-browser close
 ```
 
 ## Example: Debugging with DevTools
 
 ```bash
-playwright-cli open https://example.com
-playwright-cli click e4
-playwright-cli fill e7 "test"
-playwright-cli console
-playwright-cli network
-playwright-cli close
+stably-browser open https://example.com
+stably-browser click e4
+stably-browser fill e7 "test"
+stably-browser console
+stably-browser network
+stably-browser close
 ```
 
 ```bash
-playwright-cli open https://example.com
-playwright-cli tracing-start
-playwright-cli click e4
-playwright-cli fill e7 "test"
-playwright-cli tracing-stop
-playwright-cli close
+stably-browser open https://example.com
+stably-browser tracing-start
+stably-browser click e4
+stably-browser fill e7 "test"
+stably-browser tracing-stop
+stably-browser close
 ```
 
 ## Specific tasks

package/dist/stably-plugin-cli/skills/{playwright-cli → stably-browser}/references/request-mocking.md

@@ -6,23 +6,23 @@ Intercept, mock, modify, and block network requests.
 
 ```bash
 # Mock with custom status
-playwright-cli route "**/*.jpg" --status=404
+stably-browser route "**/*.jpg" --status=404
 
 # Mock with JSON body
-playwright-cli route "**/api/users" --body='[{"id":1,"name":"Alice"}]' --content-type=application/json
+stably-browser route "**/api/users" --body='[{"id":1,"name":"Alice"}]' --content-type=application/json
 
 # Mock with custom headers
-playwright-cli route "**/api/data" --body='{"ok":true}' --header="X-Custom: value"
+stably-browser route "**/api/data" --body='{"ok":true}' --header="X-Custom: value"
 
 # Remove headers from requests
-playwright-cli route "**/*" --remove-header=cookie,authorization
+stably-browser route "**/*" --remove-header=cookie,authorization
 
 # List active routes
-playwright-cli route-list
+stably-browser route-list
 
 # Remove a route or all routes
-playwright-cli unroute "**/*.jpg"
-playwright-cli unroute
+stably-browser unroute "**/*.jpg"
+stably-browser unroute
 ```
 
 ## URL Patterns
@@ -41,7 +41,7 @@ For conditional responses, request body inspection, response modification, or de
 ### Conditional Response Based on Request
 
 ```bash
-playwright-cli run-code "async page => {
+stably-browser run-code "async page => {
   await page.route('**/api/login', route => {
     const body = route.request().postDataJSON();
     if (body.username === 'admin') {
@@ -56,7 +56,7 @@ playwright-cli run-code "async page => {
 ### Modify Real Response
 
 ```bash
-playwright-cli run-code "async page => {
+stably-browser run-code "async page => {
   await page.route('**/api/user', async route => {
     const response = await route.fetch();
     const json = await response.json();
@@ -69,7 +69,7 @@ playwright-cli run-code "async page => {
 ### Simulate Network Failures
 
 ```bash
-playwright-cli run-code "async page => {
+stably-browser run-code "async page => {
   await page.route('**/api/offline', route => route.abort('internetdisconnected'));
 }"
 # Options: connectionrefused, timedout, connectionreset, internetdisconnected
@@ -78,7 +78,7 @@ playwright-cli run-code "async page => {
 ### Delayed Response
 
 ```bash
-playwright-cli run-code "async page => {
+stably-browser run-code "async page => {
   await page.route('**/api/slow', async route => {
     await new Promise(r => setTimeout(r, 3000));
     route.fulfill({ body: JSON.stringify({ data: 'loaded' }) });