peachsim 0.1.570 → 0.1.572

package/skills/{rnx-perf → peach-perf}/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: rnx-perf
-description: Optimize Peach engine and app performance — scroll jank, dropped frames, slow animation, idle CPU, memory growth, and "smooth normally but laggy under load" (video calls, busy machines). Covers measuring on the right thread with the right browser, proving each perf tier actually engages via its counters, a CPU-contention test harness, and the map of existing perf machinery so you improve it instead of reinventing it. For general app debugging load /rnx-debug first.
+name: peach-perf
+description: Optimize Peach engine and app performance — scroll jank, dropped frames, slow animation, idle CPU, memory growth, and "smooth normally but laggy under load" (video calls, busy machines). Covers measuring on the right thread with the right browser, proving each perf tier actually engages via its counters, a CPU-contention test harness, and the map of existing perf machinery so you improve it instead of reinventing it. For general app debugging load /peach-debug first.
 ---
 
 # Peach performance
@@ -11,8 +11,8 @@ this engine followed the same loop — measure on the right thread, read the
 counters that prove machinery engaged, fix the one thing the counters
 indict, remeasure — and every wasted week came from skipping a step.
 
-> needs a connected, pinned sim (`/rnx-setup`). general "what's wrong"
-> triage lives in `/rnx-debug`; this skill goes deeper on perf only.
+> needs a connected, pinned sim (`/peach-setup`). general "what's wrong"
+> triage lives in `/peach-debug`; this skill goes deeper on perf only.
 
 ## the four laws (each paid for by a real incident)
 
@@ -56,7 +56,7 @@ indict, remeasure — and every wasted week came from skipping a step.
 
 ### presentation proof must stay outside the simulator
 
-Performance acceptance must not use `rnx record`, `liveComposite`,
+Performance acceptance must not use `peach record`, `liveComposite`,
 `captureBitmaps`, Chrome screencast, or another in-page frame-copy path. Those
 paths add work to the simulator or browser and can change the cadence being
 measured. Record the visible window with the operating system's native screen
@@ -112,10 +112,10 @@ property on the transform owner can move the whole trajectory to the browser's
 main thread. Paint stable decoration once or give it a distinct layer.
 
 ```sh
-rnx perf shell start          # arm shell frame capture (clears prior)
+peach perf shell start          # arm shell frame capture (clears prior)
 # reproduce — e.g. 8 fling swipes:
-#   for i in {1..8}; do rnx do swipe 196 650 196 250 8 8 --no-wait; sleep 0.9; done
-rnx perf shell stop           # report (add --json for scripting)
+#   for i in {1..8}; do peach do swipe 196 650 196 250 8 8 --no-wait; sleep 0.9; done
+peach perf shell stop           # report (add --json for scripting)
 ```
 
 the report and how to read it:
@@ -244,13 +244,13 @@ identify from its own output is not evidence.
 deeper tools when the frame report isn't enough:
 
 ```sh
-rnx maestro test .maestro/scroll.yaml --profile # per-step + frame stats
-rnx perf cpu --duration 5 --output /tmp/t.cpuprofile   # sampled CPU
-rnx open 8089 --new --driver playwright --cdp-port 9222 # cpu-profile a driveable sim
-rnx debug enable layout,render && rnx debug recent layout 40
+peach maestro test .maestro/scroll.yaml --profile # per-step + frame stats
+peach perf cpu --duration 5 --output /tmp/t.cpuprofile   # sampled CPU
+peach open 8089 --new --driver playwright --cdp-port 9222 # cpu-profile a driveable sim
+peach debug enable layout,render && peach debug recent layout 40
 ```
 
-`rnx perf cpu` writes one profile for the page and one for every attached
+`peach perf cpu` writes one profile for the page and one for every attached
 worker, plus a manifest that labels shell, compositor, tenant, worklet, and
 unknown workers. exit zero requires page, shell, compositor, and tenant plus
 every other discovered target, with each covering at least 99% of the requested

package/skills/{rnx-setup → peach-setup}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: rnx-setup
+name: peach-setup
 description: Get Peach connected to your React Native app with no project setup
 ---
 
@@ -9,48 +9,48 @@ you want to drive a React Native app with Peach from the CLI. this skill
 takes you from a running development server to a connected, pinned sim that
 every other Peach skill assumes exists. Peach requires no project setup or per-app
 install. if
