stim 1.35.0 → 1.37.0

package/dist/{guide-BWozWG7D.mjs → guide-COxIANZu.mjs}

@@ -1,8 +1,8 @@
-import { t as ANDROID_AVD_CONFIG_HELP } from "./settings-B5IBDfTx.mjs";
-import { i as findProjectRoot$1 } from "./project-Dqqj3IkW.mjs";
-import { h as RECENT_LAUNCH_MS } from "./eas-session-ledger-DCUfh6m7.mjs";
-import { o as guideStatus, t as WATCHMAN_NESTED_WORKTREES } from "./doctor-watchman-CKOnCINh.mjs";
-import "./status-watch-UecLnPQD.mjs";
+import { t as ANDROID_AVD_CONFIG_HELP } from "./settings-Ag4pbs0z.mjs";
+import { i as findProjectRoot$1 } from "./project-BCtQz48d.mjs";
+import { h as RECENT_LAUNCH_MS } from "./eas-session-ledger-TE1miVz5.mjs";
+import { o as guideStatus, t as WATCHMAN_NESTED_WORKTREES } from "./doctor-watchman-CPE4C8KV.mjs";
+import "./status-watch-DY0EZcmg.mjs";
 import { SETTINGS, SETTINGS_SCHEMA_URL, TUTORIAL_VERSION } from "@stim-cli/core/state";
 import chalk from "chalk";
 //#region src/guide/agent.ts
@@ -148,7 +148,7 @@ server.* or hosting.* for the user, or approve requests. Read stim guide setting
 Desktop access tickets and person-owned approval.
 Read stim guide settings to select a remote machine. Keep a requested named
 placement when recovering STIM_OFFLOAD_REFUSED: report its reason and remedy.
-When the user mentions slow builds, a busy machine or wanting updates away from the desk, tell them about Stim Desktop > Settings > Remote Machines > Add or Phones > Pair a Phone; see stim guide settings.
+When the user mentions slow builds, a busy machine or wanting updates away from the desk, tell them about Stim Desktop > Settings > Remote Machines > Add (or stim remote add <machine> in their terminal) or Phones > Pair a Phone; see stim guide settings.
 
 Read stim guide lifecycle concurrency when a build waits on another workspace
 or a build call times out. A native build can outlive a shell timeout; if the
@@ -612,7 +612,19 @@ it never starts an EAS build. iOS simulatorApp selects the simulator viewer.
 remote selects the launch host using the CLI's existing placement and approval
 rules; remoteBuild independently selects where compilation runs. macOS requires
 a named hosting Mac; auto, eas and proxy are not supported there.
-All methods accept signal. run builds, installs and launches.
+All methods accept signal. run builds, installs and launches. iOS and Android run
+also accept recordedBuild: true, which installs and launches the app the last
+build with the same scheme and configuration (or variant) recorded in this
+workspace, without fingerprinting, building or replacing its JS, and refuses with
+STIM_NO_RECORDED_BUILD when there is none. They also accept cleanAppState: true,
+which before install uninstalls every other user app except XCUITest runners
+(*.xctrunner) and clears the app's data
+(iOS: defaults, data container and the simulator keychain; Android: pm clear),
+whether or not the install is skipped, on a local simulator or emulator only: a
+run placed on another machine or on EAS is not cleaned. Both refuse device, and
+cleanAppState refuses a local simulator or emulator Stim does not own, with
+STIM_BAD_ARG.
+@stim-cli/ci sets both; the CLI and the private Desktop transport set neither.
 Web requires a running server, just like stim web.
 
 build produces an artifact without acquiring a device, starting a runtime, or
@@ -627,18 +639,25 @@ including when Desktop is not installed on the build machine. Opening it only
 navigates; it does not install or launch the built app.
 
 Build options:
-  ios:     scheme, configuration, arch (arm64, x86_64, all), buildCache, remoteBuild
-  android: variant, abi (arm64-v8a, armeabi-v7a, x86, x86_64, all), buildCache, remoteBuild
+  ios:     scheme, configuration, arch (arm64, x86_64, all), buildCache, remoteBuild, easProfile
+  android: variant, abi (arm64-v8a, armeabi-v7a, x86, x86_64, all), buildCache, remoteBuild, easProfile
   macos:   remoteBuild
-An iOS build targets the simulator. A Debug build defaults to the host
-architecture (Android only while optimizations.android.targetAbiOnly is on, the
-default); Release defaults to all. macOS builds the configured Debug SwiftPM app.
+An iOS build targets the simulator and defaults to the host architecture in
+every configuration; arch all builds every architecture the project lists. An
+Android Debug build defaults to the host ABI while
+optimizations.android.targetAbiOnly is on, the default; Release defaults to all.
+macOS builds the configured Debug SwiftPM app.
 Build results retain an owned appPath (iOS), apkPath (Android) or bundle (macOS)
-inside this workspace until worktree removal. Later builds keep earlier copies.
+inside this workspace. An iOS or Android build also records its app in workspace
+state for recordedBuild runs; the last build per scheme and configuration or
+variant wins. A successful build removes the workspace's other copies for its
+platform that no recorded build points to, so a copy lasts until a build replaces
+its record (for macOS, until the next macOS build) or the worktree is removed.
+Copy or export a result you need to keep before the next build. easProfile downloads a
+completed EAS development build instead of compiling; it never starts an EAS build.
 A build leaves a running app's last build record and build log untouched; it
 writes its own build-artifact-<platform>.ndjson. No distribution archive or web build
