stim 1.36.0 → 1.38.0

package/dist/{guide-CuvHRP53.mjs → guide-DqJCc4vW.mjs}

@@ -1,8 +1,8 @@
-import { t as ANDROID_AVD_CONFIG_HELP } from "./settings-Bap-qjnp.mjs";
-import { i as findProjectRoot$1 } from "./project-Clk1JAWL.mjs";
-import { h as RECENT_LAUNCH_MS } from "./eas-session-ledger-CXZ4aix0.mjs";
-import { o as guideStatus, t as WATCHMAN_NESTED_WORKTREES } from "./doctor-watchman-TZxYt_98.mjs";
-import "./status-watch--rfZynD_.mjs";
+import { t as ANDROID_AVD_CONFIG_HELP } from "./settings-Cz8kQJzr.mjs";
+import { i as findProjectRoot$1 } from "./project-DIo71tGq.mjs";
+import { h as RECENT_LAUNCH_MS } from "./eas-session-ledger-BDpSdFDM.mjs";
+import { o as guideStatus, t as WATCHMAN_NESTED_WORKTREES } from "./doctor-watchman-B8e3s9ko.mjs";
+import "./status-watch-Cs18eFkQ.mjs";
 import { SETTINGS, SETTINGS_SCHEMA_URL, TUTORIAL_VERSION } from "@stim-cli/core/state";
 import chalk from "chalk";
 //#region src/guide/agent.ts
@@ -616,8 +616,15 @@ All methods accept signal. run builds, installs and launches. iOS and Android ru
 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. @stim-cli/ci uses it; the CLI and the
-private Desktop transport do not.
+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
@@ -635,13 +642,18 @@ Build options:
   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. 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. easProfile downloads a
+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
@@ -958,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
@@ -1627,7 +1641,8 @@ RULES
     invalidProjects         { path }  the registry key is not absolute
     orphanedPorts           { project, label, port }
     orphanedWorkspaces      { dir, projectRoot, bytes }  --delete removes the
-                              whole workspace directory
+                              whole workspace directory; projectRoot is null
+                              for an empty directory with no workspace.json
     linkedWorktrees         { path, idleDays, mergedInto, pullRequest,
                               pullRequestUnknown, willRemove, reason,
                               detail, eligibleAt, buildState }  mergedInto is the
@@ -1718,9 +1733,10 @@ RULES
                               whose absolute workspace root is missing on a
                               mounted volume; --delete forgets the entry
                               only and contacts no EAS session
-    staleStatusCaches       { kind: "disk-usage" | "pull-request", path,
-                              file, bytes }  entries of $STIM_HOME/disk-usage
-                              and pull-requests whose path is gone from a
+    staleStatusCaches       { kind: "disk-usage" | "pull-request" | "git-merge",
+                              path, file, bytes }  entries of
+                              $STIM_HOME/disk-usage, pull-requests and
+                              git-merge whose path is gone from a
                               mounted volume; --delete removes the file
     idleDevices             { kind, id, name, project, slot, lastActivityAt,
                               idleForMs, buildInProgress }  booted owned
@@ -1759,7 +1775,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,
@@ -1855,12 +1871,14 @@ RULES
                               "busy" | "unknown", reclaimable, reason,
                               detail }  without --cache, or with --cache
                               watchman or gradle-daemons; reclaimable marks