-`rnx describe` already
-returns a tree, you're past this skill — load `/rnx-debug` for
-debugging or `/rnx-test` for writing tests.
+`peach describe` already
+returns a tree, you're past this skill — load `/peach-debug` for
+debugging or `/peach-test` for writing tests.
 
 ## anti-patterns (read first)
 
-- **never `rnx claim --force` a sim held by another CLI.** the lease
+- **never `peach claim --force` a sim held by another CLI.** the lease
   exists for a reason. forcing strands the other agent and corrupts the
-  bridge state. use `rnx open --new` to start a fresh sim instead.
-- **don't switch sims mid-investigation.** pin once with `rnx use
+  bridge state. use `peach open --new` to start a fresh sim instead.
+- **don't switch sims mid-investigation.** pin once with `peach use
   <id>` and keep it pinned. an unpinned command refuses to choose when more
   than one driveable sim is live.
-- **an empty `rnx list` is not "broken Peach".** it usually means the
+- **an empty `peach list` is not "broken Peach".** it usually means the
   daemon is down, the dev server port is wrong, or the runtime is missing.
   walk the recovery checklist before reinstalling.
-- **keep one sim for your whole session.** the first `rnx open <port>`
+- **keep one sim for your whole session.** the first `peach open <port>`
   launches Chrome for Testing with an isolated profile. later opens reuse the
-  saved sim and navigate it in place. use `rnx do reload` when the target
+  saved sim and navigate it in place. use `peach do reload` when the target
   has not changed:
 
   ```sh
-  rnx open 8086                 # first call creates your isolated sim
-  rnx open 8090                 # same sim, different app
-  rnx do reload                 # same sim, same app
-  rnx close <id>                # dispose it when you are done
+  peach open 8086                 # first call creates your isolated sim
+  peach open 8090                 # same sim, different app
+  peach do reload                 # same sim, same app
+  peach close <id>                # dispose it when you are done
   ```
 
   `--new`, `--profile`, and `--ephemeral` create another isolated browser
   tree. use them only when separate storage or a genuinely concurrent sim is
   required. repeated new trees consume enough memory and CPU to starve other
   work on a shared machine.
-- **pin the sim before driving it.** `rnx open` records the new sim for the
+- **pin the sim before driving it.** `peach open` records the new sim for the
   current CLI identity. read its id and pin it explicitly before a longer flow:
 
   ```sh
-  rnx open 8086
-  rnx list
-  rnx use <id>
-  rnx describe --sim <id>
+  peach open 8086
+  peach list
+  peach use <id>
+  peach describe --sim <id>
   ```
 
-- **never retry-loop `rnx open` against a wedged or slow stack.** a
+- **never retry-loop `peach open` against a wedged or slow stack.** a
   connect timeout means diagnose the stack. do not retry. if the first launch
   never connects, each retry can create another browser tree before there is a
   saved sim to reuse. verify the development server and Peach runtime, then
@@ -59,57 +59,57 @@ debugging or `/rnx-test` for writing tests.
 ## first move
 
 ```sh
-rnx daemon status            # the persistent service makes agent commands much faster
-rnx daemon install           # enable it when missing on a supported personal machine
-rnx compat --json            # scan the app's native package compatibility
-rnx open 8081                # load a metro/expo dev server
-rnx list                     # confirm exactly one sim is reachable
-rnx use <id>                 # pin it for the rest of the workflow
-rnx describe                 # smoke test — should print a render tree
+peach daemon status            # the persistent service makes agent commands much faster
+peach daemon install           # enable it when missing on a supported personal machine
+peach compat --json            # scan the app's native package compatibility
+peach open 8081                # load a metro/expo dev server
+peach list                     # confirm exactly one sim is reachable
+peach use <id>                 # pin it for the rest of the workflow
+peach describe                 # smoke test — should print a render tree
 ```
 
 the background service keeps the local bridge and runtime ready between
 commands. without it, Peach still works by starting an on-demand bridge, but
 inspect, interaction, and test commands pay repeated startup cost. if the user
-declined it during onboarding, `rnx daemon install` is the direct way to enable
+declined it during onboarding, `peach daemon install` is the direct way to enable
 it. CI does not need or install the service.
 
-bare `rnx` opens ConnectRN for a human to choose among local apps. agents and
-scripts should use `rnx open <port-or-url>` so the target is explicit.
+bare `peach` opens ConnectRN for a human to choose among local apps. agents and
+scripts should use `peach open <port-or-url>` so the target is explicit.
 
-if you do not know the port, run `rnx open` with no target and pick from
+if you do not know the port, run `peach open` with no target and pick from
 the detected dev servers. for hosted or unusual targets, pass the URL
 explicitly:
 
 ```sh