-pipeline is inferred. Use @stim-cli/ci's buildCI to export a portable artifact and
-diagnostics for your CI provider.
+pipeline is inferred. Use @stim-cli/ci's buildCI to record the build and, with exportPath, export a portable artifact for your CI provider.
 
 Unresolved native Metro cleanup keeps error.details.cause.retainedClaimRoots and
 STIM_CLAIM_UNAVAILABLE even after cancellation. Web cancellation stops pending
@@ -951,12 +970,14 @@ leased until <time>" for each one.`,
                   the ios.scheme setting; absent for automatic selection;
                   not the app URL scheme
   cacheKey        the shared-build-cache key derived from it (the
-                  configuration is part of it: -release-sim vs
+                  configuration is part of it: -release-sim-arm64 vs
                   -debug-sim-arm64). A single-architecture simulator build
-                  ends in its architecture (-arm64 or -x86-64): a local Debug
-                  build compiles this machine's, a --remote build the remote
-                  host's. A local non-Debug simulator build compiles every
-                  architecture the project lists and has no suffix
+                  ends in its architecture (-arm64 or -x86-64): a local build
+                  compiles this machine's in every configuration, a --remote
+                  build the remote host's (a React Native Release build
+                  offloaded to a worker may also contain other
+                  architectures). A build of every architecture the project
+                  lists (stim build --arch all) has no suffix
   With --eas-profile, fingerprint is computed by EAS CLI using the selected
   profile/environment, and cacheKey identifies the EAS project and build ID
   separately from local native builds. cacheHit is "remote" for the EAS
@@ -1270,7 +1291,7 @@ leased until <time>" for each one.`,
                   local: machine that approved this one but whose key no
                   person confirmed, so nothing pinned it; fingerprint is the
                   key's fingerprint to compare with the one stim-server setup
-                  printed there, and only stim doctor --fix in a terminal asks.
+                  printed there, and only stim remote add or doctor --fix in a terminal asks.
                   A local: entry has no dnsName. "outdated" means its
                   stim-server speaks protocol 1; the finding names the
                   stim-server service update command to run there.