-                              the ones gc --delete --cache <cacheKind>
-                              would stop (\`guide cleanup memory\`)
+                              the ones gc --delete would stop (watchman) or
+                              gc --delete --cache gradle-daemons would
+                              (\`guide cleanup memory\`)
     watchmanRoots           { path, stale: "missing" | "pruned-worktree" |
                               null, subscriptions, triggers, removable,
                               detail }  removable marks the stale roots
-                              --cache watchman would watch-del
+                              gc --delete (or --cache watchman) would
+                              watch-del
     memoryNotices           { message }  why the memory sweep was skipped
   bytes is null when the size is unknown: not measured, or the measurement
   failed. idleDays is null when the last use is unknown. listed is false for
@@ -2846,6 +2864,9 @@ project's before exiting. You get your shell back with a bundler running: no
 backgrounding idiom, no sleep, no poll loop, and no chance of building against
 another worktree's bundler.
 
+If Expo cannot be resolved in a linked worktree, run \`stim worktree warm\`
+there before retrying. The refusal also names dependency installation.
+
   --json            one line of facts on stdout, everything else on stderr:
                       { port, supervisorPid, mode, logsDir, alreadyRunning }
   --wait <seconds>  how long to wait for server and remote tunnel readiness
@@ -3014,8 +3035,9 @@ WHAT THE SUPERVISOR IS
                  for the bundle lines.
 
   expo-child and command-child put the Node the app pins (.nvmrc,
-  .node-version, .tool-versions nodejs, or package.json volta.node) first
-  on PATH when an nvm, fnm, Volta, asdf, mise or linked Homebrew
+  .node-version, .tool-versions nodejs, or package.json volta.node), looking
+  from the app directory up to its repository or worktree root, first on PATH
+  when an nvm, fnm, Volta, asdf, mise or linked Homebrew
   node/node@NN install satisfies the pin and the node already on PATH does
   not; the metro log then records a project_node event naming it. When no
   install has the version the pin names, the newest install of the pinned
@@ -4043,7 +4065,8 @@ Branch on the code, never on the message.`,
   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
+  - NO ANDROID SDK, before gradle starts: local React Native emulator runs
+    refuse before Metro or device setup. Nothing exists at the SDK path
     Stim resolves (ANDROID_HOME, else ANDROID_SDK_ROOT, else the default
     location), and there is no android/local.properties. Set ANDROID_HOME to the SDK or write sdk.dir
     into android/local.properties; \`stim doctor --platform android\` reports
@@ -4285,7 +4308,9 @@ too old to speak protocol 2, incompatible
 toolchain/runtime/CPU, low disk, busy, sync/build failure, artifact failure,
 or a checkout that changed while it built. Unsupported build kinds also refuse.
 No local xcodebuild, Gradle or SwiftPM compile or alternate machine follows a
-refusal. For stim ios, a toolchain difference on the named machine, such as Xcode,
+refusal. For stim android, a known toolchain refusal on the named machine stops
+before prebuild; busy, low disk and unreachable are checked again afterward.
+For stim ios, a toolchain difference on the named machine, such as Xcode,
 the simulator runtime or the CPU, refuses before this machine runs prebuild or pod
 install, even when prebuild would have produced an app the local cache already holds, or the
 machine already holds the exact artifact. A
@@ -4780,7 +4805,8 @@ so a Debug run on one is wired to a LAN origin instead of localhost.`,
   owned by this Stim home, or it is not booted or running. Permission and push
   also refuse when no app is recorded for the device. Run the platform command
   the remedy names (\`stim ios\` or \`stim android\`, with \`--slot\` for a named
-  slot) and retry. No tool runs before this refusal.`
+  slot) and retry. A non-Mac client cannot run a local iOS simulator; run the
+  iOS tool on a Mac with a local Stim-owned simulator. No tool runs before this refusal.`
 		},
 		STIM_DEVICE_TOOL_UNSUPPORTED: {
 			summary: "that device tool has no equivalent on that platform",
@@ -5562,6 +5588,16 @@ not on any remote"  (worktree remove)
   source path and warm cannot move it, it prints "removed <dir>/Pods/Manifest.lock
   so pod install runs" and \`stim ios\` runs \`pod install\`.
 
+"carry       left out <app>/<platform>: <reason>"
+  The app is an Expo project whose ios/ or android/ Git ignores, and Stim
+  cannot show the source checkout's copy was generated from the app's current
+  inputs: Stim has no prebuild record for it, its last prebuild did not
+  finish, or the record names an earlier native fingerprint. Warm does not
+  copy it, so the first \`stim <platform>\` in this worktree generates it
+  fresh. Nothing to fix. To let later warms copy it, delete <platform>/ in
+  the source checkout and run \`stim <platform>\` there, so Stim generates it
+  fresh and records that.
+
 "carry       carried <dir>/Pods but there is no <dir>/Podfile.lock"
   Warm copied Pods but the destination has no Podfile.lock. Follow the printed
   pod-install command before building.
@@ -6189,7 +6225,9 @@ not the caller's. The returned fingerprint remains null; transfer digests never
 become reusable APK cache keys. Workers with native-gradle-peer-cache can offer a
 completed APK for declared source and resolved variant, ABI and build options,
 rechecking current private inputs against the saved receipt at offer and fetch.
-A hit skips source upload and compilation even while that worker is busy or
+When this machine has a JDK, native-gradle-peer-jdk also selects that exact
+JDK major for the private-input check. Older workers skip this lookup and use
+normal build placement. A hit skips source upload and compilation even while that worker is busy or
 this machine has room. A miss follows normal placement; older Gradle workers
 still build normally. Off mode, explicit local builds and disabled remote cache
 reads skip peer lookup. Hosts without native-gradle-build refuse before upload.
@@ -6218,6 +6256,7 @@ cleanup stops that workspace, including resources created before a build fails.
 
 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.
+Without --, run installs and launches the app, then stops it with exit code 0.
 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)
@@ -6228,6 +6267,16 @@ 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.
@@ -6690,8 +6739,10 @@ ${HOSTED_RECORDING("simulator")}
 
 If hosting.agentDriver is none, the driver cannot enforce its policy, or the
 host does not advertise hosted-ios-agent, agent reports
-{ driver: 'none', setting: 'hosting.agentDriver' }. Update the host and check
-its setting and agent-device installation. No other simulator becomes reachable.
+{ driver: 'none', setting: 'hosting.agentDriver' }. A run whose host disables
+the driver prints a notice; plain status also names the host setting when
+agent control is unavailable. Update the host and check its setting and
+agent-device installation. No other simulator becomes reachable.
 Client hello carries only name and version, not features, so the host cannot gate
 daemon startup or grant issuance on client support. The client checks the host's
 hosted-ios-agent feature before using a grant.
@@ -7067,7 +7118,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
@@ -7735,7 +7786,7 @@ WHAT MAKES THE CACHE ACTUALLY HIT: .FINGERPRINTIGNORE
   looks exactly like a cache that is not there.
 
   Stim ignores paths a fresh checkout never has and no native Debug build
-  reads: android/local.properties, android/.idea, *.xcodeproj/xcuserdata, and,
+  reads: android/local.properties, android/.idea, *.xcodeproj/xcuserdata, .git (and its contents), .expo, and,
   while a .gitignore pattern matches them (even when committed), the
   \`react-native bundle\` output ios/main.jsbundle and ios/assets. A project
   does not repeat those.
@@ -8048,7 +8099,7 @@ OPT-IN CONCURRENCY LIMITS (UNLIMITED BY DEFAULT)
 			summary: "every flag per command, Android variants and flavors, the per-run simulator model, runtime and system image",
 			body: () => `THE OPTION SURFACE, IN FULL
   start           --json --wait <seconds> --remote --reset-cache
-  ios             --remote-build <local|auto|remote|remote-only|name> --slot <name> --json --plan --no-metro-check --no-build-cache --scheme <name> --configuration <name> --device-type <name> --runtime <version> --simulator-app <xcode|siniulator|stim-desktop> --device [udid] --wait <seconds> --no-wait --remote <eas|proxy|local|auto|remote|remote-only|machine>
+  ios             --remote-build <local|auto|remote|remote-only|name> --slot <name> --json --plan --no-metro-check --no-build-cache --scheme <name> --configuration <name> --device-type <name> --runtime <version> --install-runtime --simulator-app <xcode|siniulator|stim-desktop> --device [udid] --wait <seconds> --no-wait --remote <eas|proxy|local|auto|remote|remote-only|machine>
   android         --remote-build <local|auto|remote|remote-only|name> --slot <name> --json --plan --no-metro-check --no-build-cache --variant <name> --system-image <id> --device-profile <id> --device [serial] --wait <seconds> --no-wait --remote <proxy|eas|local|auto|remote|remote-only|machine>
   ios/android --wait bounds owned-device slot waits (default 600s), or physical
   leases with --device (default 60s). Remote targets do not join this local
@@ -8226,16 +8277,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
@@ -8243,9 +8296,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
@@ -8265,6 +8318,17 @@ OPT-IN CONCURRENCY LIMITS (UNLIMITED BY DEFAULT)
   cannot (stale node_modules, a leftover path, an error), warm deletes
   ios/Pods/Manifest.lock so \`stim ios\` runs \`pod install\`.
 
+  In an Expo project whose ios/ or android/ Git ignores, warm copies that
+  directory only when the source's last Stim prebuild of it ran on the app's
+  current native fingerprint, and records the same prebuild in the worktree.
+  Otherwise it leaves the directory out and prints
+  "carry       left out <app>/<platform>: <reason>"; the first
+  \`stim <platform>\` there generates it fresh. A directory generated outside
+  Stim has no record and is left out. To make it eligible, delete it in the
+  source checkout and run \`stim <platform>\` there so Stim generates it
+  fresh; running Stim over the existing directory records it as current even
+  when it came from an older template.
+
   Other generated state stays eligible: .gradle, .cxx, *.tsbuildinfo, build
   directories, and embedded JavaScript need project-specific decisions about
   regeneration. Native intermediates can record the source checkout's paths;
@@ -8328,6 +8392,26 @@ OPT-IN CONCURRENCY LIMITS (UNLIMITED BY DEFAULT)
   ios.runtime, android.systemImage, android.deviceProfile) for that one
   invocation, exactly as \`--configuration\` overrides ios.configuration.
 
+  \`stim ios --runtime 26.5 --install-runtime --remote local\` installs that
+  missing iOS runtime with Xcode, then continues the run. Use
+  \`--remote <mac>\` for a named approved hosting Mac, including from Linux.
+  ios.autoInstallRuntime enables the same opt-in for an explicit ios.runtime
+  or --runtime version; it defaults to false. Installation requires an exact
+  major.minor[.patch] version, about 8-10 GB to download (actual size varies),
+  and at least 20 GB free on the simulator volume for download and unpacking.
+  A child-aware ownership claim serializes Stim installs in this Mac's Stim
+  home and the installer takes an available build slot. Run output shows
+  Xcode progress locally and periodic waiting messages remotely; status shows
+  the install phase and remote machine. Without opt-in, a missing runtime
+  still refuses. Automatic placement, eas/proxy and physical-device runs do
+  not install runtimes: choose --remote local or one named Mac first.
+  Xcode Settings > Components lists downloadable versions supported by Xcode;
+  Stim retains Xcode's error for unavailable versions. Installed versions
+  appear in stim doctor and xcrun simctl list runtimes. Runtimes are shared
+  Xcode components, not Stim-owned devices: remove them manually through
+  Xcode Settings > Components after checking other workspaces no longer need
+  them. Stim does not prune them.
+
   A name that is not INSTALLED on this machine refuses with STIM_BAD_ARG
   before anything is created, and the message lists the installed names, so a
   wrong guess is one command, not a created simulator. A blank value is the
@@ -8730,6 +8814,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
@@ -8740,7 +8827,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
@@ -8792,13 +8883,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,
@@ -9049,8 +9143,9 @@ In on mode a pass runs, cheapest to rebuild first:
   3. build-cache and Metro entries, least recently used first, down to
      maintenance.capTargetPercent of caches.buildCacheMaxGb or
      caches.metroCacheMaxGb, and entries unused for olderThanDays
-  4. the Swift compilation cache, emptied whole, only below
-     budget.hardFloorDiskGb, and kept while an iOS build holds its shared
+  4. the Swift compilation cache, emptied whole once it is over
+     caches.swiftCompilationCacheMaxGb (default 0, no cap), whatever the free
+     disk, and kept while an iOS build holds its shared
      claim (taken for each xcodebuild run that compiles with it) or that
      claim is unresolved; the emptying holds the exclusive claim
   5. linked worktrees whose branch or pull request finished (gc's finished
@@ -9248,8 +9343,9 @@ WHAT RECLAIMS AN OWNED DEVICE
                             shuts DOWN (never deletes) owned devices with no
                             driver, claim or activity for that long
 
-\`gc --delete --cache watchman\` and \`gc --delete --cache gradle-daemons\`
-stop shared helper processes, not devices (\`guide cleanup memory\`).
+\`gc --delete\` also shuts down an unused watchman daemon, and \`gc --delete
+--cache gradle-daemons\` stops idle Gradle and Kotlin daemons. They are shared
+helper processes, not devices (\`guide cleanup memory\`).
 
 \`worktree remove\` and \`gc --delete\` are the only two commands that delete;
 \`gc --delete\` deletes worktrees only through \`worktree remove\`. \`gc
@@ -9722,8 +9818,15 @@ ORPHANED WORKSPACE DIRECTORIES
   "Orphaned workspace directories" when the recorded project root is gone,
   its volume is mounted, no registry key equals it or sits under it, and the
   workspace is not in use. \`gc --delete\` re-checks each one, then removes
-  it. A directory with a missing or unparseable workspace.json, or a root on
-  an unmounted volume, is reported under Skipped and never deleted.
+  it. A directory with an unparseable workspace.json, or a root on an
+  unmounted volume, is reported under Skipped and never deleted.
+  A directory with no workspace.json that holds only leftovers of a removed
+  workspace is reported the same way: maintenance.ndjson, log-error-index.json,
+  ended-agents.json, empty lock files and an agent-device directory with no
+  running daemon. It counts as gone when it is empty, or when the project
+  root its maintenance log names maps to the directory name and is gone. Any
+  other file (state.json, for one), a held lock or a log naming no root keeps
+  it under Skipped. The empty directory report has no project root.
 
 DELETED WORKTREES STILL REGISTERED
   A worktree deleted outside Stim keeps its registry entry; \`stim status\`
@@ -9758,9 +9861,11 @@ TMPDIR LEFTOVERS
 STALE STATUS CACHE ENTRIES
   \`stim status\` caches each folder's size under $STIM_HOME/disk-usage and
   each worktree's pull request under $STIM_HOME/pull-requests, which the
-  maintenance worktree check and \`gc --delete\` also write. \`worktree
+  maintenance worktree check and \`gc --delete\` also write. The merge check
+  caches each worktree's verdict under $STIM_HOME/git-merge. \`worktree
   remove\` drops the entries of the worktree it removed (its checkout,
-  node_modules and workspace folder, and its pull request), not the size
+  node_modules and workspace folder, its pull request and its merge
+  verdict), not the size
   entries of its owned devices' data folders. \`gc\` reports the
   entries of a folder or worktree that was removed some other way under "Stale
   status cache entries", and \`gc --delete\` removes them. An entry counts as
@@ -9819,6 +9924,10 @@ WHICH stim-* DEVICES gc DELETES
   \`rm -rf <dir>\` for AVD data with no registration), and
   never runs it. Boot, shutdown and teardown re-check ownership by the same
   rule, so a device that stops matching is left alone.
+  With STIM_HOME set, gc skips the device sweep because simulators and AVDs
+  are machine-global, but pruning a dead project still deletes the devices its
+  record marks as owned. gc lists them as to be deleted under "Device sweep
+  notices"; every other stim-* device is reported as not touched.
 
 ANDROID DATA WITHOUT A REGISTRATION
   \`gc\` also reports stim-*.avd directories whose .ini registration is
@@ -9838,6 +9947,9 @@ BUILD LOCKS
   \`gc --delete\` clears them. A lock whose builder IS running is a build in
   progress -- it is named in the report and touched by nothing, because
   removing it would put a second workspace on the same compile.
+  \`gc --delete\` also removes the empty directories under ~/.stim/process-locks
+  that removed projects and worktrees leave behind; it never touches a lock
+  that holds a claim.
 
 DEVICE LEASES
   A workspace can hold a timed lease on a physical device. The lease is one
@@ -9988,7 +10100,7 @@ THE ONE CASE GC WILL NOT REAP
   Wall-clock timestamps and command names are not ownership proof.`
 		},
 		memory: {
-			summary: "watchman and Gradle and Kotlin daemon memory in gc, and when gc --delete --cache watchman or gradle-daemons stops them",
+			summary: "watchman and Gradle and Kotlin daemon memory in gc, and when gc --delete and gc --delete --cache gradle-daemons stop them",
 			body: () => `MEMORY
   Every \`gc\` without --cache, and \`gc --cache watchman\` or
   \`gc --cache gradle-daemons\`, reports the long-lived helpers that grow while
@@ -9996,19 +10108,22 @@ THE ONE CASE GC WILL NOT REAP
   daemons. Each line gives the pid, physical footprint (the measure status
   uses; resident size when the footprint cannot be read), uptime and whether
   it is idle, and a kept one says why. The reclaimable line totals what
-  the two commands below would free now.
+  the commands below would free now.
 
-  Only these two commands stop anything, and each acts only on its own kind.
-  Neither a plain \`gc --delete\` nor \`--cache all\` touches them:
-    stim gc --delete --cache watchman
+  Watchman is stopped by a plain \`gc --delete\` and by \`gc --delete --cache
+  watchman\`; \`--cache all\` and every other \`--cache\` value leave it alone.
+  The Gradle and Kotlin daemons are stopped only by \`--cache gradle-daemons\`:
+    stim gc --delete              (or: stim gc --delete --cache watchman)
                                   runs \`watchman watch-del\` on each stale root
                                   with no subscription or trigger, then
                                   \`watchman shutdown-server\` only when
                                   \`debug-status\` lists no client but gc's own
-                                  call and no root has a trigger; otherwise
-                                  the daemon is kept and the report names
-                                  each client, as the Stim workspace whose
-                                  dev server it belongs to where it can
+                                  call, every root's subscriptions and
+                                  triggers were readable and no root has a
+                                  trigger; otherwise the daemon is kept and
+                                  the report names each client, as the Stim
+                                  workspace whose dev server it belongs to
+                                  where it can
     stim gc --delete --cache gradle-daemons
                                   stops each Gradle daemon its own
                                   \`gradle --status\` reports IDLE, then each
@@ -10118,7 +10233,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
@@ -10235,8 +10350,13 @@ DEVICE RECORDINGS
   stays.
 
 SHARED BUILD CACHES
-  The caches that make a second workspace fast are alive by design and never
-  included in a plain \`gc --delete\`. Every \`gc\` run reports them anyway,
+  The caches that make a second workspace fast are alive by design and, with
+  one exception, not touched by a plain \`gc --delete\`. The exception is the
+  Swift compilation cache (the Xcode CAS under $STIM_HOME/compilation-cache):
+  once it is over caches.swiftCompilationCacheMaxGb (default 0, no cap), a
+  plain \`gc --delete\` empties it whole, since age trimming would corrupt its
+  index. It is kept, with the build named, while an iOS build holds its shared
+  claim or that claim is unresolved. Every \`gc\` run reports them anyway,
   each row tagged (registered) or (detected), with its size:
     stim gc                            # report, caches included
     stim gc --delete --older-than 30   # trim entries nothing has used
@@ -10363,6 +10483,15 @@ KEYS STIM READS
                         The \`--runtime\` flag overrides this per invocation,
                         and an uninstalled version refuses the same way,
                         naming the layer the value came from
+  ios.autoInstallRuntime false (default). With true and an explicit ios.runtime
+                        or --runtime version, install a missing iOS runtime
+                        with Xcode on the local or named approved Mac before
+                        continuing. --install-runtime opts in for one run.
+                        Requires 20 GB free for download and unpacking;
+                        typically downloads 8-10 GB (actual size varies).
+                        Automatic placement, eas/proxy and physical phones
+                        do not install runtimes. Shared runtimes are removed
+                        manually in Xcode Settings > Components.
   ios.scheme            e.g. "RNTester" -- the shared Xcode scheme to build
                         when the workspace lists several and none matches
                         its name, which otherwise refuses with
@@ -10376,7 +10505,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
@@ -11330,7 +11459,7 @@ stats. A listed paired name with a cache hit compiles nothing, contacts no worke
 and records buildMachine with builtOn absent. Build failures retain the selected
 value; builtOn is here or the configured machine entry when compilation ran.
 Prebuild and pod install still run on this machine before a named offload; stim ios
-checks the machine's toolchain first. A refusal
+and stim android check the machine's toolchain first. A refusal
 starts no local xcodebuild, Gradle or SwiftPM compile.
 A React Native offload sends the tracked and untracked files, and the gitignored
 files the native fingerprint hashes or the Expo config reads, such as .env.local
@@ -11424,7 +11553,9 @@ do not query peer caches. Older workers continue normal placement. This peer
 lookup also covers declared native Gradle worker APKs when the worker supports
 native-gradle-peer-cache. It rechecks current private inputs against the saved
 receipt at offer and fetch for the requested source, resolved variant, ABI and
-build options. Caller fingerprints stay null; worker keys stay worker-scoped.
+build options. With a known local JDK, lookup also requires native-gradle-peer-jdk
+and rechecks on that exact JDK major; older workers use normal build placement.
+Caller fingerprints stay null; worker keys stay worker-scoped.
 React Native and Expo development builds also query enabled paired workers
 with react-native-peer-cache after local and configured-provider misses. Their
 post-mutation fingerprint, native build choices and compatible toolchain must

package/dist/{hosted-android-D__HGVIO.mjs → hosted-android-gwLspaz6.mjs}

@@ -1,7 +1,7 @@
-import { d as throwIfCancelled } from "./exec-CGuDzt40.mjs";
-import { l as call, u as connectHost } from "./hosted-client-DMOOu8vD.mjs";
-import { a as requestHostedMetro } from "./metro-request-O8Q-JvBg.mjs";
-import { a as stopHostedNative, i as prepareHostedNative, r as placeHostedNative } from "./hosted-native-BiiUG_Q6.mjs";
+import { d as throwIfCancelled } from "./exec-L37dbiIb.mjs";
+import { l as call, u as connectHost } from "./hosted-client-B_h_bTlz.mjs";
+import { a as requestHostedMetro } from "./metro-request-BWCl3Zco.mjs";
+import { a as stopHostedNative, i as prepareHostedNative, r as placeHostedNative } from "./hosted-native-B6ur_0OJ.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-DMOOu8vD.mjs → hosted-client-B_h_bTlz.mjs}

@@ -1,7 +1,7 @@
-import { d as throwIfCancelled, l as cancellableSleep } from "./exec-CGuDzt40.mjs";
-import { F as diagnoseConnectFailure, q as resolveEndpoint } from "./config-BA3TgoIP.mjs";
-import { t as BuildConnection } from "./client-KSWIeQLA.mjs";
-import { nt as configuredMachines } from "./support-BJbXovoO.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-qwmHFSga.mjs";
+import { nt as configuredMachines } from "./support-BeVRaMWT.mjs";
 import { createHash } from "node:crypto";
 import { lstatSync, readFileSync, readdirSync, readlinkSync } from "node:fs";
 import { join } from "node:path";