-rnx open 8081                  # load a metro dev server
-rnx open https://my-app.local  # load a hosted bundle
+peach open 8081                  # load a metro dev server
+peach open https://my-app.local  # load a hosted bundle
 ```
 
 ## you're done when
 
-- `rnx list` shows your sim and no orphans
-- `rnx describe` returns a render tree, not an error
-- the same sim id appears in `rnx describe`, `rnx find`, and
+- `peach list` shows your sim and no orphans
+- `peach describe` returns a render tree, not an error
+- the same sim id appears in `peach describe`, `peach find`, and
   every subsequent command
-- `rnx get errors 5` and `rnx get requests 5` are quiet (or the
+- `peach get errors 5` and `peach get requests 5` are quiet (or the
   warnings are ones you understand)
 - the compatibility scan's partial, unsupported, unknown, and version-mismatched
   packages have been summarized without treating its aggregate score as a pass/fail gate
 
 ## compatibility feedback requires approval
 
-run `rnx compat --json` from the app project root during setup. if the scan
+run `peach compat --json` from the app project root during setup. if the scan
 identifies a plausible missing Peach seam, or the running app gives concrete
 evidence that behavior is missing or broken specifically in Peach, summarize
 the package, expected behavior, actual behavior, and runtime evidence for the
-user. then offer to send that finding with `rnx report-issue`.
+user. then offer to send that finding with `peach report-issue`.
 
 **never submit a report automatically or behind the user's back.** wait for an
 explicit yes. only then run this from the app project root:
 
 ```sh
-rnx report-issue --yes "<package; expected behavior; actual behavior; runtime evidence>"
+peach report-issue --yes "<package; expected behavior; actual behavior; runtime evidence>"
 ```
 
 the command automatically attaches the local compatibility scan plus bounded
@@ -121,33 +121,33 @@ it records the user's approval after the offer.
 
 ## recovery — common failure modes
 
-**`rnx list` is empty.** walk this checklist in order:
+**`peach list` is empty.** walk this checklist in order:
 
 ```sh
-rnx daemon status            # is the bridge daemon up?
-rnx runtime list             # is at least one engine runtime installed?
-rnx open <port>              # does loading explicitly work?
+peach daemon status            # is the bridge daemon up?
+peach runtime list             # is at least one engine runtime installed?
+peach open <port>              # does loading explicitly work?
 ```
 
-if the daemon is not installed: run `rnx daemon install`. if the registered
-daemon is down, run `rnx daemon restart`, or `rnx serve` in another shell for
-a foreground bridge. if no runtime is installed, `rnx open` installs it
+if the daemon is not installed: run `peach daemon install`. if the registered
+daemon is down, run `peach daemon restart`, or `peach serve` in another shell for
+a foreground bridge. if no runtime is installed, `peach open` installs it
 before launching. if open errors with "port unreachable": confirm your dev
 server is actually serving — the bundler has to be up before Peach can
 attach.
 
-**two sims appear unexpectedly.** an earlier `rnx claim` didn't
+**two sims appear unexpectedly.** an earlier `peach claim` didn't
 release on exit. close the orphan explicitly:
 
 ```sh
