@runuai/host 0.9.95 → 0.9.97

package/lib/browser-testing.ts

@@ -933,7 +933,7 @@ console.log(
  * under tiny restart loops — x11vnc EXITS whenever the X server it watches
  * isn't up yet (the race that killed the first live run), and the loops
  * also reattach after the display owner changes. Safe to run repeatedly:
- * every piece is pgrep-guarded, including the loops themselves.
+ * every piece is guarded by the X lockfile or a pidfile, loops included.
  */
 /**
  * The viewer daemons, one docker-exec each (the single-line nohup shape is
@@ -950,6 +950,22 @@ console.log(
  * proxy only SOMETIMES and reconnects the rest (live 2026-09-02). So the
  * start branch — reached only when the tracked loop is already dead — first
  * reaps anything still holding the port, guaranteeing exactly one listener.
+ *
+ * That reap MUST be `pkill -A` (--ignore-ancestors). The step runs as
+ * `sh -c "<step>"`, so the launching shell's own cmdline carries the launch
+ * line and matches the reap pattern: plain `pkill -f` SIGTERMed that shell
+ * before it reached the nohup, and neither daemon ever started — host
+ * 0.9.94–0.9.96, every Linux runtime (the pgrep self-match above, wearing a
+ * kill; reproduced in the uai-linux VM: step exit 143, no pidfile). Both
+ * shipped images run procps-ng 4.0.2 (Debian bookworm), which has -A; an
+ * older procps rejects the flag with a usage error and reaps nothing, which
+ * merely restores the pre-reap behaviour and never the self-kill.
+ * `-A` protects the launching chain only: the apt worker below inlines
+ * these steps into `su -c` / `nohup sh -c` wrappers whose argv also
+ * matches, and a per-session reap that lands inside that worker's ~1 s
+ * viewer window can kill its node-uid shell. That only costs the worker
+ * its done-marker (set -e), so it re-runs on the next ensure and finds the
+ * pidfiles alive — self-healing, and no worse than the pre-reap world.
  */
 const VIEWER_STEPS: string[] = [
   // Xvfb — one-shot; the X lockfile is the truth (also set when an agent
@@ -958,9 +974,9 @@ const VIEWER_STEPS: string[] = [
   `[ -x /usr/bin/Xvfb ] || exit 0; [ -e ${X_LOCK} ] || /usr/bin/nohup /usr/bin/${XVFB_CMD} >>/tmp/uai-xvfb.log 2>&1 &`,
   // x11vnc under a restart loop (it exits whenever the X server isn't up
   // yet). Pidfile-guarded.
-  `[ -x /usr/bin/x11vnc ] || exit 0; [ -f /tmp/uai-x11vnc.pid ] && /usr/bin/kill -0 "$(/usr/bin/cat /tmp/uai-x11vnc.pid)" 2>/dev/null && exit 0; /usr/bin/pkill -f 'x11vnc -display' 2>/dev/null; /usr/bin/nohup /bin/sh -c 'echo $$ > /tmp/uai-x11vnc.pid; while true; do /usr/bin/x11vnc -display ${SERVER_DISPLAY} -forever -shared -nopw -quiet >>/tmp/uai-x11vnc.log 2>&1; /bin/sleep 2; done' >/dev/null 2>&1 &`,
+  `[ -x /usr/bin/x11vnc ] || exit 0; [ -f /tmp/uai-x11vnc.pid ] && /usr/bin/kill -0 "$(/usr/bin/cat /tmp/uai-x11vnc.pid)" 2>/dev/null && exit 0; /usr/bin/pkill -A -f 'x11vnc -display' 2>/dev/null; /usr/bin/nohup /bin/sh -c 'echo $$ > /tmp/uai-x11vnc.pid; while true; do /usr/bin/x11vnc -display ${SERVER_DISPLAY} -forever -shared -nopw -quiet >>/tmp/uai-x11vnc.log 2>&1; /bin/sleep 2; done' >/dev/null 2>&1 &`,
   // websockify/noVNC under the same pattern.
-  `[ -x /usr/bin/websockify ] || exit 0; [ -f /tmp/uai-novnc.pid ] && /usr/bin/kill -0 "$(/usr/bin/cat /tmp/uai-novnc.pid)" 2>/dev/null && exit 0; /usr/bin/pkill -f 'websockify.*6080' 2>/dev/null; /usr/bin/nohup /bin/sh -c 'echo $$ > /tmp/uai-novnc.pid; while true; do /usr/bin/websockify --web=/usr/share/novnc 0.0.0.0:6080 localhost:5900 >>/tmp/uai-websockify.log 2>&1; /bin/sleep 2; done' >/dev/null 2>&1 &`,
+  `[ -x /usr/bin/websockify ] || exit 0; [ -f /tmp/uai-novnc.pid ] && /usr/bin/kill -0 "$(/usr/bin/cat /tmp/uai-novnc.pid)" 2>/dev/null && exit 0; /usr/bin/pkill -A -f 'websockify.*6080' 2>/dev/null; /usr/bin/nohup /bin/sh -c 'echo $$ > /tmp/uai-novnc.pid; while true; do /usr/bin/websockify --web=/usr/share/novnc 0.0.0.0:6080 localhost:5900 >>/tmp/uai-websockify.log 2>&1; /bin/sleep 2; done' >/dev/null 2>&1 &`,
 ];
 
 const DEFAULT_NODE_BIN =
@@ -1085,13 +1101,20 @@ export async function setupBrowserTesting(
     // costs ~0.5s once the build is present.
     const installed = environment
       ? await (async () => {
-          await environment.exec({
+          const chown = await environment.exec({
             argv: ["/usr/bin/chown", "node:node", "/opt/pw-browsers"],
             user: "root",
             env: authorityEnv,
             timeoutMs: 5_000,
             maxOutputBytes: 64 * 1024,
           });
+          if (chown.exitCode !== 0) {
+            // Same non-fatal stance as the CLI path below.
+            console.warn(
+              `[browser] task ${taskId}: chown /opt/pw-browsers failed (status ${chown.exitCode}); ` +
+                `continuing with the prewarm. ${Buffer.from(chown.stderr).toString("utf8").slice(0, 200)}`,
+            );
+          }
           return environment.exec({
             argv: ["sh", "-lc", PREWARM_CMD],
             cwd: "/workspace",
@@ -1113,7 +1136,16 @@ export async function setupBrowserTesting(
           ],
           { timeoutMs: 5_000 },
         ).then(async (chown) => {
-          if (chown.status !== 0) return chown;
+          if (chown.status !== 0) {
+            // Not fatal. On apple-container /opt/pw-browsers is a host-wide
+            // virtiofs volume whose ownership the guest cannot change (EPERM)
+            // although it is already node-owned inside the container; the
+            // prewarm below is the real test of writability, so let it decide.
+            console.warn(
+              `[browser] task ${taskId}: chown /opt/pw-browsers failed (status ${chown.status}); ` +
+                `continuing with the prewarm. ${chown.stderr.slice(0, 200)}`,
+            );
+          }
           return taskContainerCli(
             [
               "exec",

package/lib/orchestrator.ts

@@ -3695,6 +3695,31 @@ export function buildSystemPreamble(
         "someone only to bring them in or hand work off. (2) You may occasionally",
         "receive a `[channel check-in]` asking you to catch up on the channel.",
         ];
+  // Reply cards: agents may offer the human a bounded, clickable answer. Only
+  // the human-facing agents get this (the crew talks to the Secretary, not
+  // people). Engine-agnostic — it is a chat markdown convention.
+  const replyCardBrief =
+    isSecretaryCrew
+      ? []
+      : [
+          "When you need a SHORT, bounded answer from the human — pick one of a",
+          "few options, or a yes/no — you may offer a reply card instead of a",
+          "plain question. Write a fenced block the app turns into buttons:",
+          "",
+          "```uai-ask",
+          "type: choice",
+          "question: Which chain should I target first?",
+          "options:",
+          "  - Robinhood",
+          "  - Base",
+          "  - Skip for now",
+          "```",
+          "",
+          "Use `type: confirm` (no options) for a yes/no. The human's click",
+          "arrives as their normal reply. Offer a card only when the answer",
+          "really is a small fixed set — for anything open-ended, just ask in",
+          "prose. At most one card per message, and never for the crew.",
+        ];
   const comms = [
     "## uai task channel",
     "",
@@ -3718,6 +3743,7 @@ export function buildSystemPreamble(
     ...(sessionInboxBrief.length > 0 ? [""] : []),
     ...secretaryRoleBrief,
     ...channelConventionsBrief,
+    ...(replyCardBrief.length > 0 ? ["", ...replyCardBrief] : []),
     ...checkInTranscriptBrief,
     "",
     ...handoffBrief,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@runuai/host",
-  "version": "0.9.95",
+  "version": "0.9.97",
   "description": "Uai host — runs ephemeral AI tasks in containers on a machine you control.",
   "license": "MIT",
   "author": "Uai Tech <team@runuai.com>",