peachsim 0.1.1619 → 0.1.1625

package/README.md

@@ -231,6 +231,11 @@ actions discover the sim's owning world. Each world probe has one two-second
 wall deadline covering both connection and response. An inferred default port
 does not override the named sim's world.
 
+Bridge sockets use TCP keepalive so a governor-stopped browser can resume an
+in-flight render without losing its connection to an unanswered application
+ping. Command deadlines still bound stalled work; idle leases and abandoned
+sim cleanup remain separate from transport liveness.
+
 **The sim** is a browser/Electron *page* launched by a CLI driver. Inside that
 page run three workers: the **shell worker** owns device and native state, the
 **compositor worker** paints every visible CanvasKit surface, and the **tenant
@@ -279,7 +284,7 @@ therefore runs before assertions in each flow.
 | runtime delivery + Peach home | Versioned engine runtime management. The shared machinery owns manifest fetch, sha256 verification, channels, and auto-update. Peach binds it to `https://contrast.dev` and `~/.peach/runtimes/<version>`. A repo can select `runtimeVersion` without changing the machine default. | `src/runtime-delivery.ts`, `packages/contrast-runtime-delivery/`, `src/home-paths.ts`, `src/runtime-assets.ts` |
 | standalone CLI delivery | Cached stable-version checks, bounded interactive notices, and verified atomic executable replacement. | `cli/cli-update.ts`, `cli/commands/upgrade.ts`, `cli/commands/version.ts`, `src/cli-version.ts` |
 | `peachsim/vite` + `peachsim/metro` (runtime serving) | Published bundler plugins. Both serve the installed engine runtime at `/__peachsim/` from `~/.peach/runtimes/<version>` so an app's own dev server can host the sim shell; the Vite plugin can opt into a named Electron window. | `src/vite-plugin-one.ts`, `src/metro-plugin.ts`, `src/runtime-assets.ts` |
-| `sootsim()` vite resolver plugin (internal) | The large RN-resolution / native-stub vite plugin: aliases `react-native` to the engine shim, native packages to `@sootsim/compat` stubs, applies worklets/babel transforms, and instantiates `SootSimBridgeHost` in its dev server. Distinct from the published `peachsim/vite` export. | `src/vite-plugin.ts`, `src/worklets-babel.ts`, `packages/peach-compat/src/stub-manifest.ts` |
+| `sootsim()` vite resolver plugin (internal) | The large RN-resolution / native-stub vite plugin: aliases `react-native` to the engine shim, native packages to `@sootsim/compat` stubs, and applies worklets/babel transforms. Distinct from the published `peachsim/vite` export. | `src/vite-plugin.ts`, `src/worklets-babel.ts`, `packages/peach-compat/src/stub-manifest.ts` |
 | skills registry | Peach agent skills (`peach-setup`, `peach-debug`, `peach-test`, `peach-visual`, and the generated `contrast` index) installable with `peach skill`. | `skills/*.md`, `src/skills/registry.ts`, `src/skills/types.ts` |
 
 ## Getting started
@@ -510,8 +515,8 @@ a supported input; pass Peach the JavaScript bundle produced before Hermes
 compilation.
 
 If an app has unusual dependencies or fingerprint inference fails, you can
-optionally wrap your Metro configuration with `withPeach(config)`. It takes no
-options and enables two integrations:
+optionally wrap your Metro configuration with `withPeach(config)`. It enables
+two integrations:
 
 1. **Deterministic module identity:** appends Metro's exact module identity map
    as a trailing `globalThis.__sootsimModulePaths = { ... }` footer to every
@@ -521,6 +526,23 @@ options and enables two integrations:
 2. **In-browser dev shell:** serves the Peach simulator shell at `/__peachsim/` on
    the Metro dev server.
 
+Native app identity also travels in the bundle. Android permissions come only
+from a completed app manifest merger output. A sole output under
+`android/<module>/build/intermediates/merged_manifests/` is selected automatically;
+select one explicitly when multiple variants exist:
+
+```js
+module.exports = withPeach(config, {
+  androidMergedManifest:
+    'android/app/build/intermediates/merged_manifests/debug/processDebugManifest/AndroidManifest.xml',
+})
+```
+
+Without resolved merged output, Android permissions contain only the explicit
+Expo `android.permissions` set minus `android.blockedPermissions`. Defaults,
+plugins and linked library additions require completed merged output. See the
+[native identity contract](../../specs/sootsim-engine/native-app-identity.md).
+
 The URL helpers request ordinary Metro graphs: `dev=false&minify=true` for
 production and `dev=true&minify=false` for development.
 
@@ -571,6 +593,12 @@ and video recording create a new browser context; cold launches still use the
 supplied shell URL. When synchronization is enabled, URL delivery waits for
 existing work before dispatch and for navigation and painting afterward.
 
+Element taps finish viewport measurement before resolving the selected node's
+current center, visible frame, and relative offset in the browser task that
+sends the physical tap. Stillness samples do not supply later tap coordinates:
+startup layout can change while other bridge reads finish. A removed node
+rejects the action instead of reusing its old geometry.
+
 See `../../docs/migrating-from-detox.md` for details.
 
 ## Coming from Maestro
@@ -751,8 +779,10 @@ fails instead of loading empty native configuration. Bare Metro, which has no
 Expo manifest project root, uses
 the listening development process's cwd inside that same resolver. The invoking
 CLI's cwd is never an asset/config fallback. Asset wires stay on each opened
-project URL, so one daemon can serve several attached projects without sharing
-font or splash state between them.
+project URL. Font catalogs use content-addressed bridge asset references, so
+the navigation request stays bounded as the number of fonts grows. Recordings
+resolve these references before capturing the catalog and its assets. One daemon
+can serve several attached projects without sharing font or splash state.
 
 Bare iOS projects carry default Firebase options from their selected app
 target's Google services build resource when the app delegate initializes

package/cli/app-fonts.ts

@@ -4,6 +4,7 @@ import { createRequire } from 'node:module'
 import path from 'node:path'
 import {
   encodeAppFontsWire,
+  resolveAppFontsWire,
   expoFontPathsFromPlugins,
   nativeLinkedFontSpecsFromPaths,
   metroFontSpecsFromPaths,
@@ -448,7 +449,7 @@ export async function fetchAppFontFiles(
 ): Promise<FetchedAppFont[]> {
   const out: FetchedAppFont[] = []
   const seen = new Set<string>()
-  for (const url of appFontAssetUrlsFromWire(wire)) {
+  for (const url of appFontAssetUrlsFromWire(await resolveAppFontsWire(wire, fetch))) {
     const urlhash = createHash('sha256').update(url).digest('hex')
     if (seen.has(urlhash)) continue
     seen.add(urlhash)