peachsim 0.1.571 → 0.1.573

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

@@ -1,6 +1,6 @@
 ---
-name: rnx-debug
-description: Debug rendering, animation, gesture, performance, and accessibility issues in a React Native app running under Peach. Reach for this whenever an animation looks wrong (janky, stutters, snaps, only updates once, or doesn't move at all), a swipe/transition/gesture misbehaves or feels broken, scrolling drops frames or feels slow, the UI renders the wrong tree/props, or a screen reader can't reach something — and drive the rnx CLI debug tooling first, not screenshots or ad-hoc logging.
+name: peach-debug
+description: Debug rendering, animation, gesture, performance, and accessibility issues in a React Native app running under Peach. Reach for this whenever an animation looks wrong (janky, stutters, snaps, only updates once, or doesn't move at all), a swipe/transition/gesture misbehaves or feels broken, scrolling drops frames or feels slow, the UI renders the wrong tree/props, or a screen reader can't reach something — and drive the peach CLI debug tooling first, not screenshots or ad-hoc logging.
 ---
 
 # Peach debug
@@ -10,15 +10,15 @@ covers debugging, performance, and accessibility — three branches that
 share the same CLI primitives, the same auto-settling contract, and the
 same diff/snapshot workflow. start here for any rendering, interaction,
 event-order, or correctness question. for pixel-level rendering fidelity
-load `/rnx-visual` instead.
+load `/peach-visual` instead.
 
-> 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.
 
 ## principle — drive the CLI, don't probe by hand
 
 for any rendering, animation, gesture, or interaction bug, reach for the
-rnx CLI debug tooling **first** — `describe` and `find` to read the
+peach CLI debug tooling **first** — `describe` and `find` to read the
 tree, `debug snapshot` + `debug diff` to capture before/after, `debug
 recent` on a channel and `perf shell` for frame-by-frame stats, and the
 timeline for "what just happened". **do not** debug these by eye with
@@ -44,13 +44,13 @@ regression test. a pile of ad-hoc logs helps no one and gets deleted.
 - "screen reader can't find this / wrong label / tap target too small" → [accessibility](#branch--accessibility)
 - "I want to see what just happened" (ephemeral toast, async navigation,
   fetch + alert sequence) → [the timeline](#the-timeline-what-happened)
-- "I want pixel-level fidelity to iOS" → load `/rnx-visual`
-- "I want to author a test" → load `/rnx-test`
+- "I want pixel-level fidelity to iOS" → load `/peach-visual`
+- "I want to author a test" → load `/peach-test`
 
 ## anti-patterns (apply to every branch)
 
 - **`a1`/`a2`/`b0` style ids mean Peach sims, never browser tabs.** when a user
-  says "look at a3", that's the `rnx list` sim id. do not open chrome
+  says "look at a3", that's the `peach list` sim id. do not open chrome
   MCP unless the user explicitly says "use chrome" — the canvas has no
   DOM to inspect anyway.
 - **the CLI auto-settles. don't add `sleep`.** every read waits up to
@@ -62,10 +62,10 @@ regression test. a pile of ad-hoc logs helps no one and gets deleted.
   changes, and duplicate strings. add `testID` during implementation and
   query against it.
 - **pin a sim once.** if more than one is live, an unpinned command
-  refuses to choose. run `rnx use <id>` at the start of the workflow.
-- **keep one sim and reuse its browser tab.** before `rnx open`, run
-  `rnx list --all`. pin the target and use `rnx do reload`; a plain
-  `rnx open <target>` also navigates the saved sim. reserve `--new` for a
+  refuses to choose. run `peach use <id>` at the start of the workflow.
+- **keep one sim and reuse its browser tab.** before `peach open`, run
+  `peach list --all`. pin the target and use `peach do reload`; a plain
+  `peach open <target>` also navigates the saved sim. reserve `--new` for a
   genuinely concurrent sim. repeated browser trees consume memory and CPU on a
   shared machine.
 - **`debug eval` is an escape hatch.** if a top-level command feels
@@ -95,13 +95,13 @@ fetches resolve. the timeline records them so you can ask "what
 happened" instead of racing the UI with `find`.
 
 ```sh
-rnx timeline start                       # arm recording (cheap kinds default-on)
+peach timeline start                       # arm recording (cheap kinds default-on)
 # reproduce the flow
-rnx what-happened                        # events since the last CLI call
-rnx what-happened --since 10s            # absolute window
-rnx what-happened --kinds toast,fetch    # filter to a few kinds
-rnx what-happened --summary              # one-line counts
-rnx what-happened --flow                 # section events by screen/route
+peach what-happened                        # events since the last CLI call
+peach what-happened --since 10s            # absolute window
+peach what-happened --kinds toast,fetch    # filter to a few kinds
+peach what-happened --summary              # one-line counts
+peach what-happened --flow                 # section events by screen/route
 ```
 
 semantic kinds the timeline understands: `keyboard`, `screen`, `route`,
@@ -109,12 +109,12 @@ semantic kinds the timeline understands: `keyboard`, `screen`, `route`,
 `gesture`, `text-input`, `reanimated`, `animation`, `fetch`, `console`,
 `app-launch`, `shell`. cheap kinds record by default; heavier kinds
 (scroll, gesture, text-input, reanimated, animation) opt in via
-`rnx timeline start scroll,gesture,…`.
+`peach timeline start scroll,gesture,…`.
 
 every other CLI command also prints a one-line footer for events since
 the last call — that's the headline indicator. when the footer is empty,
 there's nothing new to look at; when it says `since last: 1 error · 1
-toast · 1 screen push`, run `rnx what-happened` to see the detail.
+toast · 1 screen push`, run `peach what-happened` to see the detail.
 
 > reach for the timeline first when the question involves *something
 > that appeared briefly and disappeared*. it's faster than a screenshot
@@ -135,11 +135,11 @@ need a manual wait when:
    (no pulsing dots, no shimmer, no looping Lottie).
 
 ```sh
-rnx do settle 5                # wait up to 5s for layout stability
-rnx wait idle --max-ms 5000    # same thing under the `wait` verb
-rnx wait idle --strict         # also require animation flags clear
-rnx do tap-id play --no-wait   # skip auto-settle on one command
-RNX_NO_AUTO_WAIT=1 rnx ... # disable auto-settle for a lane
+peach do settle 5                # wait up to 5s for layout stability
+peach wait idle --max-ms 5000    # same thing under the `wait` verb
+peach wait idle --strict         # also require animation flags clear
+peach do tap-id play --no-wait   # skip auto-settle on one command
+PEACH_NO_AUTO_WAIT=1 peach ... # disable auto-settle for a lane
 ```
 
 ## branch — debugging
@@ -147,14 +147,14 @@ RNX_NO_AUTO_WAIT=1 rnx ... # disable auto-settle for a lane
 the playbook for "wrong tree / wrong props / wrong handler":
 
 ```sh
-rnx describe                         # what's on screen now
-rnx get errors 5                     # any console smoke?
-rnx find --testid <node>             # locate the suspect
-rnx debug snapshot before
+peach describe                         # what's on screen now
+peach get errors 5                     # any console smoke?
+peach find --testid <node>             # locate the suspect
+peach debug snapshot before
 # reproduce
-rnx debug snapshot after
-rnx debug diff before after          # structural diff: what changed?
-rnx what-happened                    # timeline events during the repro
+peach debug snapshot after
+peach debug diff before after          # structural diff: what changed?
+peach what-happened                    # timeline events during the repro
 ```
 
 when the repro needs several closely timed inputs, replace the individual
@@ -162,15 +162,15 @@ write calls with one inline batch so WebSocket scheduling cannot change the
 gesture:
 
 ```sh
-rnx do touch down 200 600 --then sleep 0.03 --then touch move 200 250 --then touch up 200 250
+peach do touch down 200 600 --then sleep 0.03 --then touch move 200 250 --then touch up 200 250
 ```
 
 for nested scroll ownership or momentum transfer, compare the shell's resolved
 gesture chain with the published scroll registry:
 
 ```sh
-rnx debug state scroll-input
-rnx debug state scroll-mirror
+peach debug state scroll-input
+peach debug state scroll-mirror
 ```
 
 reading `describe` output:
@@ -187,9 +187,9 @@ for transitions, alerts, native UI, or anything spanning the shell ↔
 tenant boundary, lean on the timeline before reaching for traces:
 
 ```sh
-rnx timeline start
+peach timeline start
 # reproduce the launch / dismiss / alert
-rnx what-happened --kinds shell,alert,screen,animation
+peach what-happened --kinds shell,alert,screen,animation
 ```
 
 you're done when:
@@ -202,10 +202,10 @@ you're done when:
 ## branch — performance
 
 ```sh
-rnx perf shell start                  # arm capture (also clears prior frames)
+peach perf shell start                  # arm capture (also clears prior frames)
 # reproduce the slow interaction
-rnx perf shell stop                   # full report, including worst frames
-rnx perf shell stop --json            # machine-readable summary
+peach perf shell stop                   # full report, including worst frames
+peach perf shell stop --json            # machine-readable summary
 ```
 
 `perf shell` output:
@@ -227,8 +227,8 @@ budget. **p95 >20 ms is visible jank for a scrolling surface.**
 profiling a whole flow:
 
 ```sh
-rnx maestro test .maestro/scroll-feed.yaml --profile # per-step + frame stats
-rnx perf cpu --duration 5 --output /tmp/trace.cpuprofile  # sampled CPU
+peach maestro test .maestro/scroll-feed.yaml --profile # per-step + frame stats
+peach perf cpu --duration 5 --output /tmp/trace.cpuprofile  # sampled CPU
 ```
 
 common patterns → first probe:
@@ -245,11 +245,11 @@ debug channels that help, but cost 1–3 ms/frame on their own — enable
 only what you're investigating:
 
 ```sh
-rnx debug enable layout,onlayout,render,animated
+peach debug enable layout,onlayout,render,animated
 # reproduce
-rnx debug recent layout 20            # last 20 layout events
-rnx debug recent render 20            # last 20 draw passes
-rnx debug disable layout,onlayout,render,animated
+peach debug recent layout 20            # last 20 layout events
+peach debug recent render 20            # last 20 draw passes
+peach debug disable layout,onlayout,render,animated
 ```
 
 you're done when: a p95 number for the interaction + named hot path +
@@ -269,9 +269,9 @@ watch out for:
 ## branch — accessibility
 
 ```sh
-rnx get a11y                          # roles, labels, hints, and target geometry
-rnx get layout --styling              # boxes, styles, and native pixel contrast
-rnx describe --a11y                   # inline a11y info on every node
+peach get a11y                          # roles, labels, hints, and target geometry
+peach get layout --styling              # boxes, styles, and native pixel contrast
+peach describe --a11y                   # inline a11y info on every node
 ```
 
 native styled layout reads rendered pixels rather than inferring contrast from
@@ -287,9 +287,9 @@ contrast summary format:
 finding offenders fast:
 
 ```sh
-rnx find --no-label                   # interactive nodes missing label
-rnx find --no-role                    # interactive nodes missing role
-rnx find --pressable --max-dim 44     # undersized tap targets
+peach find --no-label                   # interactive nodes missing label
+peach find --no-role                    # interactive nodes missing role
+peach find --pressable --max-dim 44     # undersized tap targets
 ```
 
 what gets checked:
@@ -298,7 +298,7 @@ what gets checked:
 - **missing roles** — `Pressable`/`Touchable` without `accessibilityRole`
 - **missing hints** — complex interactions without `accessibilityHint`
 - **touch target size** — tappable nodes with hitSlop-expanded rect <44×44
-- **contrast** — run `rnx get layout --styling`; it samples final text and
+- **contrast** — run `peach get layout --styling`; it samples final text and
   text-suppressed background pixels, including gradients and composited opacity
 - **label / visible-text mismatch** — label that reads differently from
   the text VoiceOver would fall back to (often a translation bug)
@@ -315,11 +315,11 @@ triage order:
 fix → verify loop (the same shape as debugging):
 
 ```sh
-rnx get a11y > before-a11y.txt
-rnx get layout --styling --json > before-layout.json
+peach get a11y > before-a11y.txt
+peach get layout --styling --json > before-layout.json
 # apply the fix
-rnx get a11y > after-a11y.txt
-rnx get layout --styling --json > after-layout.json
+peach get a11y > after-a11y.txt
+peach get layout --styling --json > after-layout.json
 diff before-a11y.txt after-a11y.txt
 diff before-layout.json after-layout.json
 ```
@@ -371,7 +371,7 @@ type names sneak in).
 ## recovery — common failure modes
 
 - **`describe` returns nothing** — no sim pinned, or the app isn't
-  loaded. load `/rnx-setup` and re-confirm.
+  loaded. load `/peach-setup` and re-confirm.
 - **`find` returns multiple matches** — narrow with `--testid`,
   `--visible`, or both.
 - **`perf shell` reports zero frames** — you didn't run `perf shell start`
@@ -390,45 +390,45 @@ type names sneak in).
 ### finding and interacting
 
 ```sh
-rnx describe                          # all visible elements with styles
-rnx describe button                   # filter by text/role/label/testID
-rnx describe --testid foo             # only the subtree under a testID
-rnx describe --verbose                # include every style property
-
-rnx find "Sign in"                    # by text content
-rnx find --testid loginButton
-rnx find --role button
-rnx find --pressable
-rnx find --visible                    # only on-screen nodes
-
-rnx do tap-id loginButton             # tap by testID (preferred)
-rnx do tap-text "Submit"              # tap by text
-rnx do tap 196 400                    # tap at coordinates
-rnx do type "hello world"             # type into focused input
-rnx do type-into emailInput "a@b"     # focus then type
-rnx do key return                     # special key (return, backspace, …)
-rnx do scroll feed-list 0 500         # scroll a testID to absolute x/y offsets
-rnx do swipe feed-list left           # directional swipe
-rnx do long-press messageRow 800      # ms hold
+peach describe                          # all visible elements with styles
+peach describe button                   # filter by text/role/label/testID
+peach describe --testid foo             # only the subtree under a testID
+peach describe --verbose                # include every style property
+
+peach find "Sign in"                    # by text content
+peach find --testid loginButton
+peach find --role button
+peach find --pressable
+peach find --visible                    # only on-screen nodes
+
+peach do tap-id loginButton             # tap by testID (preferred)
+peach do tap-text "Submit"              # tap by text
+peach do tap 196 400                    # tap at coordinates
+peach do type "hello world"             # type into focused input
+peach do type-into emailInput "a@b"     # focus then type
+peach do key return                     # special key (return, backspace, …)
+peach do scroll feed-list 0 500         # scroll a testID to absolute x/y offsets
+peach do swipe feed-list left           # directional swipe
+peach do long-press messageRow 800      # ms hold
 ```
 
 ### errors and requests
 
 ```sh
-rnx get errors 5                      # last 5 console errors
-rnx get warnings 5
-rnx get requests 5                    # recent failed requests
-rnx logs --since 30s                  # recent console output
-rnx network --since 30s               # recent network traffic
+peach get errors 5                      # last 5 console errors
+peach get warnings 5
+peach get requests 5                    # recent failed requests
+peach logs --since 30s                  # recent console output
+peach network --since 30s               # recent network traffic
 ```
 
 ### snapshots and diff
 
 ```sh
-rnx debug snapshot before
+peach debug snapshot before
 # interact
-rnx debug snapshot after
-rnx debug diff before after           # added / removed / changed nodes
+peach debug snapshot after
+peach debug diff before after           # added / removed / changed nodes
 ```
 
 ### debug channels
@@ -437,7 +437,7 @@ useful: `animated`, `layout`, `onlayout`, `render`, `sheets`, `portals`,
 `gesture`, `scroll`, `text`, `image`.
 
 ```sh
-rnx debug enable animated,layout,sheets,portals
-rnx debug recent layout 20            # last 20 events on the channel
-rnx debug disable animated,layout,sheets,portals
+peach debug enable animated,layout,sheets,portals
+peach debug recent layout 20            # last 20 events on the channel
+peach debug disable animated,layout,sheets,portals
 ```

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.