delegation-layer 0.2.0 → 0.3.1

package/README.md

@@ -8,6 +8,7 @@ and retrieving results with evidence.
 · [Example](#ask-naturally)
 · [Providers](https://github.com/hishamkaram/delegation-layer/blob/main/docs/providers.md)
 · [Teams](https://github.com/hishamkaram/delegation-layer/blob/main/docs/teams.md)
+· [Start recurring tasks](docs/getting-started.md#recurring-tasks)
 · [Docs](https://github.com/hishamkaram/delegation-layer/blob/main/docs/README.md)
 
 <p align="center">
@@ -55,6 +56,12 @@ for activation and limits.
 For a manual CLI task, use the packaged
 [read-only example](skills/agent-integration/examples/read-only-task.md).
 
+For recurring work, follow the [scheduler walkthrough](docs/getting-started.md#recurring-tasks)
+to start `delegate scheduler serve` in your own terminal or tmux pane, even
+before saving a definition. Agents and manual commands share the CLI's default
+state across projects. The walkthrough covers saving a schedule, inspecting its
+first result and stopping or restarting the host.
+
 ## Help and contributing
 
 See [troubleshooting](https://github.com/hishamkaram/delegation-layer/blob/main/docs/troubleshooting.md),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "delegation-layer",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Multi-provider AI agent delegation CLI and Agent Skill for running bounded coding tasks across provider CLIs.",
   "keywords": [
     "ai-agents",

package/plugins/delegation-layer/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "delegation-layer",
   "displayName": "Delegation Layer",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Consult external AI harnesses and CCR-configured models for reviews, research, implementation, and debate through the resumable Delegate CLI.",
   "author": {
     "name": "Hesham Karam",

package/plugins/delegation-layer/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "delegation-layer",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Consult external AI harnesses and CCR-configured models for reviews, research, implementation, and debate through the resumable Delegate CLI.",
   "author": {
     "name": "Hesham Karam",

package/plugins/delegation-layer/skills/agent-integration/SKILL.md

@@ -87,11 +87,16 @@ Use a supplied brief or write the worker's bounded assignment and acceptance
 criteria to a regular file. Do not copy the orchestration request or ask workers
 to recruit others unless recursive delegation was requested.
 
-Keep the state root outside provider-writable workspaces, provider runtime
-directories, and temporary trees they may write. For every task command pass
-`--root "${DELEGATE_ROOT:-$HOME/delegation-state}"` directly in that shell
-invocation. If the user explicitly requests another root, use that exact path
-consistently. Task IDs separate tasks; do not invent per-task roots.
+For ordinary task, schedule, observation, interaction, and continuation commands,
+omit `--root`; the CLI owns default-root resolution for the user's configuration
+context, independently of the project cwd. Do not assemble a default path, use a
+sample path or shell fallback, or treat ambient `DELEGATE_ROOT` as authority.
+Only pass `--root` when the user explicitly supplies a root or existing work has
+an already recorded custom or historical root; preserve that exact path for
+every command concerning that work. Never search other roots for an old task.
+Task IDs separate tasks; do not invent per-task or per-project roots. The state
+root must remain outside provider-writable workspaces, provider runtime
+directories, and temporary trees they may write.
 
 Prepare paths and dispatch in one tool invocation; shell variables may not
 persist between calls. Use saved absolute paths in later calls. Do not use
@@ -125,13 +130,16 @@ original command and intent.
 ### 5. Observe and collect
 
 Follow [observation decisions](references/result-handling.md#observe-and-collect)
-with the same root and created task ID:
+with the created task ID, using the CLI default for ordinary work:
 
 ```sh
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" status TASK_ID --json
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" collect TASK_ID --watch 5s --json
+delegate status TASK_ID --json
+delegate collect TASK_ID --watch 5s --json
 ```
 
+For work bound to an explicit custom or historical root, add its exact
+`--root` to both commands under the [root rule](#3-prepare-separate-paths-and-a-finite-brief).
+
 Apply the owning decision order before waiting: terminal outcomes and concrete
 errors, cancellation/timeout/interruption, interaction, then pending
 observation. Keep collection in the foreground until completion or a reported

package/plugins/delegation-layer/skills/agent-integration/evals/evals.json

@@ -10,7 +10,7 @@
     {
       "name": "normal-dispatch",
       "prompt": "Run one bounded task through the available agent provider.",
-      "expected": ["dispatch --auto", "--json", "save task_id", "status", "collect"]
+      "expected": ["dispatch --auto", "omit --root on ordinary commands", "--json", "save task_id", "status", "collect"]
     },
     {
       "name": "model-discovery-when-needed",
@@ -68,9 +68,29 @@
       "expected": ["use status with returned task_id", "read saved dispatch response if needed", "do not dispatch again to print an exit code", "exactly one admitted task for the assignment"]
     },
     {
-      "name": "supplied-root-across-shell-calls",
+      "name": "ambient-root-ignored-across-shell-calls",
       "prompt": "DELEGATE_ROOT is already set. Consult a separate external agent and answer its questions; each shell tool call starts a new shell.",
-      "expected": ["use supplied DELEGATE_ROOT on dispatch, status, collect, reply, steer, and continue", "resolve the same root in each shell call", "no invented task-specific root"]
+      "expected": ["omit --root on dispatch, status, collect, reply, steer, and continue", "ambient DELEGATE_ROOT has no root-selection authority", "CLI resolves its default in the same user/configuration context", "no assembled default, shell fallback, sample path, or per-task root"]
+    },
+    {
+      "name": "ordinary-root-from-another-project",
+      "prompt": "DELEGATE_ROOT is unset. An admitted task was dispatched without --root in project A. Observe and continue it from project B in the same user/configuration context.",
+      "expected": ["omit --root on status, collect, and continue", "use the recorded task ID", "CLI default is independent of project cwd", "no path guessed from project A or B", "no search across roots"]
+    },
+    {
+      "name": "explicit-root-across-shell-calls",
+      "prompt": "For this isolated test, I explicitly choose the state root /state/custom with spaces. Consult a separate external agent and answer its questions; each shell tool call starts a new shell.",
+      "expected": ["pass --root with the exact single argument /state/custom with spaces on dispatch, status, collect, reply, steer, and continue", "quote the root in shell commands", "save and reassign absolute brief and response paths in each needed shell invocation", "no ambient variable or fallback overrides the explicit choice"]
+    },
+    {
+      "name": "historical-root-continuation",
+      "prompt": "An eligible predecessor task has recorded historical root /state/legacy with spaces. Continue that exact task and collect its successor. The current CLI default is different.",
+      "expected": ["pass the exact recorded --root argument /state/legacy with spaces on continue, status, and collect", "use the exact predecessor and returned successor IDs", "no fresh dispatch", "do not move or search for the task in the default root"]
+    },
+    {
+      "name": "ordinary-schedule-root",
+      "prompt": "Create a recurring task in this project, then inspect its definition, history, and execution from another project in the same user/configuration context. No custom state root was requested.",
+      "expected": ["omit --root on schedule create, list, show, history, and execution", "keep the definition's own project --cwd", "no per-project root", "do not start a persistent scheduler inside the agent task", "forward any returned scheduler.serve_command argv intact"]
     },
     {
       "name": "pending-without-questions",

package/plugins/delegation-layer/skills/agent-integration/examples/json-results.md

@@ -1,8 +1,11 @@
 # JSON decision sketch
 
+Use the created task's exact ID as `TASK_ID` and follow the main skill's
+[root rule](../SKILL.md#3-prepare-separate-paths-and-a-finite-brief).
+
 ```sh
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" status "$TASK_ID" --json
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" collect "$TASK_ID" --watch 5s --json
+delegate status TASK_ID --json
+delegate collect TASK_ID --watch 5s --json
 ```
 
 Apply [result handling](../references/result-handling.md) to each response and

package/plugins/delegation-layer/skills/agent-integration/examples/managed-workspace.md

@@ -3,14 +3,18 @@
 Use this example for independent write work that should be isolated in a
 retained Git worktree. The source must be a Git checkout and the state root
 must remain outside provider-writable workspaces.
+Commands use the CLI default under the main skill's
+[root rule](../SKILL.md#3-prepare-separate-paths-and-a-finite-brief); preserve any
+explicit custom or recorded historical root on all related commands.
 
 ```sh
 SOURCE="$PWD"
-BRIEF="$(mktemp)"
-RESPONSE="$(mktemp)"
+BRIEF="$(mktemp)" || exit 1
+RESPONSE="$(mktemp)" || exit 1
 printf '%s\n' 'Implement the requested change and report the files changed.' >"$BRIEF"
+printf 'Saved response: %s\n' "$RESPONSE"
 
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
+if delegate dispatch --auto \
   --brief "$BRIEF" --cwd "$SOURCE" \
   --permission workspace-write --isolation git-worktree \
   --base HEAD --workspace-budget 5m --budget 30m --json >"$RESPONSE"; then
@@ -26,28 +30,51 @@ Read the saved JSON before running another command. When
 `task_record: "created"`, use its `task_id` as `TASK_ID` below. When no task
 was created, follow the [result decisions](../references/result-handling.md#managed-workspace-results);
 do not run task status or collection against that nonexistent record.
+Each later block is a separate shell invocation. Replace `ABS_SAVED_RESPONSE`
+with the printed absolute response path and the ID placeholders with the actual
+returned IDs; reassign the path in each invocation.
 
 ```sh
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" status TASK_ID --json >"$RESPONSE.status"; then
+RESPONSE="ABS_SAVED_RESPONSE"
+if delegate status TASK_ID --json >"$RESPONSE.status"; then
   status_exit=0
 else
   status_exit=$?
 fi
 printf '%s\n' "$status_exit" >"$RESPONSE.status.exit"
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" collect TASK_ID --watch 5s --json >"$RESPONSE.collect"; then
+cat "$RESPONSE.status"
+```
+
+Read the saved status JSON and apply
+[Observe and collect](../references/result-handling.md#observe-and-collect)
+before running another command. Run the collection below only when that
+guidance calls for it.
+
+```sh
+RESPONSE="ABS_SAVED_RESPONSE"
+if delegate collect TASK_ID --watch 5s --json >"$RESPONSE.collect"; then
   collect_exit=0
 else
   collect_exit=$?
 fi
 printf '%s\n' "$collect_exit" >"$RESPONSE.collect.exit"
+cat "$RESPONSE.collect"
 ```
 
-Continue observing that created task when collection exits `3`. Wait for the
-workspace to return to `state: retained` and inspect its final capture. Only
-after the Lead explicitly chooses release, run:
+Apply that same decision order to the collection JSON before treating exit `3`
+as pending. Cancellation, `failure.code: "task_cancelled"` or
+`failure.next_action: "stop_and_report"` ends pending polling; do not continue
+the task or dispatch a replacement. Bounded
+[failure diagnosis](../references/result-handling.md#failure-diagnosis)
+remains available. Keep observing the same task with a finite watch only when
+the canonical guidance calls for it.
+
+Before release, wait for the workspace to return to `state: retained` and inspect
+its final capture. Only after the Lead explicitly chooses release, run:
 
 ```sh
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" workspace release WORKSPACE_ID \
+RESPONSE="ABS_SAVED_RESPONSE"
+if delegate workspace release WORKSPACE_ID \
   --budget 5m --json >"$RESPONSE.release"; then
   release_exit=0
 else
@@ -62,10 +89,11 @@ Follow the same result decisions rather than assuming either response is
 completed cleanup.
 
 Save each response and exit code once. A created task is observed with
-`status` first and collected in the foreground. Exit `3` means pending, not
-success; continue observing the same task. The Lead reviews the capture and
-owns landing any changes. `workspace release` is explicit; no automatic
-apply, commit, branch merge, TTL eviction, or provider-CLI fallback occurs.
+`status` first and collected in the foreground, following the canonical
+observation decisions before each next step. Exit `3` alone is not a reason
+to keep polling. The Lead reviews the capture and owns landing any changes.
+`workspace release` is explicit; no automatic apply, commit, branch merge,
+TTL eviction, or provider-CLI fallback occurs.
 
 ## Fork from a checkpoint
 
@@ -77,8 +105,9 @@ owns every response decision.
 
 ```sh
 SOURCE="$PWD"
-RESPONSE="$(mktemp)"
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" checkpoint create \
+RESPONSE="$(mktemp)" || exit 1
+printf 'Saved response: %s\n' "$RESPONSE"
+if delegate checkpoint create \
   --cwd "$SOURCE" --budget 5m --json >"$RESPONSE.checkpoint"; then
   checkpoint_exit=0
 else
@@ -91,9 +120,12 @@ cat "$RESPONSE.checkpoint"
 Exit `3` with `checkpoint.id` and `next_action: "watch_checkpoint"` means the
 request was accepted, not captured. Use that `checkpoint.id` as
 `CHECKPOINT_ID`. Do not run `create` again.
+For the later checkpoint blocks, replace `ABS_SAVED_RESPONSE` with the absolute
+response path printed by this checkpoint invocation.
 
 ```sh
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" checkpoint status CHECKPOINT_ID \
+RESPONSE="ABS_SAVED_RESPONSE"
+if delegate checkpoint status CHECKPOINT_ID \
   --watch 30s --json >"$RESPONSE.checkpoint.status"; then
   checkpoint_status_exit=0
 else
@@ -112,7 +144,8 @@ dispatch example, replacing `--base HEAD` with `--base COMMIT_OID`. Report a
 When the Lead no longer needs the checkpoint, remove it explicitly:
 
 ```sh
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" checkpoint remove CHECKPOINT_ID \
+RESPONSE="ABS_SAVED_RESPONSE"
+if delegate checkpoint remove CHECKPOINT_ID \
   --budget 5m --json >"$RESPONSE.checkpoint.remove"; then
   checkpoint_remove_exit=0
 else

package/plugins/delegation-layer/skills/agent-integration/examples/read-only-task.md

@@ -2,6 +2,8 @@
 
 Run from the intended workspace, outside Delegate's private state root.
 Use a catalog provider ID in place of `--auto` when a destination was named.
+This example uses the CLI default under the main skill's
+[root rule](../SKILL.md#3-prepare-separate-paths-and-a-finite-brief).
 Prepare paths and dispatch in this same shell invocation:
 
 ```sh
@@ -13,7 +15,7 @@ Inspect the workspace and summarize the current test failures. Do not edit files
 You are the assigned worker; perform this task without delegating it.
 EOF
 printf 'Saved response: %s\n' "$RESPONSE"
-if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
+if delegate dispatch --auto \
   --brief "$BRIEF" --cwd "$WORKSPACE" \
   --permission read-only --budget 30m --json >"$RESPONSE"; then
   dispatch_exit=0

package/plugins/delegation-layer/skills/agent-integration/references/ccr.md

@@ -3,6 +3,9 @@
 Use this reference when asked to consult Claude Code Router (CCR), use one of
 its configured model aliases, or compare its models with other harnesses.
 CCR runs Claude Code against a configured third-party or local provider.
+Use the CLI default under the main skill's
+[root rule](../SKILL.md#3-prepare-separate-paths-and-a-finite-brief); preserve any
+explicit custom or recorded historical root for model discovery and dispatch.
 
 1. Resolve CCR through `delegate providers --json`; its profile is `ccr:print`.
 2. Preserve an explicitly requested CCR alias as `--model ALIAS`. Do not replace
@@ -12,9 +15,10 @@ CCR runs Claude Code against a configured third-party or local provider.
    Choose a suitable configured alias from the available metadata and report
    the choice. Clarify when the intended model remains ambiguous. If discovery
    is unavailable and no alias is known, report the blocker; do not guess.
-4. Dispatch through Delegate with `--provider ccr:print --model ALIAS`, the brief,
-   workspace, permission, finite budget, and `--json`. Use the normal status,
-   collect, and continuation procedure from the main skill.
+4. Dispatch through Delegate with
+   `--provider ccr:print --model ALIAS`, the brief, workspace, permission, finite
+   budget, and `--json`. Use the normal status, collect, and continuation procedure
+   from the main skill.
 
 CCR requires an explicit alias. Unspecified external collaboration still uses
 `dispatch --auto`; do not prefer CCR unless the request calls for it. Multiple

package/plugins/delegation-layer/skills/agent-integration/references/collaboration.md

@@ -45,7 +45,7 @@ RECEIPTS="$(mktemp -d)" || exit 1
 # Set these absolute paths and catalog IDs in this same tool invocation.
 # BRIEF_A and BRIEF_B contain the real independent assignments.
 (
-  if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --provider "$PROVIDER_A" \
+  if delegate dispatch --provider "$PROVIDER_A" \
     --brief "$BRIEF_A" --cwd "$WORKSPACE_A" \
     --permission read-only --budget 30m --json \
     >"$RECEIPTS/review-a.json" 2>"$RECEIPTS/review-a.stderr"; then
@@ -56,7 +56,7 @@ RECEIPTS="$(mktemp -d)" || exit 1
   printf '%s\n' "$dispatch_exit" >"$RECEIPTS/review-a.exit"
 ) &
 (
-  if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --provider "$PROVIDER_B" \
+  if delegate dispatch --provider "$PROVIDER_B" \
     --brief "$BRIEF_B" --cwd "$WORKSPACE_B" \
     --permission read-only --budget 30m --json \
     >"$RECEIPTS/review-b.json" 2>"$RECEIPTS/review-b.stderr"; then