agent-tempo 1.0.1

package/packaging/systemd/agent-tempo.service

@@ -0,0 +1,32 @@
+# agent-tempo daemon — systemd --user unit
+#
+# Installed to ~/.config/systemd/user/agent-tempo.service by
+# `agent-tempo daemon install`. Enable with:
+#
+#   systemctl --user daemon-reload
+#   systemctl --user enable --now agent-tempo
+#
+# User-level only (no sudo). The daemon process claims
+# ~/.agent-tempo/daemon.pid; systemd restarts on crash.
+#
+# Environment variables (Temporal connection overrides) can be added via
+# EnvironmentFile or Environment= lines here — by default the daemon reads
+# ~/.agent-tempo/config.json or falls back to temporal CLI config.
+
+[Unit]
+Description=agent-tempo daemon (Temporal workers + reconcile loop)
+After=network-online.target
+Wants=network-online.target
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/env agent-tempo daemon start --foreground
+ExecStop=/usr/bin/env agent-tempo daemon stop
+Restart=on-failure
+RestartSec=10s
+# Prevent runaway restart loops from a broken config file.
+StartLimitIntervalSec=120
+StartLimitBurst=5
+
+[Install]
+WantedBy=default.target

package/packaging/windows/install-task.ps1

@@ -0,0 +1,71 @@
+# agent-tempo daemon — Windows Task Scheduler install script
+#
+# Registers a per-user scheduled task that starts the daemon at logon and
+# keeps it running. User-level only (current user scope; does not require
+# Administrator).
+#
+# Usage:
+#   powershell -File install-task.ps1             # install (idempotent)
+#   powershell -File install-task.ps1 -Uninstall  # remove
+
+param(
+  [switch]$Uninstall
+)
+
+$TaskName = 'agent-tempo-daemon'
+$TaskDescription = 'agent-tempo daemon — Temporal workers + reconcile loop'
+
+if ($Uninstall) {
+  $existing = Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue
+  if ($existing) {
+    Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
+    Write-Output "Unregistered scheduled task: $TaskName"
+  } else {
+    Write-Output "No scheduled task named $TaskName was registered."
+  }
+  exit 0
+}
+
+# Resolve agent-tempo.cmd (the npm-installed shim on PATH).
+$claudeTempo = (Get-Command agent-tempo -ErrorAction SilentlyContinue).Source
+if (-not $claudeTempo) {
+  Write-Error "agent-tempo not found on PATH. Install it first (`npm i -g agent-tempo`)."
+  exit 1
+}
+
+# Replace any prior registration so re-runs are idempotent.
+$existing = Get-ScheduledTask -TaskName $TaskName -ErrorAction SilentlyContinue
+if ($existing) {
+  Unregister-ScheduledTask -TaskName $TaskName -Confirm:$false
+}
+
+$action = New-ScheduledTaskAction `
+  -Execute $claudeTempo `
+  -Argument 'daemon start --foreground'
+
+$trigger = New-ScheduledTaskTrigger -AtLogOn -User $env:USERNAME
+
+$settings = New-ScheduledTaskSettingsSet `
+  -AllowStartIfOnBatteries `
+  -DontStopIfGoingOnBatteries `
+  -StartWhenAvailable `
+  -RestartCount 3 `
+  -RestartInterval (New-TimeSpan -Minutes 1)
+
+$principal = New-ScheduledTaskPrincipal `
+  -UserId $env:USERNAME `
+  -LogonType Interactive `
+  -RunLevel Limited
+
+Register-ScheduledTask `
+  -TaskName $TaskName `
+  -Description $TaskDescription `
+  -Action $action `
+  -Trigger $trigger `
+  -Settings $settings `
+  -Principal $principal | Out-Null
+
+Write-Output "Registered scheduled task: $TaskName"
+Write-Output "  Exec:  $claudeTempo daemon start --foreground"
+Write-Output "  User:  $env:USERNAME (Interactive, limited)"
+Write-Output "  Trigger: at logon"

package/scenarios/conductor-recruit-mock.yaml

@@ -0,0 +1,33 @@
+name: conductor-recruit-mock
+description: |
+  Stand-alone scenario for a conductor mock that recruits a sub-player on
+  demand. When the conductor receives a cue starting with "recruit ", it
+  fires a `recruit` outbox entry for a new mock player named after the
+  remainder of the cue, then reports completion. Useful for validating the
+  recruit → spawn → claim → first-heartbeat path end-to-end without a
+  real LLM in the loop.
+
+  Drive with: `agent-tempo --dev cue conductor "recruit alice"`.
+
+defaultDelayMs: 800
+
+rules:
+  - when: "recruit "
+    do:
+      - report:
+          type: "update"
+          text: "received recruit request — issuing recruit outbox entry"
+      - recruit:
+          name: alice
+          workDir: "/tmp/dev-scratch"
+          agent: mock
+      - delayMs: 2000
+      - cue:
+          to: "@sender"
+          message: "recruit submitted; alice should land on the dashboard within ~30s"
+
+  - when: "*"
+    do:
+      - cue:
+          to: "@sender"
+          message: "[conductor mock] try: 'recruit <name>'"

