rnxsim 0.1.334 → 0.1.336

package/skills/rnx-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 rnx. 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 rnxsim CLI debug tooling first, not screenshots or ad-hoc logging.
+description: Debug rendering, animation, gesture, performance, and accessibility issues in a React Native app running under rnx. 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.
 ---
 
 # rnx debug
@@ -12,13 +12,13 @@ same diff/snapshot workflow. start here for any rendering, interaction,
 event-order, or correctness question. for pixel-level rendering fidelity
 load `/rnx-visual` instead.
 
-> needs a connected, pinned sim. if `rnxsim describe` errors, load
+> needs a connected, pinned sim. if `rnx describe` errors, load
 > `/rnx-setup` first.
 
 ## principle — drive the CLI, don't probe by hand
 
 for any rendering, animation, gesture, or interaction bug, reach for the
-rnxsim CLI debug tooling **first** — `describe` and `find` to read the
+rnx 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
@@ -49,8 +49,8 @@ regression test. a pile of ad-hoc logs helps no one and gets deleted.
 
 ## anti-patterns (apply to every branch)
 
-- **`a1`/`a2`/`b0` style ids mean rnxsim sims, never browser tabs.** when a user
-  says "look at a3", that's the `rnxsim list` sim id. do not open chrome
+- **`a1`/`a2`/`b0` style ids mean rnx sims, never browser tabs.** when a user
+  says "look at a3", that's the `rnx 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 `rnxsim use <id>` at the start of the workflow.
-- **keep one sim and reuse its browser tab.** before `rnxsim open`, run
-  `rnxsim list --all`. pin the target and use `rnxsim do reload`; a plain
-  `rnxsim open <target>` also navigates the saved sim. reserve `--new` for a
+  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
   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
@@ -85,13 +85,13 @@ fetches resolve. the timeline records them so you can ask "what
 happened" instead of racing the UI with `find`.
 
 ```sh
-rnxsim timeline start                       # arm recording (cheap kinds default-on)
+rnx timeline start                       # arm recording (cheap kinds default-on)
 # reproduce the flow
-rnxsim what-happened                        # events since the last CLI call
-rnxsim what-happened --since 10s            # absolute window
-rnxsim what-happened --kinds toast,fetch    # filter to a few kinds
-rnxsim what-happened --summary              # one-line counts
-rnxsim what-happened --flow                 # section events by screen/route
+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
 ```
 
 semantic kinds the timeline understands: `keyboard`, `screen`, `route`,
@@ -99,12 +99,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
-`rnxsim timeline start scroll,gesture,…`.
+`rnx 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 `rnxsim what-happened` to see the detail.
+toast · 1 screen push`, run `rnx 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
@@ -125,11 +125,11 @@ need a manual wait when:
    (no pulsing dots, no shimmer, no looping Lottie).
 
 ```sh
-rnxsim do settle 5                # wait up to 5s for layout stability
-rnxsim wait idle --max-ms 5000    # same thing under the `wait` verb
-rnxsim wait idle --strict         # also require animation flags clear
-rnxsim do tap-id play --no-wait   # skip auto-settle on one command
-SOOTSIM_NO_AUTO_WAIT=1 rnxsim ... # disable auto-settle for a lane
+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
+SOOTSIM_NO_AUTO_WAIT=1 rnx ... # disable auto-settle for a lane
 ```
 
 ## branch — debugging
@@ -137,22 +137,22 @@ SOOTSIM_NO_AUTO_WAIT=1 rnxsim ... # disable auto-settle for a lane
 the playbook for "wrong tree / wrong props / wrong handler":
 
 ```sh
-rnxsim describe                         # what's on screen now
-rnxsim get errors 5                     # any console smoke?
-rnxsim find --testid <node>             # locate the suspect
-rnxsim debug snapshot before
+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
 # reproduce
-rnxsim debug snapshot after
-rnxsim debug diff before after          # structural diff: what changed?
-rnxsim what-happened                    # timeline events during the repro
+rnx debug snapshot after
+rnx debug diff before after          # structural diff: what changed?
+rnx what-happened                    # timeline events during the repro
 ```
 
 for nested scroll ownership or momentum transfer, compare the shell's resolved
 gesture chain with the published scroll registry:
 
 ```sh
-rnxsim debug state scroll-input
-rnxsim debug state scroll-mirror
+rnx debug state scroll-input
+rnx debug state scroll-mirror
 ```
 
 reading `describe` output:
@@ -169,9 +169,9 @@ for transitions, alerts, native UI, or anything spanning the shell ↔
 tenant boundary, lean on the timeline before reaching for traces:
 
 ```sh