-rnx list                     # note the stale id
-rnx close <id>               # release it cleanly
+peach list                     # note the stale id
+peach close <id>               # release it cleanly
 ```
 
-**`rnx open` errors with "no runtime".** the engine binary isn't installed.
-Run `rnx runtime install`, then retry `rnx open <port>`.
+**`peach open` errors with "no runtime".** the engine binary isn't installed.
+Run `peach runtime install`, then retry `peach open <port>`.
 
-**`rnx open` times out ("timed out waiting for opened sim to connect").**
+**`peach open` times out ("timed out waiting for opened sim to connect").**
 do not retry in a loop. verify the development server first: `__soot/` must
 respond and the engine watchers must be running. inspect the driver diagnostic
 path printed by the failed command. restart the broken development stack at its
@@ -155,18 +155,18 @@ supervisor, then retry once. Peach owns the isolated browser profile and its
 process tree; do not open the shell URL through an operating-system browser.
 
 **bridge disconnects mid-sim.** the WebSocket dropped (laptop slept,
-network blip). re-pin: `rnx use <id>`. the daemon retries reconnection
+network blip). re-pin: `peach use <id>`. the daemon retries reconnection
 automatically; you usually just need to re-issue the command.
 
 **"sim held by another CLI".** another agent or your own previous CLI
-process has the lease. find it (`rnx list`), close it (`rnx close
-<id>`), or start a clean sim (`rnx open --new`) — do **not**
-`rnx claim --force`.
+process has the lease. find it (`peach list`), close it (`peach close
+<id>`), or start a clean sim (`peach open --new`) — do **not**
+`peach claim --force`.
 
 ## related
 
-- `/rnx-debug` — once setup is good, this is where you debug
+- `/peach-debug` — once setup is good, this is where you debug
   rendering, performance, and accessibility issues.
-- `/rnx-test` — write or run automated flows against the connected
+- `/peach-test` — write or run automated flows against the connected
   sim.
-- `/rnx-visual` — pixel-level rendering comparisons.
+- `/peach-visual` — pixel-level rendering comparisons.

package/skills/{rnx-test → peach-test}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: rnx-test
+name: peach-test
 description: Run automated tests against your React Native app under Peach with Maestro YAML or Detox/Jest
 ---
 
@@ -9,10 +9,10 @@ Peach has two test runners. Maestro owns every YAML test, whether it was
 hand-authored, generated from a goal, or recorded from live CLI actions.
 Detox runs existing imperative Jest suites through the Peach driver.
 
-> needs a connected, pinned sim. if `rnx describe` errors, load
-> `/rnx-setup` first.
+> needs a connected, pinned sim. if `peach describe` errors, load
+> `/peach-setup` first.
 
-Set `RNX_NO_OPEN=1` before starting an app dev server for a Detox,
+Set `PEACH_NO_OPEN=1` before starting an app dev server for a Detox,
 Maestro, or iOS-only pass. Apps can opt into a named Electron window through
 the official Vite or Metro plugin, and test-only work must not open that window.
 
@@ -37,15 +37,15 @@ Do not invent a third runner for how a Maestro flow was authored.
   implementation and author flows against it.
 - **pin a sim before running a suite.** parallel CI jobs colliding
   on the default bridge port is the #1 flake source. pass `--port` in
-  CI and `rnx use <id>` locally.
+  CI and `peach use <id>` locally.
 - **every flow ends with an assert, not a screenshot.** a screenshot
   passes as long as the flow didn't throw. `assertVisible` (or
   `expect(...).toBeVisible()`) actually verifies the happy path.
 - **don't run a 40-step "smoke everything" flow.** when it fails, you
   can't tell what regressed. split into `login.yaml`, `compose.yaml`,
   `settings.yaml`, chain with `runFlow`.
-- **inside an `rnx do` chain, use `sleep` only for gesture timing.** after the
-  chain, use `rnx wait` for app state so automation advances on a real condition.
+- **inside an `peach do` chain, use `sleep` only for gesture timing.** after the
+  chain, use `peach wait` for app state so automation advances on a real condition.
 
 ## you're done when
 
@@ -62,8 +62,8 @@ batch. use a chain for a short repro, form fill, or timing-sensitive gesture
 that does not belong in a saved test:
 
 ```sh
-rnx do tap email --then type user@example.com --then tap submit
-rnx wait selector dashboard
+peach do tap email --then type user@example.com --then tap submit
+peach wait selector dashboard
 ```
 
 the batch stops on the first failure. add `--json` for per-action results.
@@ -79,23 +79,23 @@ Write declarative Maestro YAML. The same command runs existing suites,
 generates tests, records live drafts, profiles, and uploads replayable results.
 
 ```sh
-rnx maestro test .maestro/login.yaml             # run one flow
-rnx maestro test .maestro/login.yaml --record    # record video
-rnx maestro test .maestro/login.yaml --profile   # include perf stats
-rnx maestro test .maestro/                       # run the suite
+peach maestro test .maestro/login.yaml             # run one flow
+peach maestro test .maestro/login.yaml --record    # record video
+peach maestro test .maestro/login.yaml --profile   # include perf stats
+peach maestro test .maestro/                       # run the suite
 ```
 
 Author from a live interaction:
 
 ```sh