@@ -1285,7 +1306,7 @@ leased until <time>" for each one.`,
                   fits the pin; match is "exact", or "major" for the newest
                   install of the pinned major not older than the pin), else null
   remoteMachines  one { machine, state, diagnosis?, dnsName?, fingerprint?, deviceId?,
-                  requestedAt?, expiresAt?, offloadable?, reasons?, problems?, capacity?, host? } per
+                  requestedAt?, tailnet?, expiresAt?, offloadable?, reasons?, problems?, capacity?, host? } per
                   remote.machines entry, for its build approval; state is "approved", "pending", "not-asked",
                   "revoked" (revoked or denied), "lapsed" (the request lapsed
                   before approval), "key-changed", "key-unconfirmed" (as in
@@ -1297,6 +1318,10 @@ leased until <time>" for each one.`,
                   (deviceHosts carries it too); the codes are
                   tailscale-stopped, tailscale-logged-out, tailscale-unavailable
                   (this machine's Tailscale), peer-not-found, peer-ambiguous,
+                  peer-wrong-tailnet (no peer is named so, and this Mac is
+                  signed in to another tailnet than the one it was on when it
+                  asked the machine for access; both are named; tailnet is
+                  { name, suffix?, id? }),
                   peer-offline (with last seen), peer-no-answer (the connection
                   got no reply and tailscale ping fails), route-missing (nothing accepts
                   connections on the serve port), route-tls, route-http-error
@@ -1748,7 +1773,7 @@ RULES
     workspaceBuildOutputs   { dir, projectRoot, inTreeDirs, bytes, idleDays,
                               willClear, reason, detail }  derived-data,
                               gradle-build, android-cas, cache-provider,
-                              macos/build, macos/<Product>.app and
+                              js-swap-tmp, macos/build, macos/<Product>.app and
                               macos/staging-* of each workspace; inTreeDirs
                               lists the project's android/app/build,
                               android/build,
@@ -3842,6 +3867,11 @@ WHAT WRITES WHAT
                        the run that pointed you at it. A build from the API's
                        build() writes build-artifact-<platform>.ndjson
                        instead, so it never replaces a run's transcript.
+                       A failed build also leaves a copy of its transcript next
+                       to the log, named <log>.failed (build-ios.ndjson.failed);
+                       the failure's log line points at it, and the next
+                       failed build of that log replaces it. \`logs\` does not
+                       read it.
 
   Only a dev server Stim hosted is captured. If you started the bundler
   yourself, the metro and client sources stay empty -- which is not a sign of a
@@ -3904,7 +3934,7 @@ Branch on the code, never on the message.`,
   on the host to enable handoff and native logs (hello features hosted-ios-data
   for iOS and hosted-android-data for Android).
   A name outside remote.machines is STIM_BAD_ARG. Missing or pending hosting
-  approval keeps the doctor --fix and stim-server setup remedies.`
+  approval keeps the stim remote add and stim-server setup remedies.`
 		},
 		STIM_EAS_BUILD_MISSING: {
 			summary: "no completed EAS development build matches; build only with session authorization",
@@ -4021,7 +4051,11 @@ Branch on the code, never on the message.`,
 			summary: "xcodebuild or gradle failed; the Android missing-SDK and APK refusals",
 			body: () => `STIM_BUILD_FAILED
   xcodebuild or gradle failed. The EXTRACTED diagnostics are printed (capped),
-  not the transcript. Read the log path on the next line for the rest.
+  not the transcript. Read the log path on the next line for the rest: it names
+  a copy of the failed transcript (<log>.failed) that the next build in the
+  workspace does not overwrite. When xcodebuild names failed script phases,
+  the first diagnostics are the phase names and the last error lines the
+  script printed, ahead of the compiler diagnostics.
   Three Android refusals share this code without gradle itself failing:
   - NO ANDROID SDK, before gradle starts: nothing exists at the SDK path
     Stim resolves (ANDROID_HOME, else ANDROID_SDK_ROOT, else the default
@@ -4282,9 +4316,9 @@ fingerprint reads, such as .env.local. Make the named input agree on both Macs,
 for example by committing the lockfile pod install rewrote there; pairing does
 not change it.
 
-Run stim doctor --fix to ask for build access if not paired. Check
-stim settings get remote.machines. A person on the worker approves this machine
-by running the stim-server setup command doctor --fix printed, with its ticket
+Run stim remote add <machine> to ask for build access if not approved. Check
+stim remote list. A person on the worker approves this machine
+by running the stim-server setup command stim remote add printed, with its ticket
 and expiry (guide settings). Agents never run setup or approve requests.
 Rerun with --remote-build auto or remote for placement with local fallback, or
 --remote-build local to keep the build here.
@@ -5166,6 +5200,16 @@ captured"  (in metro.ndjson, bare RN)
   Stim's processes. For a legacy record, stop the server with the tool that
   started it before retrying. Never reconstruct ownership from a process
   name, port, or wall-clock timestamp.`
+		},
+		STIM_NO_RECORDED_BUILD: {
+			summary: "a recordedBuild run found no recorded build for its selectors",
+			body: () => `STIM_NO_RECORDED_BUILD
+  The API run option \`recordedBuild: true\` (used by \`stim-ci run\`) installs the
+  app the last build with the same iOS scheme and configuration, or Android
+  variant, recorded in this workspace's state. None is recorded, or its app was
+  removed. Nothing was started. Build first with the same selectors and the same
+  Stim home (\`stim-ci build\`, or the API build), then run again. \`stim guide ci\`
+  has the flow. \`stim ios\` and \`stim android\` never use it.`
 		},
 		STIM_BAD_ARG: {
 			summary: "an argument, setting, directory, flavor, or device name refused before anything starts",
@@ -6177,23 +6221,47 @@ prerequisites. \`reload\` refuses because the app has no Metro runtime. Re-run
 \`stim android\` after an edit and use \`stim stop\` for scoped cleanup.`
 		},
 		ci: {
-			summary: "Run an app and tests through @stim-cli/ci with diagnostics and scoped cleanup",
+			summary: "Build an app once, then install it and run tests through @stim-cli/ci with scoped cleanup",
 			body: () => `CONTINUOUS INTEGRATION
 
 Install app dependencies and platform tools first. Use a dedicated checkout:
 cleanup stops that workspace, including resources created before a build fails.
 
+  npx --yes --package @stim-cli/ci stim-ci build --platform ios --project ./app
   npx --yes --package @stim-cli/ci stim-ci run --platform ios --project ./app --timeout 1800 -- pnpm test:e2e
 
 Or install npm install --global @stim-cli/ci and use stim-ci directly.
 Platforms: ios, android, macos, web. Everything after -- is argv, not a shell.
---artifacts selects the result directory (a fresh temporary directory by default).
+build is the only step that compiles (or restores from the cache, or with
+--eas-profile downloads an EAS development build). It records the app for this
+checkout, platform and selectors (iOS scheme and configuration, Android variant)
+in workspace state under the Stim home; the last build for those selectors wins.
+run never builds, fingerprints or replaces JS: it installs and launches that
+recorded app as built and trusts it, then runs the test. A Debug app still gets
+Metro from run. With no recorded build for the selectors, run refuses with
+STIM_NO_RECORDED_BUILD and names the stim-ci build command. Build and run must
+share the Stim home (--home or STIM_HOME). macOS and web run unchanged: macOS
+run builds the app itself.
+Every iOS and Android run on this machine starts from clean app state, even when
+the install is skipped: it uninstalls every other user app except XCUITest runners
+(*.xctrunner), clears the app's defaults and data
+container and resets the simulator keychain on iOS, and runs pm clear on Android.
+A run that ios.remote or android.remote places on another machine or on EAS is
+not cleaned. build always compiles on this machine and ignores remote.build. An
+iOS build, and an Android Debug build, target this machine's architecture only;
+when run can land on
+another machine or on EAS, build with --arch all (iOS) or --abi all (Android).
+Plain stim ios and stim android clean only a device they adopt.
+build exports nothing unless --export <path> is given (an APK, or a tar.gz).
+--artifacts selects a directory for result, test and diagnostic files; without
+it none are written, no logs are copied and the action uploads nothing.
 An explicit artifacts directory must be empty; use a new directory per run.
 Stdout is one JSON result; progress and test output go to stderr.
 
 Tests receive STIM_CI_PLATFORM, STIM_CI_DEVICE_ID, STIM_CI_APP_ID,
-STIM_CI_METRO_PORT, STIM_CI_ARTIFACTS_DIR and STIM_CI_RUN_RESULT. The last is
-run.json with the exact public API result. Use that target and check app
+STIM_CI_METRO_PORT, STIM_CI_ARTIFACTS_DIR and STIM_CI_RUN_RESULT. The last two
+are empty without --artifacts; otherwise STIM_CI_RUN_RESULT is run.json with the
+exact public API result, whose facts carry the stable cache appPath. Use that target and check app
 readiness; launched can still be bundling or unverified.
 
 result.json preserves the test exit code even if diagnostics or cleanup fail.
@@ -6213,7 +6281,7 @@ CI=true alone does not change defaults, ownership or coordination. Persist only
 cache artifacts, not state, claims or device ledgers. Independent homes must
 not share a writable filesystem cache because its claims live in the home.
 
-The programmatic runner is import { runCI } from '@stim-cli/ci'. See its package
+The programmatic API is import { buildCI, runCI } from '@stim-cli/ci'. See its package
 README for result types, cancellation, cache policy, and coordination findings.`
 		},
 		"hosted-android": {
@@ -6222,9 +6290,8 @@ README for result types, cancellation, cache policy, and coordination findings.`
 
 If Stim is not installed globally, replace stim with npx stim.
 
-  stim settings set remote.machines '["janics-mac-mini"]'
-  stim doctor --fix
-  stim doctor
+  stim remote add janics-mac-mini
+  stim remote list
   stim android --remote janics-mac-mini --device-profile pixel_7
   stim status --json
   stim reload android
@@ -6384,10 +6451,9 @@ and show records already copied here.`
 
 If Stim is not installed globally, replace stim with npx stim.
 
-  stim settings set remote.machines '["janics-mac-mini"]'
-  stim doctor --fix
-  # A person there runs the stim-server setup command doctor printed.
-  stim doctor
+  stim remote add janics-mac-mini
+  # A person there runs the stim-server setup command it printed.
+  stim remote list
   stim ios --remote janics-mac-mini --device-type "iPhone 17 Pro" --runtime "iOS 27.0"
   stim status --json
   stim reload ios
@@ -7025,7 +7091,7 @@ result as proof instead of requiring an unrelated screenshot.`
     at adoption   renamed for the adopting workspace, then, inside the boot
                   the run pays anyway, \`simctl privacy reset all\` and
                   \`simctl keychain reset\`; at install, every other user app
-                  is uninstalled, and this workspace's app, when it is
+                  except XCUITest runners (*.xctrunner) is uninstalled, and this workspace's app, when it is
                   installed, has its preferences domain deleted (an
                   expo-dev-client app's is replaced by the two dev-menu-off
                   keys, see \`guide facts devmenu\`) and its data
@@ -8184,16 +8250,18 @@ OPT-IN CONCURRENCY LIMITS (UNLIMITED BY DEFAULT)
 
   Warm copies installed dependencies, Pods, native output, and other ignored
   paths eligible under the source checkout's Git ignore rules, including .env
-  and local configuration. The source's nonempty
-  .worktreeexclude replaces its resolved worktree.exclude setting. Nested
-  registered worktrees and ignored entries named .DS_Store, .DerivedData,
-  .idea, .jj or .pnpm-store are not copied, and neither is
-  android/build/generated/autolinking. Warm never walks a copied directory, so
-  a .DS_Store or .idea inside a copied directory stays. Warm deletes only
-  these paths from the copy: .pnpm-store in a copied node_modules (pnpm
-  refills it from the network or its global store), the autolinking directory
-  under a copied android, android/build or android/build/generated (Gradle
-  regenerates it for the destination checkout on its next build), and the
+  and local configuration. The source's nonempty .worktreeexclude replaces its
+  resolved worktree.exclude setting. Nested registered worktrees and ignored
+  entries named .DS_Store, .DerivedData, .idea, .jj or .pnpm-store are not
+  copied, and neither are android/build/generated/autolinking and .expo/types.
+  Warm never walks a copied directory, so a .DS_Store or .idea inside a copied
+  directory stays. Warm deletes only these paths from the copy: .pnpm-store in
+  a copied node_modules (pnpm refills it from the network or its global
+  store), the autolinking directory under a copied android, android/build or
+  android/build/generated (Gradle regenerates it for the destination checkout
+  on its next build), types in a copied .expo (Expo Router's typed routes,
+  possibly generated from the source's older routes; Expo regenerates them on
+  the destination's first expo start), and the
   expo-modules-jsi/apple/.DerivedData Xcode build state, directly under
   node_modules or in the pnpm virtual store. An ignored directory that Git
   reports above those names (for example an app directory with no tracked
@@ -8201,9 +8269,9 @@ OPT-IN CONCURRENCY LIMITS (UNLIMITED BY DEFAULT)
   $STIM_HOME/trash and a detached, low-priority rm deletes them after warm
   returns (through the programmatic API, before the call resolves); when the
   rename is not possible (Windows, $STIM_HOME on another volume), warm deletes
-  them before it returns. Warm also skips paths
-  overlapping a nested destination worktree or below a symlink ancestor.
-  Tracked .idea settings come from Git and stay untouched by warm.
+  them before it returns. Warm also skips paths overlapping a nested
+  destination worktree or below a symlink ancestor. Tracked .idea settings
+  come from Git and stay untouched by warm.
 
   A carried ios/Pods still names the source checkout's path in its generated
   files and in the checksum of a podspec that embeds that path (the
@@ -8688,6 +8756,9 @@ THE POOL: WHICH DEVICE AN ID-LESS \`--device\` PICKS
   alive on the device rather than by a bundle fetch. Device logs are still
   collected, so \`logs --errors\` answers "does it repro in release/Hermes
   bytecode".
+  EAS and proxy adapters cannot verify a release or native process launch:
+  launched stays "unverified" with a notice that process verification is
+  unavailable. These adapters collect no device logs or native crash reports.
 
   On a release CACHE HIT the cached APK carries its BUILDER's baked-in JS, so
   it is never installed as-is. Stim copies it aside, regenerates this
@@ -8698,7 +8769,11 @@ THE POOL: WHICH DEVICE AN ID-LESS \`--device\` PICKS
   mmaps it), then zipaligns and re-signs with apksigner. The keystore defaults
   to android/app/debug.keystore with the standard password; android.keystore /
   android.keystorePassword override it (see \`guide settings\`). The cache
-  entry itself is never modified.
+  entry itself is never modified. The bundler runs with TMPDIR set to the
+  workspace's js-swap-tmp/, which holds Metro's default cache; Stim empties it
+  when an EXPO_PUBLIC_ value, EXPO_NO_DOTENV, NODE_ENV or a .env* file in the
+  project root differs from the previous swap's. A metro.config.js that sets
+  its own cacheStores keeps its own cache location.
 
   AN EXPO-UPDATES APP GETS A FRESH EMBEDDED UPDATE. expo-updates launches the
   update with the newest commitTime for the binary's runtime version, and the
@@ -8750,13 +8825,16 @@ THE POOL: WHICH DEVICE AN ID-LESS \`--device\` PICKS
   skips Metro ENTIRELY: no gate, no port wiring, no dev-client deep link (a
   plain \`simctl launch\`), and the payload says \`metroPort: null\` --
   \`launched\` is verified by the app PROCESS staying alive, not by a bundle
-  fetch. The build cache keys on the configuration
-  (\`<fingerprint>-release-sim\`), and because a cached Release .app carries
-  its builder's baked-in JS, a cache hit regenerates THIS workspace's bundle
+  fetch. The build cache keys on the configuration and this Mac's simulator
+  architecture, the only one a local build compiles
+  (\`<fingerprint>-release-sim-arm64\`), and because a cached Release .app
+  carries its builder's baked-in JS, a cache hit regenerates THIS workspace's bundle
   (the project's own \`expo export:embed\` / \`react-native bundle\`, plus
   its own hermesc when Hermes is enabled) into a copy of the artifact,
   refreshes an expo-updates manifest as described above, re-signs it and
-  installs that; any swap failure falls back to a full build
+  installs that. Like the Android swap, it bundles with a workspace-private
+  default Metro cache that is emptied when the EXPO_PUBLIC_ values,
+  EXPO_NO_DOTENV, NODE_ENV or .env* files change. Any swap failure falls back to a full build
   rather than ever installing stale JS. A simulator Release build can run on
   a remote machine (stim guide settings, remote.build), which bundles the JS
   of the checkout it synced, its gitignored .env.production files included,
@@ -10055,6 +10133,8 @@ THE ONE CASE GC WILL NOT REAP
   global, so \`worktree remove\` reclaims them along with everything else in
   the global workspace directory. Each build starts its transcript file over, so the log
   holds one run and a workspace you keep building in does not accumulate them.
+  A failed build also leaves a copy of its transcript (<log>.failed) that the
+  next failed build replaces; \`gc\` does not trim it, \`worktree remove\` does.
 
   Simulators are large and live in the CoreSimulator device set, not in your
   project. If the disk is filling up, Stim's own devices are usually not the
@@ -10074,7 +10154,7 @@ a changed value.
 
 WORKSPACE BUILD OUTPUTS
   Each workspace directory holds derived-data/, gradle-build/, android-cas/,
-  cache-provider/, macos/build, the staged macos/<Product>.app and macos/staging-*
+  cache-provider/, js-swap-tmp/, macos/build, the staged macos/<Product>.app and macos/staging-*
   leftovers. The project's own android/app/build, android/build,
   android/.gradle and .build count with them when git ignores every file in
   the directory and tracks none; one that fails that check, or is not in a
@@ -10332,7 +10412,7 @@ KEYS STIM READS
                         (simulator only). Committing
                         { "ios": { "configuration": "Release" } } makes every
                         \`stim ios\` in the app a release-shaped build:
-                        embedded JS, no Metro, cache keyed -release-sim, and
+                        embedded JS, no Metro, cache keyed -release-sim-<arch>, and
                         a JS-bundle swap on cache hits. The \`--configuration\`
                         flag overrides this per invocation. Unset means Debug.
   ios.remote            where the simulator runs, with the same meaning as
@@ -10998,11 +11078,12 @@ A remote machine approves this one when a person there runs
 \`stim-server setup\` with this machine's setup ticket (32 random bytes, 43
 base64url characters) in STIM_SETUP_TICKET. Stim Desktop's Add wizard makes the
 ticket and sets STIM_ACCESS_TICKET for one \`doctor --fix\` run; without it,
-\`doctor --fix\` makes one and prints the setup command to run on the worker.
+\`stim remote add <machine>\` or \`doctor --fix\` makes one and prints the setup
+command to run on the worker.
 Agents never set STIM_ACCESS_TICKET, never run \`stim-server setup\`, never edit
 \`remote.*\`, \`server.*\` or \`hosting.*\` for the user, and never approve requests.
 Until setup approves, the worker answers unknown-secret and the entry stays
-pending; every doctor run tries again. The first connection after approval pins
+pending; every \`stim remote list\` or doctor run tries again. The first connection after approval pins
 the worker's stim-server key in build-machines.json or device-host-machines.json,
 and every later connection must prove that key; the tailnet node and address
 never decide who the worker is. With --fix, a pending entry is replaced when
@@ -11018,8 +11099,8 @@ agents do not run them. \`stim guide facts doctor\` lists the codes.
 REMOTE MACHINES AND PHONE APP
 When the user mentions slow builds, a busy machine, a full disk or device limit, or
 wanting updates away from the desk, tell them about Stim Desktop > Settings >
-Remote Machines > Add (another machine on the tailnet that builds for this one,
-or a Mac that also hosts simulators) or Phones > Pair a Phone (the Stim phone
+Remote Machines > Add, or \`stim remote add <machine>\` in their terminal (another
+machine on the tailnet that builds for this one, or a Mac that also hosts simulators) or Phones > Pair a Phone (the Stim phone
 app). Stim Desktop also suggests these itself, at most once a day and never
 during a build. Agents only tell the user: they never run \`stim-server setup\`,
 never edit \`remote.*\`, \`server.*\` or \`hosting.*\` for the user, and never
@@ -11028,10 +11109,20 @@ approve requests.
 REMOTE MACHINES ARE MACHINE-LEVEL
 \`remote.machines\` names the remote machines this machine may build on and host owned
 simulator sessions on, by MagicDNS name with an optional serve port (default
-7443). Name each node and port once:
+7443). Name each node and port once. From any directory:
+
+  stim remote add janics-mac-mini
+  stim remote list
+  stim remote remove janics-mac-mini
 
-  stim settings set remote.machines '["janics-mac-mini"]'
-  stim doctor --fix
+\`stim remote add\` appends the machine to the machine-scope list, keeping the
+entries already there, asks it for build and device-host approval and prints
+the setup command for it. \`stim remote list\` contacts every listed machine
+and reports both approvals; it asks nothing new. \`stim remote remove\` drops the
+entry and forgets this machine's credentials for it; the remote machine keeps
+its approval until a person there runs the \`stim-server devices revoke\`
+command it prints. Each takes --json. \`stim settings set remote.machines\`
+replaces the whole list.
 
 The order of \`remote.machines\` is the priority order for every workload: the
 build, simulator, emulator and macOS app each go to the first listed machine that
@@ -11059,16 +11150,15 @@ addresses are refused, and the running server applies a change within seconds.
 An interface name follows the interface onto whatever private network it
 joins, so name the address on a machine that moves between networks, and an
 interface only on a worker that stays put. Then the person runs the setup
-command \`stim doctor --fix\` prints here:
+command \`stim remote add\` prints here:
 
   stim settings set server.lanAddresses '["10.0.0.92"]'     # on the worker
-  stim settings set remote.machines '["local:10.0.0.92"]'   # on this machine
-  stim doctor --fix
+  stim remote add local:10.0.0.92                           # on this machine
 
 Every connection runs Stim's Noise handshake, so plain WebSocket carries it
 without TLS, and the address never identifies anyone. Nothing on a local network
 vouches for the worker's key, so \`stim-server setup\` prints the worker's server
-key fingerprint and \`stim doctor --fix\`, run by a person in a terminal, shows
+key fingerprint and \`stim remote list\`, run by a person in a terminal, shows
 the fingerprint the worker answered with and pins the key only after they
 confirm it matches. Until then the entry reports key-unconfirmed and is not
 used. Agents never answer that question. The printed setup command carries the
@@ -11135,8 +11225,8 @@ machine idle: wait for existing work to finish or stop the relevant sessions bef
 benchmarking. Agents change these settings only when the user asks them to.
 
 DEVICE HOSTING
-Only \`doctor --fix\` asks for device-host access: it makes a setup ticket and
-prints the command. A person approves by running \`stim-server setup\` on the
+Only \`stim remote add\` and \`doctor --fix\` ask for device-host access: they
+make a setup ticket and print the command. A person approves by running \`stim-server setup\` on the
 worker with that ticket: one ticket, one expiry, one record per capability for
 the key that holds the ticket, with a per-grant Y/n question (Enter approves) in a
 terminal or \`--yes\` otherwise. Agents never run \`stim-server setup\` or
@@ -11166,9 +11256,11 @@ Stim sends tokens only to the pinned node's own tailnet address,
 with its MagicDNS name for TLS and Host routing. A changed node refuses
 access, and uncertain replies or unreadable credentials preserve the pin.
 An invalid remote.machines setting reports an error and preserves every saved credential.
-\`doctor --fix\` forgets entries removed from remote.machines; remove a
-replaced machine, run it, then re-add the name to request a new approval.
-A definite revoked or lapsed request can be requested again with --fix.
+\`stim remote remove\` forgets the credentials of the machine it removes, and
+\`doctor --fix\` forgets those of entries removed from remote.machines otherwise.
+For a replaced machine, run \`stim remote remove <machine>\`, then
+\`stim remote add <machine>\` to request a new approval. A definite revoked or
+lapsed request can be requested again with \`stim remote add\` or --fix.
 An in-progress approval inspection reports busy rather than replacing its
 pending token. \`stim macos --remote <placement>\` or \`macos.remote\` runs a macOS
 app on an approved remote Mac (stim guide macos), and \`ios.remote\` and
@@ -11197,10 +11289,11 @@ The same \`remote.machines\` list names the machines that may build for this one
     "remote": { "machines": ["janics-mac-mini"] }
   }
 
-\`doctor --fix\`, run in any app directory, makes a setup ticket for each named
-machine and prints the \`stim-server setup\` command a person runs on that
-machine to approve this one, under the approval rule above. The next doctor run
-pins the worker's stim-server key in $STIM_HOME/build-machines.json. A build grant is full access
+\`stim remote add <machine>\`, run in any directory, makes a setup ticket for
+that machine and prints the \`stim-server setup\` command a person runs on that
+machine to approve this one, under the approval rule above; \`doctor --fix\`,
+run in an app directory, does the same for every named machine. The next
+\`stim remote list\` or doctor run pins the worker's stim-server key in $STIM_HOME/build-machines.json. A build grant is full access
 to the account stim-server runs as: project code runs there unsandboxed, so it
 can grant itself read and control. Revoking it does not undo what that code
 already did. Grant it only to machines you trust.
@@ -11280,8 +11373,8 @@ files the native fingerprint hashes or the Expo config reads, such as .env.local
 and other Expo .env files, secrets included. Nothing under node_modules and no
 build output the fingerprint ignores is sent. A fingerprint-mismatch refusal
 names the sources that differ and the files pod install or prebuild rewrote there.
-Run stim doctor --fix to ask for build access if not paired. A person on the
-worker approves it by running the stim-server setup command doctor printed, with
+Run stim remote add <machine> to ask for build access if not approved. A person
+on the worker approves it by running the stim-server setup command it printed, with
 its ticket and expiry. Check stim settings get remote.machines,
 or rerun with --remote-build auto or --remote-build local. Ctrl-C cancels
 the remote build without a local xcodebuild, Gradle or SwiftPM compile.
@@ -12350,9 +12443,9 @@ ON ANOTHER MAC
 
 stim macos --remote <machine> or macos.remote builds the Debug app on this Mac and runs it on an
 approved remote Mac over the tailnet, without SSH. The Mac must be listed
-in remote.machines and approved: stim doctor --fix makes a setup ticket, a
-person on that Mac runs stim-server setup with that ticket and expiry (guide
-settings), and stim doctor then pins that Mac's stim-server key. Stim goes ahead
+in remote.machines and approved: stim remote add <machine> adds it and makes a
+setup ticket, a person on that Mac runs stim-server setup with that ticket and
+expiry (guide settings), and stim remote list then pins that Mac's stim-server key. Stim goes ahead
 only with the stim-server that proves it holds that key.
 A refusal or an unreachable host fails the command; with a named Mac it never launches here
 instead.

package/dist/{hosted-android-y6K3DKQT.mjs → hosted-android-D8JbIzgC.mjs}

@@ -1,7 +1,7 @@
-import { d as throwIfCancelled } from "./exec-CGuDzt40.mjs";
-import { l as call, u as connectHost } from "./hosted-client-Bb89P6an.mjs";
-import { a as requestHostedMetro } from "./metro-request-2LmFpC1z.mjs";
-import { a as stopHostedNative, i as prepareHostedNative, r as placeHostedNative } from "./hosted-native-C9xQYYFb.mjs";
+import { d as throwIfCancelled } from "./exec-L37dbiIb.mjs";
+import { l as call, u as connectHost } from "./hosted-client-BLwuXEZS.mjs";
+import { a as requestHostedMetro } from "./metro-request-DcUxyaq8.mjs";
+import { a as stopHostedNative, i as prepareHostedNative, r as placeHostedNative } from "./hosted-native-OBT2sJxn.mjs";
 //#region src/device-host/hosted-android.ts
 async function prepareHostedAndroid(machine, selectors, recorded, mode) {
 	return await prepareHostedNative(machine, selectors, recorded, "android", false, mode);

package/dist/{hosted-client-Bb89P6an.mjs → hosted-client-BLwuXEZS.mjs}

@@ -1,7 +1,7 @@
-import { d as throwIfCancelled, l as cancellableSleep } from "./exec-CGuDzt40.mjs";
-import { K as resolveEndpoint, P as diagnoseConnectFailure } from "./config-BW0fAtoK.mjs";
-import { t as BuildConnection } from "./client-Dy0eJJtz.mjs";
-import { tt as configuredMachines } from "./support-DW575Dnx.mjs";
+import { d as throwIfCancelled, l as cancellableSleep } from "./exec-L37dbiIb.mjs";
+import { F as diagnoseConnectFailure, q as resolveEndpoint } from "./config-CNmN-ndb.mjs";
+import { t as BuildConnection } from "./client-DU6dnGX1.mjs";
+import { nt as configuredMachines } from "./support-CfYmOdQs.mjs";
 import { createHash } from "node:crypto";
 import { lstatSync, readFileSync, readdirSync, readlinkSync } from "node:fs";
 import { join } from "node:path";
@@ -28,7 +28,7 @@ function credentialRefusal(message, remedy = "Run stim doctor.") {
 function hostingCredential(machine) {
 	const configured = configuredMachines();
 	if (configured === null) throw credentialRefusal("remote.machines is invalid. Run stim guide settings and correct it.", "Run stim guide settings and correct remote.machines.");
-	if (!configured.includes(machine)) throw Object.assign(/* @__PURE__ */ new Error(`${machine} is not in remote.machines. Add it with stim settings set remote.machines, then run stim doctor --fix to ask it for hosting access.`), { code: "STIM_BAD_ARG" });
+	if (!configured.includes(machine)) throw Object.assign(/* @__PURE__ */ new Error(`${machine} is not in remote.machines. Run stim remote add ${machine} to add it and ask it for hosting access.`), { code: "STIM_BAD_ARG" });
 	let credentials;
 	try {
 		credentials = readDeviceHostMachines();
@@ -36,9 +36,9 @@ function hostingCredential(machine) {
 		throw credentialRefusal("The hosting credentials are unreadable. Run stim doctor.");
 	}
 	const credential = credentials.find((each) => each.machine === machine);
-	if (!credential) throw credentialRefusal(`This machine has not asked ${machine} for hosting access. Run stim doctor --fix.`, "Run stim doctor --fix.");
+	if (!credential) throw credentialRefusal(`This machine has not asked ${machine} for hosting access. Run stim remote add ${machine}.`, `Run stim remote add ${machine}.`);
 	if (credential.state !== "approved") {
-		const remedy = `A person on ${machine} runs the stim-server setup command stim doctor --fix printed; then run stim doctor.`;
+		const remedy = `A person on ${machine} runs the stim-server setup command stim remote add ${machine} printed; then run stim remote list.`;
 		throw credentialRefusal(`${machine} has not confirmed hosting access for this machine. ${remedy}`, remedy);
 	}
 	return credential;

package/dist/{hosted-logs-DYPsnWMF.mjs → hosted-logs-BWEQNJx_.mjs}

@@ -1,11 +1,11 @@
-import { t as getExecutor } from "./exec-CGuDzt40.mjs";
-import { E as workspaceDir, k as workspaceLogsDir$1 } from "./workspace-state-BdZ-QgmB.mjs";
-import { l as phaseLine } from "./command-output-CGxrQ3Bd.mjs";
-import { U as parseMachine$1, _t as validateDeviceSlot, ut as deviceSlotFileKey } from "./config-BW0fAtoK.mjs";
-import { n as macosDir } from "./state-DSOUqO-o.mjs";
-import { n as androidLogGroups, r as isAndroidCrashText } from "./android-B2DSKg-A.mjs";
+import { t as getExecutor } from "./exec-L37dbiIb.mjs";
+import { E as workspaceDir, k as workspaceLogsDir$1 } from "./workspace-state-DOPXG2Gp.mjs";
+import { l as phaseLine } from "./command-output-ByEmIwur.mjs";
+import { W as parseMachine$1, dt as deviceSlotFileKey, vt as validateDeviceSlot } from "./config-CNmN-ndb.mjs";
+import { n as macosDir } from "./state-DsrFh3yv.mjs";
+import { n as androidLogGroups, r as isAndroidCrashText } from "./android-BPBARZMR.mjs";
 import { c as readNdjsonGenerations$1, i as createNdjsonWriter } from "./ndjson-CrjIsGzw.mjs";
-import { l as call } from "./hosted-client-Bb89P6an.mjs";
+import { l as call } from "./hosted-client-BLwuXEZS.mjs";
 import { mkdirSync, readFileSync, realpathSync, renameSync, rmSync, writeFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { LOG_ROTATE_BYTES, ambientWrite, withDirLockAsync } from "@stim-cli/core";

package/dist/{hosted-logs-sync-DfUJ2GpF.mjs → hosted-logs-sync-uWSrH2mf.mjs}

@@ -1,8 +1,8 @@
-import { l as phaseLine } from "./command-output-CGxrQ3Bd.mjs";
-import { n as pullHostedNativeLogs, r as readHostedNativeLogs, t as pullHostedMacosLogs } from "./hosted-logs-DYPsnWMF.mjs";
-import { u as connectHost } from "./hosted-client-Bb89P6an.mjs";
-import { n as readHostedIos, t as readHostedAndroid } from "./ios-state-CWsBysyN.mjs";
-import "./hosted-macos-DsEzYVY_.mjs";
+import { l as phaseLine } from "./command-output-ByEmIwur.mjs";
+import { n as pullHostedNativeLogs, r as readHostedNativeLogs, t as pullHostedMacosLogs } from "./hosted-logs-BWEQNJx_.mjs";
+import { u as connectHost } from "./hosted-client-BLwuXEZS.mjs";
+import { n as readHostedIos, t as readHostedAndroid } from "./ios-state-enWc5P6U.mjs";
+import "./hosted-macos-BnCYAv1y.mjs";
 import { watch } from "node:fs";
 import { dirname, relative, resolve, sep } from "node:path";
 import { ambientWrite, configDir } from "@stim-cli/core";