gemini-computer-use 0.4.2 → 0.4.3

package/README.md

@@ -333,10 +333,10 @@ The release also ships a single compiled installer, for machines where you would
 not clone or download anything else — `AntigravityMesh-Setup-<version>.exe`:
 
 ```powershell
-.\AntigravityMesh-Setup-0.4.2.exe            # open the visual installer
-.\AntigravityMesh-Setup-0.4.2.exe -Lang ru   # start in Russian
-.\AntigravityMesh-Setup-0.4.2.exe -SelfTest  # headless self-check, prints JSON
-.\AntigravityMesh-Setup-0.4.2.exe --version  # print the version
+.\AntigravityMesh-Setup-0.4.3.exe            # open the visual installer
+.\AntigravityMesh-Setup-0.4.3.exe -Lang ru   # start in Russian
+.\AntigravityMesh-Setup-0.4.3.exe -SelfTest  # headless self-check, prints JSON
+.\AntigravityMesh-Setup-0.4.3.exe --version  # print the version
 ```
 
 It carries the wizard, `install.ps1`, `core/` and `install.sh` inside itself, unpacks them
@@ -882,10 +882,10 @@ https://racknerd-5a24bf9.merino-carob.ts.net/sse?user=<имя-вашего-уз
 где не хочется ничего клонировать:
 
 ```powershell
-.\AntigravityMesh-Setup-0.4.2.exe            # открыть визуальный установщик
-.\AntigravityMesh-Setup-0.4.2.exe -Lang ru   # начать на русском
-.\AntigravityMesh-Setup-0.4.2.exe -SelfTest  # самопроверка без окна, печатает JSON
-.\AntigravityMesh-Setup-0.4.2.exe --version  # показать версию
+.\AntigravityMesh-Setup-0.4.3.exe            # открыть визуальный установщик
+.\AntigravityMesh-Setup-0.4.3.exe -Lang ru   # начать на русском
+.\AntigravityMesh-Setup-0.4.3.exe -SelfTest  # самопроверка без окна, печатает JSON
+.\AntigravityMesh-Setup-0.4.3.exe --version  # показать версию
 ```
 
 Внутри него лежат мастер, `install.ps1`, `core/` и `install.sh`; он распаковывает их в

package/core/version.py

@@ -20,7 +20,7 @@ pre-release is older than the release it precedes, which is what
 """
 
 #: The node version. Keep it in sync with ``package.json`` (the build enforces it).
-__version__ = "0.4.2"
+__version__ = "0.4.3"
 
 #: The repository that publishes the releases this node updates itself from.
 #: Declared here as well so a checkout says where it came from; ``package.json``

package/install.sh

@@ -876,7 +876,16 @@ if [ ! -f "$SCRIPT_DIR/core/agent.py" ]; then
     require_gateway_dns || exit 1
     BOOTSTRAP_DIR="$HOME/.gemini-computer-use"
     mkdir -p "$BOOTSTRAP_DIR/core" "$BOOTSTRAP_DIR/skills"
-    for f in core/agent.py core/server.py core/mcp_tools.py core/web_share.py core/domain.py core/vitals.py core/updater.py core/version.py core/__init__.py skills/orchestrator.md; do
+    # EVERY module the node can import, not a hand-picked few: the list below used to
+    # stop at the files that existed when it was written, and a fresh phone install
+    # then answered "the device layer (core/device.py) is missing from this checkout"
+    # while the branch was advertised - the tool was there, its module was not.
+    # tests/test_installer_bootstrap.py fails when a core module is missing here.
+    for f in core/__init__.py core/agent.py core/agent_harness.py core/code_cache.py \
+             core/device.py core/domain.py core/hooks.py core/mcp_tools.py core/policies.py \
+             core/schemas.py core/server.py core/subagents.py core/termux.py core/triggers.py \
+             core/updater.py core/version.py core/vitals.py core/web_share.py \
+             skills/orchestrator.md; do
         bootstrap_tmp="$BOOTSTRAP_DIR/${f}.part"
         if curl -fsSL "https://${GATEWAY}/${f}" -o "$bootstrap_tmp" 2>/dev/null \
             || curl -fsSL "https://raw.githubusercontent.com/LevRa7/Computer-use-for-Gemini-App-Web/main/${f}" -o "$bootstrap_tmp" 2>/dev/null; then
@@ -1188,12 +1197,18 @@ exec "$run_script"
 SV_EOF
         chmod 755 "$svdir/$name/run"
         # runit refuses to supervise without log/run, and svlogger is a script, not
-        # a program: the documented setup is a symlink to it. A $PREFIX that refuses
-        # symlinks (a FUSE-backed home, an unusual mount) gets an equivalent script
-        # instead, so the node is never left unsupervised for want of a link.
-        if ! ln -sf "$TERMUX_PREFIX/share/termux-services/svlogger" "$svdir/$name/log/run" 2>/dev/null; then
-            printf '#!%s/bin/sh\nexec "%s/share/termux-services/svlogger"\n' \
-                "$TERMUX_PREFIX" "$TERMUX_PREFIX" > "$svdir/$name/log/run"
+        # a program: the documented setup is a symlink to it. Two cases need the
+        # equivalent script instead, because a link that cannot resolve is worse
+        # than no link at all: a $PREFIX that refuses symlinks (a FUSE-backed home,
+        # an unusual mount), and a phone where sv and runsvdir exist but
+        # termux-services never installed its svlogger - 'ln -sf' happily creates a
+        # dangling log/run against a missing target, and runit then has a logger it
+        # cannot execute.
+        local svlogger="$TERMUX_PREFIX/share/termux-services/svlogger"
+        if [ ! -e "$svlogger" ] \
+            || ! ln -sf "$svlogger" "$svdir/$name/log/run" 2>/dev/null; then
+            printf '#!%s/bin/sh\nexec "%s"\n' \
+                "$TERMUX_PREFIX" "$svlogger" > "$svdir/$name/log/run"
             chmod 755 "$svdir/$name/log/run"
         fi
         export SVDIR="$svdir"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gemini-computer-use",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "Turn your PC, Laptop, Server or Android phone into an autonomous execution node for Google Gemini via native MCP: 26 tools, write/edit/search, background jobs, public file and page sharing, secure reverse tunnel, self-update, and a device branch (battery, signal, sensors, camera, microphone, notifications) for phones and laptops.",
   "main": "bin/cli.js",
   "bin": {