-rnx maestro start                     # begin a draft
-rnx do tap-id loginButton             # drive the app via the CLI
-rnx maestro keep                      # save the step
-rnx do type "user@example.com"
-rnx maestro keep
-rnx do tap-id submit
-rnx maestro keep
-rnx maestro end --output .maestro/login.yaml --validate
+peach maestro start                     # begin a draft
+peach do tap-id loginButton             # drive the app via the CLI
+peach maestro keep                      # save the step
+peach do type "user@example.com"
+peach maestro keep
+peach do tap-id submit
+peach maestro keep
+peach maestro end --output .maestro/login.yaml --validate
 ```
 
 the recorder emits minimal YAML — no coordinate dumps, no `sleep` noise —
@@ -129,7 +129,7 @@ exemplar flow:
 run with env interpolation:
 
 ```sh
-rnx maestro --env USERNAME=alice --env PASSWORD=hunter2 \
+peach maestro --env USERNAME=alice --env PASSWORD=hunter2 \
   test .maestro/login.yaml \
   --record --profile
 ```
@@ -144,7 +144,7 @@ CLI's `wait idle` with a generous budget. use it before any
 Generate and immediately run a Maestro flow from a plain-language goal:
 
 ```sh
-rnx maestro generate "log in with the demo account and verify the dashboard"
+peach maestro generate "log in with the demo account and verify the dashboard"
 ```
 
 Generation writes the same deterministic Maestro artifact, uploads its replay,
@@ -161,19 +161,19 @@ command change:
 maestro test .maestro/login.yaml
 
 # after
-rnx maestro test .maestro/login.yaml
+peach maestro test .maestro/login.yaml
 ```
 
 no test rewrites, no detox config, no simulator. the runtime auto-launches
 a Peach shell if one isn't running.
 
 ```sh
-rnx maestro                           # auto-discover .maestro/ or maestro/
-rnx maestro test .maestro/login.yaml
-rnx maestro test .maestro/            # every flow in a directory
-rnx maestro init                      # scaffold a starter flow
-rnx maestro --list-compat             # supported / partial / unsupported
-rnx maestro --env USERNAME=alice test .maestro/login.yaml
+peach maestro                           # auto-discover .maestro/ or maestro/
+peach maestro test .maestro/login.yaml
+peach maestro test .maestro/            # every flow in a directory
+peach maestro init                      # scaffold a starter flow
+peach maestro --list-compat             # supported / partial / unsupported
+peach maestro --env USERNAME=alice test .maestro/login.yaml
 ```
 
 ### supported verbs
@@ -211,7 +211,7 @@ these throw `unsupported maestro verb: X`:
 ### troubleshooting
 
 - **"no maestro flows found"** — pass an explicit path
-  (`rnx maestro test path/to/flow.yaml`) or run `rnx maestro
+  (`peach maestro test path/to/flow.yaml`) or run `peach maestro
   init` to scaffold one.
 - **"missing environment variable for flow placeholder: FOO"** — pass
   `--env FOO=bar` or export it. pick one mechanism per repo and document
@@ -229,7 +229,7 @@ an existing detox suite runs against Peach with **one line** of jest
 config and zero test changes.
 
 `import { by, device, element, expect, waitFor } from 'detox'` is
-rewritten by jest to an rnx-backed driver that drives the real shell
+rewritten by jest to a peach-backed driver that drives the real shell
 over playwright. matchers, assertions, and the `waitFor` API match the
 upstream detox surface.
 
@@ -238,7 +238,7 @@ upstream detox surface.
 ```js
 // rnx-detox.config.cjs
 module.exports = {
-  preset: 'rnxsim/detox',
+  preset: 'peachsim/detox',
   rootDir: __dirname,
   testMatch: ['<rootDir>/e2e/**/*.test.ts'],
 }
@@ -248,7 +248,7 @@ or, if you already have a jest config, pull in just the module mapper:
 
 ```js
 moduleNameMapper: {
-  '^detox$': require.resolve('rnxsim/detox'),
+  '^detox$': require.resolve('peachsim/detox'),
 }
 ```
 
