agent-tempo 1.0.1

package/dist/constants.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Shared constants used across the CLI, TUI, and MCP tool layers.
+ *
+ * Keep runtime-free (no imports) so this module can be pulled into workflow
+ * code without dragging Node-only modules into the sandboxed bundle.
+ */
+/**
+ * CLI flag injected into every Claude Code spawn to carry the ensemble name as a
+ * sentinel in the process's CommandLine. `src/activities/hard-terminate.ts`
+ * matches against this flag to scope `destroy --all` kills to a single ensemble
+ * (issue #180): two ensembles sharing a lineup template (identical player names)
+ * must not clobber each other's processes.
+ *
+ * The claude CLI silently accepts this flag even when remote control is inactive,
+ * and the value remains visible in Win32_Process.CommandLine / /proc/<pid>/cmdline
+ * for the kill regex to match.
+ */
+export declare const ENSEMBLE_SENTINEL_FLAG = "--remote-control-session-name-prefix";
+/**
+ * Escape the two regex metacharacters that can appear in validated player/ensemble
+ * names (which are constrained to `[A-Za-z0-9._-]+`). Safe to interpolate the
+ * result into a regex source string.
+ */
+export declare function escapeNameForRegex(s: string): string;
+/**
+ * Canonical "ensemble ready" banner shown after `up` / `conduct` completes
+ * ensemble startup but before the user has typed their first message.
+ *
+ * Used by:
+ *   - CLI (`src/cli/commands.ts`) — printed on stdout after successful setup
+ *   - `load_lineup` tool — delivered as the banner half of the combined
+ *     system message seeded on the conductor's inbox when `initialStartup=true`
+ *
+ * Intentionally duplicated verbatim across surfaces so the user sees the same
+ * phrasing on every entry point. See issue #172 for the rationale.
+ */
+export declare function ensembleReadyBanner(name: string, playerCount: number): string;
+/**
+ * Combined banner + "wait for user, then resume_ensemble first" directive
+ * baked into the conductor's `messages[]` at workflow creation on
+ * initial-startup paths (`up --lineup` / `conduct --lineup`). Issue #172.
+ *
+ * Delivered as a single `from: 'system'` message that the conductor reads
+ * alongside the lineup instructions. The directive is carried via the
+ * message text itself — the LLM reads "wait silently until the user speaks,
+ * then call `resume_ensemble` FIRST" and honors it. No workflow-level
+ * interceptor is needed; the ensemble-wide pause (`pause_ensemble`) is what
+ * actually stops other players from acting while the conductor waits.
+ */
+export declare function ensembleReadyDirective(name: string, playerCount: number): string;

package/dist/constants.js

@@ -0,0 +1,74 @@
+"use strict";
+/**
+ * Shared constants used across the CLI, TUI, and MCP tool layers.
+ *
+ * Keep runtime-free (no imports) so this module can be pulled into workflow
+ * code without dragging Node-only modules into the sandboxed bundle.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ENSEMBLE_SENTINEL_FLAG = void 0;
+exports.escapeNameForRegex = escapeNameForRegex;
+exports.ensembleReadyBanner = ensembleReadyBanner;
+exports.ensembleReadyDirective = ensembleReadyDirective;
+/**
+ * CLI flag injected into every Claude Code spawn to carry the ensemble name as a
+ * sentinel in the process's CommandLine. `src/activities/hard-terminate.ts`
+ * matches against this flag to scope `destroy --all` kills to a single ensemble
+ * (issue #180): two ensembles sharing a lineup template (identical player names)
+ * must not clobber each other's processes.
+ *
+ * The claude CLI silently accepts this flag even when remote control is inactive,
+ * and the value remains visible in Win32_Process.CommandLine / /proc/<pid>/cmdline
+ * for the kill regex to match.
+ */
+exports.ENSEMBLE_SENTINEL_FLAG = '--remote-control-session-name-prefix';
+/**
+ * Escape the two regex metacharacters that can appear in validated player/ensemble
+ * names (which are constrained to `[A-Za-z0-9._-]+`). Safe to interpolate the
+ * result into a regex source string.
+ */
+function escapeNameForRegex(s) {
+    return s.replace(/[.-]/g, (c) => `\\${c}`);
+}
+/**
+ * Canonical "ensemble ready" banner shown after `up` / `conduct` completes
+ * ensemble startup but before the user has typed their first message.
+ *
+ * Used by:
+ *   - CLI (`src/cli/commands.ts`) — printed on stdout after successful setup
+ *   - `load_lineup` tool — delivered as the banner half of the combined
+ *     system message seeded on the conductor's inbox when `initialStartup=true`
+ *
+ * Intentionally duplicated verbatim across surfaces so the user sees the same
+ * phrasing on every entry point. See issue #172 for the rationale.
+ */
+function ensembleReadyBanner(name, playerCount) {
+    const plural = playerCount === 1 ? '' : 's';
+    return `Ensemble **${name}** is ready. ${playerCount} player${plural} on standby. Describe your task to begin.`;
+}
+/**
+ * Combined banner + "wait for user, then resume_ensemble first" directive
+ * baked into the conductor's `messages[]` at workflow creation on
+ * initial-startup paths (`up --lineup` / `conduct --lineup`). Issue #172.
+ *
+ * Delivered as a single `from: 'system'` message that the conductor reads
+ * alongside the lineup instructions. The directive is carried via the
+ * message text itself — the LLM reads "wait silently until the user speaks,
+ * then call `resume_ensemble` FIRST" and honors it. No workflow-level
+ * interceptor is needed; the ensemble-wide pause (`pause_ensemble`) is what
+ * actually stops other players from acting while the conductor waits.
+ */
+function ensembleReadyDirective(name, playerCount) {
+    return [
+        ensembleReadyBanner(name, playerCount),
+        '',
+        'IMPORTANT: The ensemble is PAUSED and players are HELD. Do not take any action yet — the user has not described their task.',
+        '',
+        'When the user sends their first message, you must:',
+        '1. Call the `resume_ensemble` tool to unpause the scheduler and sessions.',
+        '2. Call the `release` tool (no args) to deliver any deferred task assignments to held players and unlock their outboxes.',
+        '3. Then decompose the user\'s task using the lineup context above, and delegate to the appropriate players.',
+        '',
+        'If the user has not spoken yet, wait silently.',
+    ].join('\n');
+}

package/dist/copilot-bridge.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Copilot Bridge — allows GitHub Copilot CLI sessions to participate
+ * as players in a claude-tempo ensemble.
+ *
+ * The bridge:
+ * 1. Spawns a Copilot CLI session via the Copilot SDK
+ * 2. Configures it with claude-tempo as an MCP server (so it gets all tools)
+ * 3. Polls the Temporal workflow for pending messages
+ * 4. Injects messages as prompts via the SDK
+ *
+ * Usage:
+ *   npx ts-node src/copilot-bridge.ts
+ *
+ * Environment variables:
+ *   CLAUDE_TEMPO_ENSEMBLE     — ensemble name (default: "default")
+ *   CLAUDE_TEMPO_PLAYER_NAME  — player ID for workflow registration (set by spawner for deterministic workflow IDs)
+ *   COPILOT_BRIDGE_NAME       — player name for set_name (optional)
+ *   COPILOT_BRIDGE_MODEL      — model to use (optional)
+ *   COPILOT_BRIDGE_SESSION_ID — deterministic session ID for resumable sessions (optional)
+ *   GITHUB_TOKEN              — GitHub auth token (optional, uses logged-in user by default)
+ */
+export {};