package/scenarios/echo-roundtrip.yaml

@@ -0,0 +1,15 @@
+name: echo-roundtrip
+description: |
+  Smallest possible scripted scenario — every inbound message comes back
+  as `[ECHO] <text>` to the sender. Equivalent to `mockMode: echo` but
+  expressed declaratively so the validation harness can pin it as a
+  baseline regression check.
+
+defaultDelayMs: 250
+
+rules:
+  - when: "*"
+    do:
+      - cue:
+          to: "@sender"
+          message: "[ECHO] $message"

package/scenarios/multi-player-handoff.yaml

@@ -0,0 +1,38 @@
+name: multi-player-handoff
+description: |
+  Three-player handoff exercising cross-player coordination depth without a
+  real LLM. When `alice` receives a "ship feature <topic>" cue, she splits the
+  task: cues `bob` for implementation, `carol` for review, then reports an
+  "in flight" update to the conductor. After a 2 s simulated thinking window
+  she fires a "shipped" report. The dashboard should render two outbox
+  branches under alice's audit trail and inbound cues on both bob's and
+  carol's rosters.
+
+  Pair this with a `tempo-mock-jam`-shaped lineup (3 mock players named
+  alice / bob / carol). Drive with: `agent-tempo --dev cue alice "ship
+  feature caching"`.
+
+defaultDelayMs: 500
+
+rules:
+  - when: "ship feature"
+    do:
+      - cue:
+          to: "bob"
+          message: "alice asks: please scaffold $message"
+      - cue:
+          to: "carol"
+          message: "alice asks: prep review for $message once bob lands"
+      - report:
+          type: "update"
+          text: "split '$message' into bob (impl) + carol (review); both notified"
+      - delayMs: 2000
+      - report:
+          type: "result"
+          text: "$message handoff complete — bob + carol coordinating downstream"
+
+  - when: "*"
+    do:
+      - cue:
+          to: "@sender"
+          message: "[alice mock] try: 'ship feature <topic>'"

package/scenarios/recruit-cascade.yaml

@@ -0,0 +1,38 @@
+name: recruit-cascade
+description: |
+  Stress-tests orchestration depth by chaining recruits. When this conductor
+  mock receives a "cascade <depth> <name>" cue, it issues a `recruit` outbox
+  entry and (after a brief simulated thinking window) reports completion.
+  Drive recursively from the dashboard or via `cue` to exercise the full
+  recruit → spawn → claim → first-heartbeat cascade across multiple players.
+
+  Drive with: `agent-tempo --dev cue conductor "cascade 3 worker"`.
+  Each "worker" mock you recruit can re-cascade if pointed at this scenario,
+  letting validation harnesses observe the maestro's per-ensemble player
+  count tick up under load.
+
+defaultDelayMs: 600
+
+rules:
+  - when: "cascade "
+    do:
+      - report:
+          type: "update"
+          text: "received cascade request — issuing recruit"
+      - recruit:
+          name: cascade-worker
+          workDir: "/tmp/dev-scratch"
+          agent: mock
+      - delayMs: 1500
+      - cue:
+          to: "@sender"
+          message: "cascade recruit submitted; new worker should land within ~30s"
+      - report:
+          type: "result"
+          text: "cascade level complete; downstream workers should now be visible on the roster"
+
+  - when: "*"
+    do:
+      - cue:
+          to: "@sender"
+          message: "[cascade conductor] try: 'cascade <depth> <name>'"

package/scenarios/two-player-conversation.yaml

@@ -0,0 +1,33 @@
+name: two-player-conversation
+description: |
+  Exercises cross-player coordination through the mock adapter. When alice
+  receives a "discuss <topic>" cue, she fires a follow-up cue at "bob"
+  asking for input, then reports an update to the conductor. The dashboard
+  should render the `attached → processing → attached` transition for
+  alice, the inbound cue on bob's roster, and the outbox audit on the
+  conductor's report stream — all without a real LLM call.
+
+  Pair this scenario with another player named "bob" (any mode — `echo`
+  works fine). Drive with: `agent-tempo --dev cue alice "discuss caching"`.
+
+defaultDelayMs: 600
+
+rules:
+  - when: "discuss"
+    do:
+      - cue:
+          to: "bob"
+          message: "alice asks: do we have an opinion on $message?"
+      - report:
+          type: "update"
+          text: "delegated discussion of '$message' to bob"
+      - delayMs: 1500
+      - report:
+          type: "result"
+          text: "discussion thread launched; bob will respond when ready"
+
+  - when: "*"
+    do:
+      - cue:
+          to: "@sender"
+          message: "[no rule matched] try: 'discuss <topic>'"