@@ -259,14 +259,14 @@ works until your first hung shell.
 ### commands
 
 ```sh
-rnx detox                             # run e2e/, test/e2e/, or detox/
-rnx detox --config my.cjs             # use a specific jest config
-rnx detox --watch                     # jest watch mode
-rnx detox -t "login"                  # --testNamePattern
-rnx detox --headed                    # keep the shell window visible
-rnx detox --no-launch                 # don't auto-launch a shell
-rnx detox --port 5173                 # explicit bridge port for CI
-rnx detox init                        # scaffold config + e2e/example.test.ts
+peach detox                             # run e2e/, test/e2e/, or detox/
+peach detox --config my.cjs             # use a specific jest config
+peach detox --watch                     # jest watch mode
+peach detox -t "login"                  # --testNamePattern
+peach detox --headed                    # keep the shell window visible
+peach detox --no-launch                 # don't auto-launch a shell
+peach detox --port 5173                 # explicit bridge port for CI
+peach detox init                        # scaffold config + e2e/example.test.ts
 ```
 
 ### compat surface
@@ -292,12 +292,12 @@ rnx detox init                        # scaffold config + e2e/example.test.ts
 ### troubleshooting
 
 - **"no Peach shell reachable"** — start one yourself
-  (`rnx open <port>`) or pass `--port <n>`.
+  (`peach open <port>`) or pass `--port <n>`.
 - **"jest cannot find module 'detox'"** — the preset isn't wired. confirm
-  `preset: 'rnxsim/detox'` is in the jest config jest
+  `preset: 'peachsim/detox'` is in the jest config jest
   actually loaded (`--config` overrides package.json).
 - **matchers fail on elements that exist** — canvas has no DOM. use
-  `by.id` (testID); `rnx describe` shows what the shell sees.
+  `by.id` (testID); `peach describe` shows what the shell sees.
 - **passes locally, flakes in CI** — the shell boots asynchronously.
   bump jest `testTimeout` to 10–15 s and add a `waitFor(element(...))
   .toBeVisible().withTimeout(10000)` before the first assertion.
@@ -315,7 +315,7 @@ rnx detox init                        # scaffold config + e2e/example.test.ts
   the first assertion, pin the bridge port, and run with `--video` so
   failing Maestro runs land a recording next to the output.
 - **a flake reproduces but resists fixing** — don't paper over with
-  `sleep`. open `/rnx-debug` against the same sim, capture
-  the timeline (`rnx timeline start` → reproduce → `rnx
+  `sleep`. open `/peach-debug` against the same sim, capture
+  the timeline (`peach timeline start` → reproduce → `peach
   what-happened`), and look for the missing animation-completion or
   the unresolved fetch that's racing the assertion.

package/skills/{rnx-visual → peach-visual}/SKILL.md

@@ -1,25 +1,25 @@
 ---
-name: rnx-visual
+name: peach-visual
 description: Pixel-level rendering comparison between Peach and native iOS — fonts, gradients, shadows, image fidelity
 ---
 
 # Peach visual fidelity
 
 pixel-level rendering fidelity: does the Peach canvas match native iOS
-for text, gradients, shadows, blur, and image rendering? the `rnx`
-CLI gives you two primitives — **canvas capture** (`rnx screenshot`)
-and **structural diff** (`rnx debug snapshot`/`diff`). pixel
+for text, gradients, shadows, blur, and image rendering? the `peach`
+CLI gives you two primitives — **canvas capture** (`peach screenshot`)
+and **structural diff** (`peach debug snapshot`/`diff`). pixel
 comparison itself is "capture both sides, diff the PNGs with a standard
 image tool" — there is no single oracle-diff command, and that's fine:
 the capture step is the hard part and it's fully reproducible.
 
-> needs a connected, pinned sim. if `rnx describe` errors,
-> load `/rnx-setup` first.
+> needs a connected, pinned sim. if `peach describe` errors,
+> load `/peach-setup` first.
 
 ## route in
 
 - structural change ("which nodes / which props changed?") → load
-  `/rnx-debug`, debugging branch — `debug snapshot` + `debug
+  `/peach-debug`, debugging branch — `debug snapshot` + `debug
   diff` is faster, deterministic, and tells you *why*.
 - visual change (color, gradient, shadow, font metric, blur, image)? →
   continue here.
@@ -28,36 +28,36 @@ the capture step is the hard part and it's fully reproducible.
 
 ## anti-patterns (read first)
 
-- **run structural diff before pixel work.** `rnx debug snapshot` /
-  `debug diff` (in `/rnx-debug`) is cheaper, deterministic, and
+- **run structural diff before pixel work.** `peach debug snapshot` /
+  `debug diff` (in `/peach-debug`) is cheaper, deterministic, and
   points at the responsible nodes. only when it's empty (or the change is
   pure rendering) does a pixel comparison add information.
 - **don't single-screenshot animated surfaces.** a gradient
