agent-tempo 1.5.0 → 1.6.0

package/dist/server.js

@@ -72,7 +72,10 @@ async function main() {
         await idleServer.connect(transport);
         return;
     }
-    const config = (0, config_1.getConfig)();
+    // #676 FIX-1 — resolve config WITH sources so recruit can tell an operator-SET
+    // defaultAgent from the built-in 'claude' default. `.config` is the same Config
+    // getConfig() returns (behavior-preserving); `.sources.defaultAgent` is the origin.
+    const { config, sources } = (0, config_1.getConfigWithSources)();
     const isConductor = process.env[config_1.ENV.CONDUCTOR] === 'true';
     const requestedName = process.env[config_1.ENV.PLAYER_NAME] || '';
     // Conductors use their requested name or fall back to 'conductor'.
@@ -289,7 +292,7 @@ async function main() {
     // the same call. Adding a new tool? Add it once in `server-tools.ts`.
     (0, server_tools_1.registerAllTempoTools)(mcpServer, {
         client, config, getPlayerId, setPlayerId, handle, workflowId,
-        ownAgentType, isConductor,
+        ownAgentType, defaultAgentSource: sources.defaultAgent, isConductor,
     });
     const MAESTRO_ACK = '\n\n[IMPORTANT: This message is from a human (Maestro). Immediately cue the sender back with a brief acknowledgment and your planned next step before doing the work.]';
     // Start message poller — push messages into Claude Code via channel notifications.

package/dist/spawn.d.ts

@@ -150,6 +150,16 @@ export interface CopilotBridgeOpts {
     attachmentId?: string;
     attachmentRunId?: string;
     adapterId?: string;
+    /**
+     * #672 — set true by a TRANSIENT-CLI spawner that launches this bridge DETACHED
+     * to outlive it: BOTH the `up` conductor (commands.ts) AND the `up --lineup`
+     * copilot PLAYER loop (commands.ts applyLineupPlayersAndSchedules) — both spawn
+     * the bridge directly (no terminal), so its ppid is the short-lived CLI. When
+     * set, the bridge skips the ppid-poll that would self-kill it on the CLI's exit
+     * (stdin-EOF stays). The DAEMON-recruit path (outbox.ts) OMITS it → the bridge
+     * keeps the ppid-poll (#604 anti-leak on daemon death; ppid = persistent daemon).
+     */
+    transientSpawner?: boolean;
 }
 export interface CopilotBridgeResult {
     pid: number | undefined;

package/dist/spawn.js

@@ -518,6 +518,10 @@ function buildPiConductorSpawn(opts) {
         [config_1.ENV.TASK_QUEUE]: opts.taskQueue,
         [config_1.ENV.ENSEMBLE]: opts.ensemble,
         [config_1.ENV.CONDUCTOR]: 'true', // codebase-consistent; the Pi extension accepts '1'|'true'
+        // #672 — the Pi conductor is launched detached by the transient `up` CLI:
+        // skip the ppid-poll (no current pi process installs the watchdog, but this is
+        // propagation-safe + principled if a pi subprocess ever does; stdin-EOF stays).
+        [config_1.ENV.NO_PPID_WATCHDOG]: '1',
         [config_1.ENV.PLAYER_NAME]: opts.sessionName,
         ...(opts.devMode ? { [config_1.ENV.DEV_MODE]: '1' } : {}),
         ...(opts.anthropicApiKey ? { ANTHROPIC_API_KEY: opts.anthropicApiKey } : {}),
@@ -565,6 +569,9 @@ function spawnCopilotBridge(opts) {
                 [config_1.ENV.BRIDGE_MODE]: '', // Clear parent's bridge mode
                 [config_1.ENV.TEMPORAL_ADDRESS]: opts.temporalAddress,
                 [config_1.ENV.CONDUCTOR]: opts.isConductor ? 'true' : '',
+                // #672 — transient-CLI spawner: the detached bridge skips the ppid-poll
+                // (would self-kill on the short-lived `up` exit). Daemon recruit omits it.
+                ...(opts.transientSpawner ? { [config_1.ENV.NO_PPID_WATCHDOG]: '1' } : {}),
                 // Forward Temporal connection settings so child processes can connect
                 ...(opts.temporalNamespace ? { [config_1.ENV.TEMPORAL_NAMESPACE]: opts.temporalNamespace } : {}),
                 ...(opts.temporalApiKey ? { [config_1.ENV.TEMPORAL_API_KEY]: opts.temporalApiKey } : {}),

package/dist/tools/recruit.d.ts

@@ -1,5 +1,5 @@
 import { Client, WorkflowHandle } from '@temporalio/client';
-import { Config } from '../config';
+import { Config, ConfigSource } from '../config';
 import { AgentType } from '../types';
 import type { HostInfo } from '../types';
 import { type TempoToolDescriptor } from './descriptor';
@@ -13,7 +13,24 @@ import { type TempoToolDescriptor } from './descriptor';
 export interface RegisterRecruitToolDeps {
     listHostsFn?: (client: Client) => Promise<HostInfo[]>;
 }
-export declare function buildRecruitTool(client: Client, config: Config, getPlayerId: () => string, handle: WorkflowHandle, ownAgentType?: AgentType, deps?: RegisterRecruitToolDeps): TempoToolDescriptor;
+/**
+ * #676 FIX-1 — recruit agent precedence: explicit `argAgent` > operator-SET
+ * `configDefault` > `ownAgentType` (this player's mirror-fallback). The
+ * `defaultAgentSource` distinguishes an operator-set default (origin
+ * flag/env/config/temporal-cli) from the built-in 'claude' default (source
+ * 'default') / truly-unset ('none') — only an operator-set default wins over the
+ * mirror, so a copilot/pi conductor recruits its own kind by default. Pure +
+ * exported for unit testing.
+ */
+export declare function resolveRecruitAgent(argAgent: AgentType | undefined, configDefault: AgentType, defaultAgentSource: ConfigSource | undefined, ownAgentType: AgentType): AgentType;
+export declare function buildRecruitTool(client: Client, config: Config, getPlayerId: () => string, handle: WorkflowHandle, ownAgentType?: AgentType, 
+/**
+ * #676 FIX-1 — the SOURCE of `config.defaultAgent` (from getConfigWithSources),
+ * used to distinguish an operator-SET default from the built-in 'claude'
+ * default (source 'default'). Undefined → treated as not-operator-set →
+ * recruit falls back to `ownAgentType` (preserves the pre-FIX-1 mirror).
+ */
+defaultAgentSource?: ConfigSource, deps?: RegisterRecruitToolDeps): TempoToolDescriptor;
 /**
  * Given a host liveness+profile snapshot, validate that `targetHost` is
  * (a) known, (b) recruit-ready, and (c) advertises support for

package/dist/tools/recruit.js

@@ -33,6 +33,7 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.resolveRecruitAgent = resolveRecruitAgent;
 exports.buildRecruitTool = buildRecruitTool;
 exports.checkHostPreflight = checkHostPreflight;
 exports.nearestHostname = nearestHostname;
@@ -78,7 +79,30 @@ function hasOpencodeOnPath() {
         return false;
     }
 }
-function buildRecruitTool(client, config, getPlayerId, handle, ownAgentType = 'claude', deps = {}) {
+/**
+ * #676 FIX-1 — recruit agent precedence: explicit `argAgent` > operator-SET
+ * `configDefault` > `ownAgentType` (this player's mirror-fallback). The
+ * `defaultAgentSource` distinguishes an operator-set default (origin
+ * flag/env/config/temporal-cli) from the built-in 'claude' default (source
+ * 'default') / truly-unset ('none') — only an operator-set default wins over the
+ * mirror, so a copilot/pi conductor recruits its own kind by default. Pure +
+ * exported for unit testing.
+ */
+function resolveRecruitAgent(argAgent, configDefault, defaultAgentSource, ownAgentType) {
+    if (argAgent)
+        return argAgent;
+    const operatorSet = !!defaultAgentSource
+        && ['flag', 'env', 'config', 'temporal-cli'].includes(defaultAgentSource);
+    return operatorSet ? configDefault : ownAgentType;
+}
+function buildRecruitTool(client, config, getPlayerId, handle, ownAgentType = 'claude', 
+/**
+ * #676 FIX-1 — the SOURCE of `config.defaultAgent` (from getConfigWithSources),
+ * used to distinguish an operator-SET default from the built-in 'claude'
+ * default (source 'default'). Undefined → treated as not-operator-set →
+ * recruit falls back to `ownAgentType` (preserves the pre-FIX-1 mirror).
+ */
+defaultAgentSource, deps = {}) {
     // Lazy default — only imports utils/hosts when actually called, so the
     // MCP server's module load graph doesn't drag the whole join layer
     // into every consumer at import time.
@@ -133,7 +157,7 @@ function buildRecruitTool(client, config, getPlayerId, handle, ownAgentType = 'c
         handler: async (args) => {
             const { workDir, name, initialMessage } = args;
             const isConductor = args.conductor === true;
-            const agent = args.agent || ownAgentType;
+            const agent = resolveRecruitAgent(args.agent, config.defaultAgent, defaultAgentSource, ownAgentType);
             const model = args.model;
             const agentTypeName = args.type;
             const systemPrompt = args.systemPrompt;

package/dist/tui/index.js

@@ -134,6 +134,7 @@ function createDummyClient() {
         restore: fail,
         isConnected: async () => false,
         hasGlobalMaestro: async () => false,
+        ensembleExists: async () => false,
         getSchedules: async () => [],
         cancelSchedule: fail,
         getEnsembleChat: async () => ({ messages: [], total: 0, hasMore: false, hasConductor: false }),

package/dist/utils/parent-death-watchdog.d.ts

@@ -1 +1,13 @@
+/**
+ * Should the ppid-poll signal be installed? FALSE only when a TRANSIENT-CLI
+ * spawner set {@link ENV.NO_PPID_WATCHDOG} on a process it intentionally detached
+ * to OUTLIVE it (#672 — e.g. the short-lived `up` conductor: polling its dead pid
+ * would self-kill the conductor seconds after launch). Pure + injectable.
+ *
+ * Skipping ppid-poll is propagation-SAFE: the flag inherits down the spawn tree,
+ * but stdin-EOF (always installed) protects any child — its stdin IS this
+ * process's pipe, so it fires the instant THIS process dies. Only the ppid-poll
+ * (which keys on the SPAWNER, not the immediate parent) is the harmful signal.
+ */
+export declare function shouldInstallPpidPoll(env?: NodeJS.ProcessEnv): boolean;
 export declare function installParentDeathWatchdog(): void;

package/dist/utils/parent-death-watchdog.js

@@ -23,15 +23,40 @@
 // we falsely conclude the parent is alive. The stdin EOF path catches
 // that case immediately, so this is purely a fallback.
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.shouldInstallPpidPoll = shouldInstallPpidPoll;
 exports.installParentDeathWatchdog = installParentDeathWatchdog;
+const config_1 = require("../config");
 const log = (...args) => console.error('[agent-tempo:watchdog]', ...args);
+/**
+ * Should the ppid-poll signal be installed? FALSE only when a TRANSIENT-CLI
+ * spawner set {@link ENV.NO_PPID_WATCHDOG} on a process it intentionally detached
+ * to OUTLIVE it (#672 — e.g. the short-lived `up` conductor: polling its dead pid
+ * would self-kill the conductor seconds after launch). Pure + injectable.
+ *
+ * Skipping ppid-poll is propagation-SAFE: the flag inherits down the spawn tree,
+ * but stdin-EOF (always installed) protects any child — its stdin IS this
+ * process's pipe, so it fires the instant THIS process dies. Only the ppid-poll
+ * (which keys on the SPAWNER, not the immediate parent) is the harmful signal.
+ */
+function shouldInstallPpidPoll(env = process.env) {
+    return env[config_1.ENV.NO_PPID_WATCHDOG] !== '1';
+}
 function installParentDeathWatchdog() {
     const exit = (reason) => {
         log('parent gone (', reason, ') — exiting');
         process.exit(0);
     };
+    // stdin-EOF — UNIVERSALLY correct + ALWAYS installed: a closed stdin pipe means
+    // the IMMEDIATE parent is gone. This is what reaps a detached process's OWN
+    // children even when ppid-poll is skipped (the child's stdin is our pipe).
     process.stdin.on('end', () => exit('stdin end'));
     process.stdin.on('close', () => exit('stdin close'));
+    // ppid-poll — keys on the SPAWNER's death. Correct for a long-lived daemon
+    // spawner (#604 anti-leak), HARMFUL for a transient CLI that detached us to
+    // outlive it (#672). Skipped when the spawner marked itself transient; the
+    // Temporal lease TTL reaps a genuinely-orphaned detached process instead.
+    if (!shouldInstallPpidPoll())
+        return;
     const parentPid = process.ppid;
     if (parentPid && parentPid > 1) {
         const timer = setInterval(() => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agent-tempo",
-  "version": "1.5.0",
+  "version": "1.6.0",
   "description": "Many agents, one tempo. Durable coordination for multi-agent work via Temporal.",
   "keywords": [
     "mcp",