-rnxsim timeline start
+rnx timeline start
 # reproduce the launch / dismiss / alert
-rnxsim what-happened --kinds shell,alert,screen,animation
+rnx what-happened --kinds shell,alert,screen,animation
 ```
 
 you're done when:
@@ -184,10 +184,10 @@ you're done when:
 ## branch — performance
 
 ```sh
-rnxsim perf shell start                  # arm capture (also clears prior frames)
+rnx perf shell start                  # arm capture (also clears prior frames)
 # reproduce the slow interaction
-rnxsim perf shell stop                   # full report, including worst frames
-rnxsim perf shell stop --json            # machine-readable summary
+rnx perf shell stop                   # full report, including worst frames
+rnx perf shell stop --json            # machine-readable summary
 ```
 
 `perf shell` output:
@@ -209,8 +209,8 @@ budget. **p95 >20 ms is visible jank for a scrolling surface.**
 profiling a whole flow:
 
 ```sh
-rnxsim maestro test .maestro/scroll-feed.yaml --profile # per-step + frame stats
-rnxsim perf cpu --duration 5 --output /tmp/trace.cpuprofile  # sampled CPU
+rnx maestro test .maestro/scroll-feed.yaml --profile # per-step + frame stats
+rnx perf cpu --duration 5 --output /tmp/trace.cpuprofile  # sampled CPU
 ```
 
 common patterns → first probe:
@@ -227,11 +227,11 @@ debug channels that help, but cost 1–3 ms/frame on their own — enable
 only what you're investigating:
 
 ```sh
-rnxsim debug enable layout,onlayout,render,animated
+rnx debug enable layout,onlayout,render,animated
 # reproduce
-rnxsim debug recent layout 20            # last 20 layout events
-rnxsim debug recent render 20            # last 20 draw passes
-rnxsim debug disable layout,onlayout,render,animated
+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
 ```
 
 you're done when: a p95 number for the interaction + named hot path +
@@ -251,9 +251,9 @@ watch out for:
 ## branch — accessibility
 
 ```sh
-rnxsim get a11y                          # roles, labels, hints, and target geometry
-rnxsim get layout --styling              # boxes, styles, and native pixel contrast
-rnxsim describe --a11y                   # inline a11y info on every node
+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
 ```
 
 native styled layout reads rendered pixels rather than inferring contrast from
@@ -269,9 +269,9 @@ contrast summary format:
 finding offenders fast:
 
 ```sh
-rnxsim find --no-label                   # interactive nodes missing label
-rnxsim find --no-role                    # interactive nodes missing role
-rnxsim find --pressable --max-dim 44     # undersized tap targets
+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
 ```
 
 what gets checked:
@@ -280,7 +280,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 `rnxsim get layout --styling`; it samples final text and
+- **contrast** — run `rnx 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)
@@ -297,11 +297,11 @@ triage order:
 fix → verify loop (the same shape as debugging):
 
 ```sh
-rnxsim get a11y > before-a11y.txt
-rnxsim get layout --styling --json > before-layout.json
+rnx get a11y > before-a11y.txt
+rnx get layout --styling --json > before-layout.json
 # apply the fix
-rnxsim get a11y > after-a11y.txt
-rnxsim get layout --styling --json > after-layout.json
+rnx get a11y > after-a11y.txt
+rnx get layout --styling --json > after-layout.json
 diff before-a11y.txt after-a11y.txt
 diff before-layout.json after-layout.json
 ```
@@ -372,45 +372,45 @@ type names sneak in).
 ### finding and interacting
 
 ```sh
-rnxsim describe                          # all visible elements with styles
-rnxsim describe button                   # filter by text/role/label/testID
-rnxsim describe --testid foo             # only the subtree under a testID
-rnxsim describe --verbose                # include every style property
-
-rnxsim find "Sign in"                    # by text content
-rnxsim find --testid loginButton
-rnxsim find --role button
-rnxsim find --pressable
-rnxsim find --visible                    # only on-screen nodes
-
-rnxsim do tap-id loginButton             # tap by testID (preferred)
-rnxsim do tap-text "Submit"              # tap by text
-rnxsim do tap 196 400                    # tap at coordinates
-rnxsim do type "hello world"             # type into focused input
-rnxsim do type-into emailInput "a@b"     # focus then type
-rnxsim do key return                     # special key (return, backspace, …)
-rnxsim do scroll feed-list 0 500         # scroll a testID by dx/dy
-rnxsim do swipe feed-list left           # directional swipe
-rnxsim do long-press messageRow 800      # ms hold
+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 by dx/dy
+rnx do swipe feed-list left           # directional swipe
+rnx do long-press messageRow 800      # ms hold
 ```
 
 ### errors and requests
 
 ```sh
-rnxsim get errors 5                      # last 5 console errors
-rnxsim get warnings 5
-rnxsim get requests 5                    # recent failed requests
-rnxsim logs --since 30s                  # recent console output
-rnxsim network --since 30s               # recent network traffic
+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
 ```
 
 ### snapshots and diff
 
 ```sh
-rnxsim debug snapshot before
+rnx debug snapshot before
 # interact
-rnxsim debug snapshot after
-rnxsim debug diff before after           # added / removed / changed nodes
+rnx debug snapshot after
+rnx debug diff before after           # added / removed / changed nodes
 ```
 
 ### debug channels
