Fix PC-assisted Robot Hardware installation

docs/project-lifecycle.md

@@ -157,7 +157,13 @@ manageable.
 
 A Runtime-only managed device can add the organized Hardware checkout in place
 from **Attach robot → Install Hardware package**. This preserves the Runtime
-pairing and does not require deleting the device.
+pairing and does not require deleting the device. For a PC-assisted device, the
+editor downloads the pinned Robot Hardware source and Linux dependencies,
+verifies and caches them, then transfers the bundle over SSH. Hardware uses the
+stack's managed Python 3.11 and does not require the device to contact GitHub or
+PyPI. A recognized partial Hardware clone from an interrupted earlier install
+is cleaned before the verified bundle is applied; unrelated directories remain
+untouched.
 
 **Delete device** stops the selected Runtime and its deployments, removes its
 Runtime checkout, synchronized workflow packages, managed Linux Python,

editor-server/device-hardware-requirements.in

@@ -0,0 +1,11 @@
+# Linux Python 3.11 dependencies staged by the editor for managed Robot Hardware.
+# Keep this aligned with the blacknode-robot pyproject and setup script.
+feetech-servo-sdk>=1.0
+# Autobahn 26.x does not publish a CPython 3.11 manylinux2014 aarch64 wheel.
+autobahn>=24.4.2,<=25.12.1
+cbor2<=5.9.0
+pyserial>=3.5
+roslibpy>=1.5
+setuptools>=68
+smbus2>=0.5
+wheel

editor-server/device-runtime-sources.lock.json

@@ -8,5 +8,9 @@
   "core": {
     "repository": "temiroff/Blacknode",
     "commit": "62f812412561f9ab59dde67d749ff291087222fb"
+  },
+  "hardware": {
+    "repository": "temiroff/blacknode-robot",
+    "commit": "0311491e73e3b71fe0d2d6c18d64588dd38947b0"
   }
 }