@rallycry/conveyor-agent 10.4.4 → 10.6.0

package/dist/index.d.ts

@@ -46,6 +46,19 @@ interface SpawnReviewData {
     prNumber?: number | null;
     checkoutRef?: string | null;
 }
+/**
+ * Server push asking the builder pod to spawn an extra interactive child on
+ * this pod: a second Claude TUI (mode "adhoc") or a raw login shell (mode
+ * "shell"), each bound to a fresh WorkspaceSession (sessionId + sessionJwt).
+ * No taskId on the wire — the child inherits the parent's CONVEYOR_TASK_ID
+ * and the server derives it from the JWT (SEC-9).
+ */
+interface SpawnTuiData {
+    sessionId: string;
+    sessionJwt: string;
+    mode: "adhoc" | "shell";
+    projectId: string;
+}
 declare class AgentConnection {
     private socket;
     private readonly config;
@@ -75,6 +88,8 @@ declare class AgentConnection {
     private earlyPullBranches;
     private spawnReviewCallback;
     private earlySpawnReviews;
+    private spawnTuiCallback;
+    private earlySpawnTuis;
     private ptyInputCallback;
     private ptyResizeCallback;
     constructor(config: AgentConnectionConfig);
@@ -132,6 +147,13 @@ declare class AgentConnection {
      * it; the review session is identified separately.
      */
     reportReviewSpawnFailure(reviewSessionId: string, error?: string): void;
+    onSpawnTui(callback: (data: SpawnTuiData) => void): void;
+    /**
+     * Report that a same-pod TUI/shell child failed to spawn (fire-and-forget).
+     * The server Ends the orphaned session — no fallback pod (unlike review).
+     * sessionId is OUR (builder) session — the SEC-9 guard runs on it.
+     */
+    reportSessionSpawnFailure(spawnedSessionId: string, error?: string): void;
     onFinalizeSnapshot(callback: () => void): void;
     onRunStartCommand(callback: () => void): void;
     /**
@@ -282,24 +304,16 @@ declare class ModeController {
     /** Resolve the initial mode based on task context */
     resolveInitialMode(context: ModeTaskContext): AgentMode;
     /**
-     * An auto task that still NEEDS PLANNING (no plan saved, pre-build status, no
-     * PR — see `taskNeedsPlanning` in @project/shared) runs the read-only plan turn
-     * first (`--permission-mode plan`): resolveInitialMode leaves it in `auto` with
-     * `_hasExitedPlanMode = false`, and once the agent finishes it calls
-     * ExitPlanMode → building. Everything else bypasses planning and builds
-     * immediately with `--dangerously-skip-permissions`:
-     *
-     * - a plan already on the card (e.g. a Planning card planned by a human/PM),
-     * - a build already underway (status past `Planning`/`Open` — releases booted
-     *   `InProgress`, pod restarts mid-build where DB `agentMode` stays `"auto"`),
-     * - a PR already open (safety net if status lags).
-     *
-     * Runtime Build-after-Discovery never reaches this gate as `auto` — the server's
-     * `resolveModeToSend` rewrites it to `"building"` for any task with a plan.
+     * Auto mode always bypasses the plan turn: resolveInitialMode calls
+     * transitionToBuilding() at boot, so the agent runs with
+     * `--dangerously-skip-permissions` from turn 1 and documents its plan into
+     * the card (via update_task_plan) as the approach firms up — non-blocking,
+     * never a gate. Use discovery mode for a plan turn that stops for human
+     * approval. Non-auto modes never bypass.
      */
-    canBypassPlanning(context: ModeTaskContext): boolean;
+    canBypassPlanning(_context: ModeTaskContext): boolean;
     /** Handle mode change from server */
-    handleModeChange(newMode: AgentMode, context?: ModeTaskContext | null): ModeAction;
+    handleModeChange(newMode: AgentMode, _context?: ModeTaskContext | null): ModeAction;
     /** Handle ExitPlanMode call from the agent */
     handleExitPlanMode(context: ModeTaskContext): ModeAction;
     /** Check if pack runner behavior should be used */
@@ -527,8 +541,8 @@ declare class SessionRunner {
     /** The build-phase nudge (In Progress, no PR). Offers BOTH escape routes so
      *  the agent never just goes idle. */
     private static readonly STUCK_PROMPT;
-    /** The planning-phase nudge (still Planning, identification/plan unfinished).
-     *  Same two-escape-route shape, aimed at finishing discovery instead of a PR. */
+    /** The pre-build nudge (still Planning/Open, identification/plan unfinished).
+     *  Same two-escape-route shape, aimed at landing the plan + continuing to build. */
     private static readonly STUCK_PROMPT_PLANNING;
     /**
      * Classify how an auto task is "stuck" after its turn ended (call sites run
@@ -539,11 +553,12 @@ declare class SessionRunner {
      *
      * - "pr":       In Progress with no open PR (build finished without shipping).
      * - "planning": still in a pre-build status (Planning/Open) without
-     *   (identified + saved plan). A fresh auto agent that finishes its plan turn
-     *   WITHOUT ExitPlanMode would otherwise idle → clean-exit → its session Ends
-     *   → the workspace is reaped "agent_gone" before a plan ever landed. Nudging
-     *   (and, on exhaustion, going dormant) keeps the session Active so the pod
-     *   is never prematurely slept.
+     *   (identified + saved plan) — e.g. the server-side InProgress bump failed
+     *   and the agent idled before documenting its plan. An agent that idles
+     *   here would otherwise clean-exit → its session Ends → the workspace is
+     *   reaped "agent_gone" before a plan ever landed. Nudging (and, on
+     *   exhaustion, going dormant) keeps the session Active so the pod is never
+     *   prematurely slept.
      */
     private autoStuckKind;
     private isAutoStuck;

package/dist/index.js

@@ -20,7 +20,7 @@ import {
   unshallowRepo,
   updateRemoteToken,
   uploadSnapshotToGcs
-} from "./chunk-VCXKVINO.js";
+} from "./chunk-5FRDOFI4.js";
 import "./chunk-7TQO4ZF4.js";
 
 // src/runner/worktree.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rallycry/conveyor-agent",
-  "version": "10.4.4",
+  "version": "10.6.0",
   "description": "Conveyor Agent Runner v10 - PTY harness for the task chat (SDK harness for audit/project-chat). Agent-as-User architecture with BaseService patterns. Works locally too.",
   "keywords": [
     "agent",