@@ -419,7 +419,7 @@ useful: `animated`, `layout`, `onlayout`, `render`, `sheets`, `portals`,
 `gesture`, `scroll`, `text`, `image`.
 
 ```sh
-rnxsim debug enable animated,layout,sheets,portals
-rnxsim debug recent layout 20            # last 20 events on the channel
-rnxsim debug disable animated,layout,sheets,portals
+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
 ```

package/skills/rnx-perf/SKILL.md

@@ -57,7 +57,7 @@ indict, remeasure — and every wasted week came from skipping a step.
 
 ### presentation proof must stay outside the simulator
 
-Performance acceptance must not use `rnxsim record`, `liveComposite`,
+Performance acceptance must not use `rnx 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
@@ -120,10 +120,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
-rnxsim perf shell start          # arm shell frame capture (clears prior)
+rnx perf shell start          # arm shell frame capture (clears prior)
 # reproduce — e.g. 8 fling swipes:
-#   for i in {1..8}; do rnxsim do swipe 196 650 196 250 8 8 --no-wait; sleep 0.9; done
-rnxsim perf shell stop           # report (add --json for scripting)
+#   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)
 ```
 
 the report and how to read it:
@@ -190,10 +190,10 @@ identify from its own output is not evidence.
 deeper tools when the frame report isn't enough:
 
 ```sh
-rnxsim maestro test .maestro/scroll.yaml --profile # per-step + frame stats
-rnxsim perf cpu --duration 5 --output /tmp/t.cpuprofile   # sampled CPU
-rnxsim open 8089 --new --driver playwright --cdp-port 9222 # cpu-profile a driveable sim
-rnxsim debug enable layout,render && rnxsim debug recent layout 40
+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
 ```
 
 ### the cadence block: frames that never happened

package/skills/rnx-setup/SKILL.md

@@ -1,55 +1,55 @@
 ---
 name: rnx-setup
-description: Get rnx connected to your React Native app — from `rnxsim setup` to a driveable sim
+description: Get rnx connected to your React Native app — from `rnx setup` to a driveable sim
 ---
 
-# rnxsim setup
+# rnx setup
 
 you want to drive a React Native app with rnx from the CLI. this skill
-takes you from `rnxsim setup` to a connected, pinned sim that every other
-rnxsim skill assumes exists. no per-app rnx install is required. if
-`rnxsim describe` already
+takes you from `rnx setup` to a connected, pinned sim that every other
+rnx skill assumes exists. no per-app rnx install is required. if
+`rnx describe` already
 returns a tree, you're past this skill — load `/rnx-debug` for
 debugging or `/rnx-test` for writing tests.
 
 ## anti-patterns (read first)
 
-- **never `rnxsim claim --force` a sim held by another CLI.** the lease
+- **never `rnx 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 `rnxsim open --new` to start a fresh sim instead.
-- **don't switch sims mid-investigation.** pin once with `rnxsim use
+  bridge state. use `rnx open --new` to start a fresh sim instead.
+- **don't switch sims mid-investigation.** pin once with `rnx use
   <id>` and keep it pinned. an unpinned command refuses to choose when more
   than one driveable sim is live.
-- **an empty `rnxsim list` is not "broken rnx".** it usually means the
+- **an empty `rnx list` is not "broken rnx".** 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 `rnxsim open <port>`
+- **keep one sim for your whole session.** the first `rnx open <port>`
   launches Chrome for Testing with an isolated profile. later opens reuse the
-  saved sim and navigate it in place. use `rnxsim do reload` when the target
+  saved sim and navigate it in place. use `rnx do reload` when the target
   has not changed:
 
   ```sh
-  rnxsim open 8086                 # first call creates your isolated sim
-  rnxsim open 8090                 # same sim, different app
-  rnxsim do reload                 # same sim, same app
-  rnxsim close <id>                # dispose it when you are done
+  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
   ```
 
   `--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.** `rnxsim open` records the new sim for the
