feat(node): ship managed environment startup and USB recovery

AGENTS.md

@@ -62,6 +62,24 @@ and the boundary between Mission Core and vendor-specific integration code.
 - Synthetic or explicitly redacted fixtures may be committed under
   `tests/fixtures/`.
 
+## Onboard environment ownership — owner requirement, 2026-09-24
+
+- Every onboard OS change belongs to the shipped, versioned installer or the
+  application's environment/device preparation workflow from the first test.
+  The operator installs the build and configures it in the application; never
+  require hand-written service files, USB rules, permission fixes or commands.
+- This applies to all Node features, including GUI/service autostart and USB
+  recovery, not just individual camera drivers. Read-only SSH inspection and
+  bounded artifact-owned build staging remain allowed.
+- Detect the distribution, architecture and required capabilities. Maintain
+  explicit supported environment profiles; do not claim arbitrary Linux
+  compatibility from a qualified Ubuntu build. Preserve foreign configuration,
+  report unsupported features, make preparation repeatable, and ship rollback.
+- Do not add USB administration controls or port resets to inventory refresh.
+  Automatic startup recovery may retry terminal enumeration failures only;
+  preserve enumerated devices and active companion ports. Device identity and
+  assignments must survive changes of USB port and tty number.
+
 ## Insta360 and clean-host installation — owner requirement, 2026-09-08
 
 - The current X4 starting point is USB enumeration only. SDK installation,