dsh-mobilecode 0.11.8 → 0.11.9

package/lib/client.js

@@ -198,7 +198,7 @@ window.__ModuleLoader__.load({
 		// Shown on both stream captions so a refresh visibly proves which client
 		// bundle the browser is actually running. Kept in lockstep with
 		// package.json by test/client.mjs.
-		const MC_VERSION = "0.11.8";
+		const MC_VERSION = "0.11.9";
 		// The panel shows cards for platforms the host can actually drive; the
 		// server reports its OS in info.os (iOS tooling is darwin-only).
 		const fallbackPlatforms = (os) => (os === "darwin" ? ["ios", "android"] : ["android"]);
@@ -1607,3 +1607,4 @@ window.__ModuleLoader__.load({
 		return module.exports;
 	}
 });
+

package/lib/skill.js

@@ -47,7 +47,7 @@ The loop is **observe once → act with an assertion → observe again only if t
 - Prefer \`device_tap_element\` (resource-id / text / content-desc). Raw pixel coordinates through \`device_input action=tap\` are the last resort — they break on the next layout change.
 - When you must tap pixels, take the center of a box from \`device_ui_tree\`/\`device_screen\`: x=(x1+x2)/2, y=(y1+y2)/2. Coordinates are ABSOLUTE pixels of the current display.
 - \`device_input action=swipe\` scrolls; \`action=key\` with "back" is a first-class verb on Android — use it instead of hunting for an on-screen back arrow.
-- Typing: ASCII goes through `input text` directly. Non-ASCII (Chinese, emoji) needs the ADBKeyboard IME — `device_input` uses it automatically when installed, and refuses with the install hint otherwise (github.com/senzhk/ADBKeyBoard); do not retry a refused non-ASCII type.
+- Typing: ASCII goes through \`input text\` directly. Non-ASCII (Chinese, emoji) needs the ADBKeyboard IME — \`device_input\` uses it automatically when installed, and refuses with the install hint otherwise (github.com/senzhk/ADBKeyBoard); do not retry a refused non-ASCII type.
 
 ## Never guess a package name or a control
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-mobilecode",
   "description": "MobileCode for the dsh web GUI: detect iOS/Android projects, run preview servers, and drive the simulator/emulator from the session — 37 agent tools (device_run, device_screen, device_ui_tree, device_ui_rows, device_tap_row, device_tap_element, device_wait_for, device_scroll_to, device_input, device_batch, device_intent, device_connect, device_pair_qr, device_perf, device_meminfo, device_backtrace, device_display, device_avd_create, device_pair_capture, device_app_info, device_install, device_uninstall, device_reboot, device_log, live screen stream, multimodal screenshots) plus a host-mediated co-op mesh hub (random callsigns, JSON pub/sub, tunable latency/jitter/drop/dup/throttle) so two virtual devices — and the AI watching them — can talk in real time. One classified adb boundary and a Wi-Fi connect/pair QR flow in the Connection settings tab. Hot-pluggable — mounted via the profile bundle list + cordis.patch.yml, no dsh source changes.",
-  "version": "0.11.8",
+  "version": "0.11.9",
   "type": "module",
   "packageManager": "pnpm@11.22.0",
   "engines": {