+- **pin the sim before driving it.** `rnx open` records the new sim for the
   current CLI identity. read its id and pin it explicitly before a longer flow:
 
   ```sh
-  rnxsim open 8086
-  rnxsim list
-  rnxsim use <id>
-  rnxsim describe --sim <id>
+  rnx open 8086
+  rnx list
+  rnx use <id>
+  rnx describe --sim <id>
   ```
 
-- **never retry-loop `rnxsim open` against a wedged or slow stack.** a
+- **never retry-loop `rnx 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 rnx runtime, then
@@ -58,47 +58,47 @@ debugging or `/rnx-test` for writing tests.
 ## first move
 
 ```sh
-rnxsim setup                    # one-time guided setup; installs daemon
-rnxsim compat --json            # scan the app's native package compatibility
-rnxsim open 8081                # load a metro/expo dev server
-rnxsim list                     # confirm exactly one sim is reachable
-rnxsim use <id>                 # pin it for the rest of the workflow
-rnxsim describe                 # smoke test — should print a render tree
+rnx setup                    # one-time guided setup; installs daemon
+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
 ```
 
-if you do not know the port, run `rnxsim open` with no target and pick from
+if you do not know the port, run `rnx open` with no target and pick from
 the detected dev servers. for hosted or unusual targets, pass the URL
 explicitly:
 
 ```sh
-rnxsim open 8081                  # load a metro dev server
-rnxsim open https://my-app.local  # load a hosted bundle
+rnx open 8081                  # load a metro dev server
+rnx open https://my-app.local  # load a hosted bundle
 ```
 
 ## you're done when
 
-- `rnxsim list` shows your sim and no orphans
-- `rnxsim describe` returns a render tree, not an error
-- the same sim id appears in `rnxsim describe`, `rnxsim find`, and
+- `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
   every subsequent command
-- `rnxsim get errors 5` and `rnxsim get requests 5` are quiet (or the
+- `rnx get errors 5` and `rnx 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 `rnxsim compat --json` from the app project root during setup. if the scan
+run `rnx compat --json` from the app project root during setup. if the scan
 identifies a plausible missing rnx seam, or the running app gives concrete
 evidence that behavior is missing or broken specifically in rnx, summarize
 the package, expected behavior, actual behavior, and runtime evidence for the
-user. then offer to send that finding with `rnxsim report-issue`.
+user. then offer to send that finding with `rnx 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
-rnxsim report-issue --yes "<package; expected behavior; actual behavior; runtime evidence>"
+rnx report-issue --yes "<package; expected behavior; actual behavior; runtime evidence>"
 ```
 
 the command automatically attaches the local compatibility scan plus bounded
@@ -110,32 +110,32 @@ it records the user's approval after the offer.
 
 ## recovery — common failure modes
 
-**`rnxsim list` is empty.** walk this checklist in order:
+**`rnx list` is empty.** walk this checklist in order:
 
 ```sh
-rnxsim daemon status            # is the bridge daemon up?
-rnxsim runtime list             # is at least one engine runtime installed?
-rnxsim open <port>              # does loading explicitly work?
+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?
 ```
 
-if daemon is down: run `rnxsim setup`, or `rnxsim serve` in another shell for
-a foreground bridge. if no runtime is installed, `rnxsim open` installs it
+if daemon is down: run `rnx setup`, or `rnx serve` in another shell for
+a foreground bridge. if no runtime is installed, `rnx 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 rnxsim can
+server is actually serving — the bundler has to be up before rnx can
 attach.
 
-**two sims appear unexpectedly.** an earlier `rnxsim claim` didn't
+**two sims appear unexpectedly.** an earlier `rnx claim` didn't
 release on exit. close the orphan explicitly:
 
 ```sh
-rnxsim list                     # note the stale id
-rnxsim close <id>               # release it cleanly
+rnx list                     # note the stale id
+rnx close <id>               # release it cleanly
 ```
 
-**`rnxsim open` errors with "no runtime".** the engine binary isn't installed.
-Run `rnxsim runtime install`, then retry `rnxsim open <port>`.
+**`rnx open` errors with "no runtime".** the engine binary isn't installed.
+Run `rnx runtime install`, then retry `rnx open <port>`.
 
-**`rnxsim open` times out ("timed out waiting for opened sim to connect").**
+**`rnx 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
@@ -143,13 +143,13 @@ supervisor, then retry once. rnx 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: `rnxsim use <id>`. the daemon retries reconnection
+network blip). re-pin: `rnx 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 (`rnxsim list`), close it (`rnxsim close
-<id>`), or start a clean sim (`rnxsim open --new`) — do **not**
-`rnxsim claim --force`.
+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`.
 
 ## related