-  mid-animation never matches. gate the capture behind `rnx wait
+  mid-animation never matches. gate the capture behind `peach wait
   idle` first.
 - **a > 5% pixel threshold hides regressions.** ~1% is the right
   ballpark for catching real font / shadow / gradient drift without
   flagging anti-alias noise. go higher only with a written reason.
 - **pin device and theme.** capture both sides on the same simulated
   device and appearance. capture each appearance separately with
-  `rnx screenshot` after setting it on both simulators.
+  `peach screenshot` after setting it on both simulators.
 - **commit baselines alongside the code change that produced them.**
   baseline churn without code churn means someone captured noise.
 
-## capturing — `rnx screenshot`
+## capturing — `peach screenshot`
 
 fast, no extra setup, works on any loaded app:
 
 ```sh
-rnx screenshot --output app.png            # full canvas
-rnx screenshot --area 0,200,393,400        # crop to a logical rect
-rnx screenshot --id loginButton -o btn.png # crop to a node by testID
-rnx screenshot --text "Sign in"            # crop to a node by text
-rnx screenshot --no-shell -o tenant.png    # tenant surface only, no iOS chrome
-rnx screenshot --shell-only                # only the simulated iOS chrome
+peach screenshot --output app.png            # full canvas
+peach screenshot --area 0,200,393,400        # crop to a logical rect
+peach screenshot --id loginButton -o btn.png # crop to a node by testID
+peach screenshot --text "Sign in"            # crop to a node by text
+peach screenshot --no-shell -o tenant.png    # tenant surface only, no iOS chrome
+peach screenshot --shell-only                # only the simulated iOS chrome
 ```
 
-`rnx screenshot` captures the current screen as a PNG. navigate to each
+`peach screenshot` captures the current screen as a PNG. navigate to each
 screen you want to inspect and capture it with a distinct output filename.
 
 ## comparing pixels
@@ -67,9 +67,9 @@ capture both sides to PNGs, then diff with any standard image tool.
 **Peach vs Peach (regression across your own commits):**
 
 ```sh
-rnx screenshot -o before.png                      # baseline, before your change
+peach screenshot -o before.png                      # baseline, before your change
 # … make the rendering change, let the sim hot-reload …
-rnx screenshot -o after.png                       # after your change
+peach screenshot -o after.png                       # after your change
 npx pixelmatch before.png after.png diff.png 0.1      # writes diff.png
 # or: magick compare before.png after.png diff.png
 ```
@@ -80,9 +80,9 @@ npx pixelmatch before.png after.png diff.png 0.1      # writes diff.png
 # native side: lifecycle and UI use xcodebuildmcp with one claimed simulator
 # lossless capture names that simulator explicitly; never use the booted alias
 xcrun simctl io <udid> screenshot --type=png native.png
-# rnx side: same screen, same appearance
-rnx screenshot -o rnx.png
-npx pixelmatch native.png rnx.png diff.png 0.1
+# peach side: same screen, same appearance
+peach screenshot -o peach.png
+npx pixelmatch native.png peach.png diff.png 0.1
 ```
 
 `xcodebuildmcp simulator screenshot` may return an optimized JPEG even when the
@@ -97,7 +97,7 @@ under unrelated chrome.
 ## typical workflow
 
 1. structural diff first — confirm the change is genuinely visual.
-2. capture the affected screen with `rnx screenshot` (crop to the
+2. capture the affected screen with `peach screenshot` (crop to the
    element if you can).
 3. diff against the baseline (previous commit, or a native capture).
 4. iterate the rendering until the diff is under threshold.
@@ -114,7 +114,7 @@ under unrelated chrome.
 ## recovery — common failure modes
 
 - **a single icon/glyph diffs** — font-load race or image not yet
-  cached. recapture after `rnx wait idle`, or navigate away and back
+  cached. recapture after `peach wait idle`, or navigate away and back
   to seed the cache.
 - **everything diffs by a constant offset** — you captured the two sides
   on different devices or appearances. pin both, recapture.