chore: bump @simular-ai/simulang-js from 6.0.0 to 12.1.0

[dependabot]

Bumps @simular-ai/simulang-js from 6.0.0 to 12.1.0.

Changelog

Sourced from @​simular-ai/simulang-js's changelog.

[12.1.0] - 2026-08-26

Added

• clickablePoint(allowDescendants?) on AccessibilityNode, AccessibilityTree (by ref id), and AccessibilitySnapshot (by index) — a screen point [x, y] where a pointer click actually lands on the element, verified by hit-testing (Windows: UIA GetClickablePoint; macOS/Linux: UIA's probe ladder — center, edge midpoints, sparse grid, diagonal — checked against the platform hit test; Android: bounds center, unverified). allowDescendants (default false) also accepts a point landing on a node inside the element; a point landing on an ancestor never counts. Throws with the reason (naming the covering element when known) when no verified point exists — obscured, offscreen, or zero-sized — instead of guessing a center that would click something else.

[12.0.3] - 2026-08-25

Added

• showMenu on AccessibilityNode, AccessibilityTree (by ref id), and AccessibilitySnapshot (by index) — opens an element's context menu semantically (the right-click equivalent) without synthesizing pointer input, so it works on background/obscured windows; note the opened menu itself typically appears topmost/focused. Maps to IUIAutomationElement3::ShowContextMenu on Windows, AXShowMenu on macOS, the toolkit's advertised show-menu action on Linux, and a long-press on Android. Throws when the element doesn't support it, so callers can fall back to a coordinate right-click at the element's bounds.

[12.0.2] - 2026-08-25

[12.0.2-rc1] - 2026-08-19

Added

• Window.normal() — put the window on-screen at its restored size, neither minimized nor maximized. No-op when already normal. Replaces the old restore() / unmaximize() pair with one named end-state (ShowWindow(SW_SHOWNORMAL) on Windows; clear AXMinimized then AXFullScreen on macOS; remove the EWMH maximized atoms and map the window on Linux).
• Instance.root() — root accessibility node of this application (macOS: the app element including the menu bar; Windows/Linux: the process accessibility root; Android: the current screen root, instance must be in the foreground). This is the replacement for the removed Machine.processRoot(pid). It was listed in the 12.0.0-rc1 notes but missing from the bindings until now.

Changed

• Breaking: Window.restore() and Window.unmaximize() are removed in favor of Window.normal(). The old pair were inverses of minimize / maximize that left the other state alone (restore() never un-maximized; unmaximize() never un-minimized). normal() always ends in the on-screen, neither-minimized-nor-maximized state. Replace both call sites with normal().
• Breaking: Machine.windowsForPid(pid) is removed. Use instance.windows() — windows belong to an instance, and on Windows an instance is app-scoped (it stores no PID). If you only have a pid, filter machine.windows() by window.pid (this also replaces the machine.windowsForPid(pid)[0] migration the 12.0.0 notes suggested for AccessibilityTree.fromPid).
• Breaking: Machine.processRoot(pid) is removed. Use instance.root() or AccessibilityTree.fromInstance(instance) — accessibility trees are addressed by instance, not by process id (Android never supported process-scoped trees).
• App.open(..., waitForLoadComplete) waits until the instance has a window (or the platform reports launch finished), up to twenty seconds, instead of a short fixed delay. Desktop timeouts are logged; Android treats them as errors. Pass false for apps that never show a window. Existing windows of an already-running app satisfy the wait immediately — this does not wait for a window or tab the call may add.
• Window.minimize() / Window.maximize() are named end-states (no-op when already in that state). maximize() shows a minimized window maximized; on macOS minimize() leaves full screen first.
• Instance.pid is diagnostic only. On Windows the instance is app-scoped and the PID is resolved lazily from a window or matching process (may be null while the app has no window yet). On Linux it follows a single-instance handoff to the surviving process.

[12.0.1-rc1] - 2026-08-06

Added

• macOS Window background input methods (backgroundMoveMouse, backgroundButton, backgroundClick, backgroundScroll, backgroundText, backgroundKey, backgroundKeyUnicode, backgroundKeyOther, backgroundRaw) send input to that specific window without moving the system cursor or bringing its application to the foreground. The methods throw as unsupported on other platforms.

[12.0.0-rc2] - 2026-07-30

Added

• Machine.systemRoot() — root accessibility node spanning everything currently accessible: on desktops the system-wide root (its children are the running applications), on Android a snapshot of everything currently shown on screen (which can span the foreground app, the system bars, and a split-screen neighbor).
• AndroidExtras.swipe(fromX, fromY, toX, toY, durationMs) (via machine.asAndroid()) — touch swipe between two points in absolute device pixels, holding the finger down for durationMs. The cross-platform mouse lowering always synthesizes a fixed 200ms drag, so gesture timing (a brief fling with momentum vs a slow deliberate drag) was previously inexpressible.

Changed

• Breaking: Machine.root() is renamed to Machine.focusedRoot() and Machine.rootForPid(pid) to Machine.processRoot(pid), matching the underlying simulang-rs API and disambiguating from the new Machine.systemRoot(). Same signatures and behavior; update call sites.
• Breaking: Screenshot.toGlobalDesktopCoordinates(...) is renamed to Screenshot.toMachineCoordinates(...), matching the underlying simulang-rs API. The result is in the owning machine's canonical coordinate space — on an Android machine that is the device screen, not a "global desktop", so the old name was wrong there. Same signature and behavior; update call sites.

[12.0.0-rc1] - 2026-07-22

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​simular-ai/simulang-js since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[dependabot]

Superseded by #22.