delegation-layer 0.1.21 → 0.1.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "delegation-layer",
-  "version": "0.1.21",
+  "version": "0.1.22",
   "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.1.21",
+  "version": "0.1.22",
   "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.1.21",
+  "version": "0.1.22",
   "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

@@ -1,6 +1,6 @@
 ---
 name: agent-integration
-description: Coordinate external agent, model, and separate harness tasks through Delegate, including research, implementation, tests, reviews, consultations, comparisons, and debates. Use before choosing an external integration; ordinary native subagents and questions about tools remain local.
+description: Use Delegate for work assigned to another agent, model, or separate harness CLI session. Load this before a provider-specific skill or plugin, including when a user names a CLI for research, implementation, tests, reviews, consultations, comparisons, or debates. A named destination still routes through Delegate. Ordinary same-harness subagents and questions about tools remain local; respect an explicit choice of another integration.
 ---
 
 # Delegation Layer
@@ -13,6 +13,8 @@ external harness to do work. Requests such as “ask Codex to review this”,
 collaboration even when the user never mentions Delegate. The same applies
 when you decide external expertise is useful to fulfill the user's task.
 These names are examples; discover supported destinations through the CLI.
+A destination name identifies who should do the work; it does not by itself
+select a provider-specific skill, plugin, or direct CLI integration.
 “Claude Code Router” and “CCR” mean `ccr:print`, not ordinary Claude Code.
 For that request, use Delegate with a CCR model alias; a Claude-specific skill
 or subscription model does not fulfill the requested route.
@@ -36,8 +38,10 @@ not turn that request into an environment-repair task. When a response says
 `failure.next_action: "stop_and_report"`, that attempt is finished. Include its
 failure in your final response without opening a clarification dialog to choose
 a fallback. For `task_record: not_created`, identify the requested destination
-and quote the returned `task_id` (if present), `task_record`, `failure`, and
-`error`. Do not append inferred state paths or provider-setup diagnoses. Do not run diagnostic commands, retry it, or use another integration.
+and include the saved JSON failure response verbatim. A `task_id` can be returned
+even when no task record was created. Do not infer that an unavailable provider
+is uninstalled or unauthenticated. Do not append inferred state paths or
+provider-setup diagnoses, run diagnostic commands, retry it, or use another integration.
 Troubleshooting requires a separate user request. Other independently requested
 tasks may proceed; the failed attempt must remain reported as failed or blocked.
 
@@ -79,18 +83,23 @@ tasks may proceed; the failed attempt must remain reported as failed or blocked.
    Collection may recover the
    saved supervisor only to observe an already-requested budget stop; it never
    launches a provider or retries a task.
-6. If a task is timed out and its JSON says `continuation.resumable: true`, use
+6. If `failure.next_action` is `recheck`, follow
+   [offline recovery](references/result-handling.md#offline-recovery) once for
+   that task. Rechecking saved evidence does not run the provider again.
+   Otherwise, report a rejected result without redispatching or reading raw
+   output as an answer.
+7. If a task is timed out and its JSON says `continuation.resumable: true`, use
    `continue --task TASK_ID`, optionally with a new `--brief`. Do not create a
    fresh unrelated dispatch to replace a resumable task.
-7. Treat `blocked` authentication as unresolved. Do not call it compatible,
+8. Treat `blocked` authentication as unresolved. Do not call it compatible,
    successful, or failed provider behavior, and do not invent login commands.
-8. Never put credentials, tokens, or unrestricted provider output in a brief,
+9. Never put credentials, tokens, or unrestricted provider output in a brief,
    option, receipt, or agent message.
-9. Permission modes select provider-native behavior, not an independent sandbox.
+10. Permission modes select provider-native behavior, not an independent sandbox.
    Providers load their own configuration and extensions. If a task is rejected,
    report delegate's evidence; do not assume the user's configuration is faulty
    or remove MCP servers, plugins, settings, or credentials to make it pass.
-10. The model chooses ordinary-task fan-out by issuing independent `dispatch`
+11. The model chooses ordinary-task fan-out by issuing independent `dispatch`
     commands concurrently. The private supervisor does not impose a task-count
     or CPU-based limit. Use this for independent investigation, debate, review,
     or provider comparison. Concurrent write tasks must use separate workspaces
@@ -162,6 +171,8 @@ Use an existing task brief when one is supplied. Otherwise create a bounded
 brief file that contains the requested work and its acceptance criteria. Keep
 the state root outside the workspace and provider-writable trees (which can
 include the system temporary directory). Use `DELEGATE_ROOT` when supplied.
+Pass a regular file path for `--brief`, not shell process substitution such as
+`<(...)` or an ephemeral `/dev/fd/...` path.
 
 Run path preparation and dispatch in **one shell/tool invocation**, as shown
 below. Shell variables may disappear between tool calls. For later commands,
@@ -190,7 +201,10 @@ when waiting, replying, steering, or continuing.
 
 Use automatic selection unless the user named a destination.
 For a named harness or provider resolved in step 2, replace `--auto` with `--provider PROVIDER_ID`; never
-combine the two:
+combine the two.
+
+Capture the dispatch exit code with `if`, as below. This prints the response
+even when dispatch fails and the surrounding shell has `set -e` enabled.
 
 ```sh
 WORKSPACE="$PWD"
@@ -200,13 +214,17 @@ cat >"$BRIEF" <<'EOF'
 Describe the delegated task, the files or behavior to change, and the checks
 that must pass. Keep the response concise and report validation evidence.
 EOF
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
+printf 'Saved response: %s\n' "$RESPONSE"
+if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
   --brief "$BRIEF" \
   --cwd "$WORKSPACE" \
   --permission read-only \
   --budget 30m \
-  --json >"$RESPONSE"
-dispatch_exit=$?
+  --json >"$RESPONSE"; then
+  dispatch_exit=0
+else
+  dispatch_exit=$?
+fi
 cat "$RESPONSE"
 printf '\nDispatch exit: %s; saved response: %s\n' "$dispatch_exit" "$RESPONSE"
 ```

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

@@ -199,6 +199,32 @@
       ],
       "split": "validation"
     },
+    {
+      "name": "recheck-recoverable",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md without editing. If the terminal result is rejected with failure.next_action=recheck, recheck the same task once and report only the verified recovered answer.",
+      "external": true,
+      "provider": "codex:exec",
+      "fixture_scenario": "recoverable-rejection",
+      "holdout": true,
+      "split": "validation"
+    },
+    {
+      "name": "recheck-still-rejected",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md without editing. If the terminal result is rejected with failure.next_action=recheck, recheck the same task once and report the rejection without using raw output as an answer.",
+      "external": true,
+      "provider": "codex:exec",
+      "fixture_scenario": "still-rejected-recheck",
+      "holdout": true,
+      "split": "validation"
+    },
+    {
+      "name": "external-collaboration-holdout",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md and report its finding without editing.",
+      "external": true,
+      "provider": "codex:exec",
+      "holdout": true,
+      "split": "validation"
+    },
     {
       "name": "requested-model-effort",
       "prompt": "Ask a separate Codex CLI session to review pricing.py without edits. Use model gpt-5.6-luna and effort max, preserving both choices.",

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

@@ -13,6 +13,7 @@ All paths passed to `--root`, `--cwd`, and `--brief` must be absolute. Add
 | `delegate dispatch --auto ... --json` | Select and admit one bounded turn | Yes, at most once |
 | `delegate status TASK --json` | Reconcile and observe task state | No provider launch |
 | `delegate collect TASK --watch 5s --json` | Read or wait for publication | No provider launch |
+| `delegate recheck TASK --json` | Reassess eligible rejected evidence offline | No provider launch; original outcome unchanged |
 | `delegate continue --task TASK ... --json` | Create an exact-session successor | Yes, at most once for the successor |
 | `delegate reply TASK --request ID --answers FILE --id MESSAGE_ID --json` | Answer a pending native question | No new launch |
 | `delegate steer TASK --brief FILE --id MESSAGE_ID --json` | Guide a supported active turn | No new launch |

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

@@ -15,8 +15,9 @@ the same as a successful provider result.
    permits a linked successor even when no outcome has been published.
 4. If `publication` is committed and `outcome.verdict` is committed, return
    the result and its payload/evidence descriptors.
-5. If `outcome.verdict` is rejected, report a terminal rejected result with its
-   refusal and evidence. Do not retry automatically.
+5. If `outcome.verdict` is rejected and `failure.next_action` is `recheck`,
+   follow [offline recovery](#offline-recovery) once. Otherwise report the
+   terminal rejection with its diagnostic and evidence. Do not redispatch.
 6. If `pending.kind` is `interaction`, handle the returned questions using
    [interaction guidance](interaction.md) before waiting again. Otherwise, if
    `liveness` is queued or running or publication is pending, observe the same
@@ -44,3 +45,29 @@ checks static readiness; runtime verification requires the supervised probe.
 Versions and help are observations, not semantic-version allowlists.
 Authentication is a separate live gate (`not_run`, `passed`, or `blocked`).
 Report a blocked prerequisite without inventing a login command or retrying.
+
+## Offline recovery
+
+When Delegate returns `failure.next_action: "recheck"`, use the same root and
+exact task ID:
+
+```sh
+delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" recheck TASK_ID --json
+```
+
+This command checks the already sealed evidence with an explicitly compatible
+new interpreter. It does not run the provider, contact a service, spend model
+tokens, or change the original outcome.
+
+- Exit `0` with `recheck.status: "recovered"`: use only the answer descriptor
+  returned for that recheck. Report that the answer was recovered from saved
+  evidence. The original `publication` remains `rejected`; do not call the
+  original task committed or use recovery to infer continuation permission.
+- Exit `4` with `recheck.status: "rejected"`: report the diagnostic and stop.
+- Exit `1` or `2`, or any response without a verified recovered answer:
+  report the error and stop. Do not read raw streams as a substitute answer,
+  invent a result path, run a provider directly, or launch a replacement task.
+
+Keep the assessment ID and source/target descriptors with the result. Do not
+loop on the same recheck. A separate user request is required for further
+troubleshooting or a new provider task.

package/skills/agent-integration/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: agent-integration
-description: Coordinate external agent, model, and separate harness tasks through Delegate, including research, implementation, tests, reviews, consultations, comparisons, and debates. Use before choosing an external integration; ordinary native subagents and questions about tools remain local.
+description: Use Delegate for work assigned to another agent, model, or separate harness CLI session. Load this before a provider-specific skill or plugin, including when a user names a CLI for research, implementation, tests, reviews, consultations, comparisons, or debates. A named destination still routes through Delegate. Ordinary same-harness subagents and questions about tools remain local; respect an explicit choice of another integration.
 ---
 
 # Delegation Layer
@@ -13,6 +13,8 @@ external harness to do work. Requests such as “ask Codex to review this”,
 collaboration even when the user never mentions Delegate. The same applies
 when you decide external expertise is useful to fulfill the user's task.
 These names are examples; discover supported destinations through the CLI.
+A destination name identifies who should do the work; it does not by itself
+select a provider-specific skill, plugin, or direct CLI integration.
 “Claude Code Router” and “CCR” mean `ccr:print`, not ordinary Claude Code.
 For that request, use Delegate with a CCR model alias; a Claude-specific skill
 or subscription model does not fulfill the requested route.
@@ -36,8 +38,10 @@ not turn that request into an environment-repair task. When a response says
 `failure.next_action: "stop_and_report"`, that attempt is finished. Include its
 failure in your final response without opening a clarification dialog to choose
 a fallback. For `task_record: not_created`, identify the requested destination
-and quote the returned `task_id` (if present), `task_record`, `failure`, and
-`error`. Do not append inferred state paths or provider-setup diagnoses. Do not run diagnostic commands, retry it, or use another integration.
+and include the saved JSON failure response verbatim. A `task_id` can be returned
+even when no task record was created. Do not infer that an unavailable provider
+is uninstalled or unauthenticated. Do not append inferred state paths or
+provider-setup diagnoses, run diagnostic commands, retry it, or use another integration.
 Troubleshooting requires a separate user request. Other independently requested
 tasks may proceed; the failed attempt must remain reported as failed or blocked.
 
@@ -79,18 +83,23 @@ tasks may proceed; the failed attempt must remain reported as failed or blocked.
    Collection may recover the
    saved supervisor only to observe an already-requested budget stop; it never
    launches a provider or retries a task.
-6. If a task is timed out and its JSON says `continuation.resumable: true`, use
+6. If `failure.next_action` is `recheck`, follow
+   [offline recovery](references/result-handling.md#offline-recovery) once for
+   that task. Rechecking saved evidence does not run the provider again.
+   Otherwise, report a rejected result without redispatching or reading raw
+   output as an answer.
+7. If a task is timed out and its JSON says `continuation.resumable: true`, use
    `continue --task TASK_ID`, optionally with a new `--brief`. Do not create a
    fresh unrelated dispatch to replace a resumable task.
-7. Treat `blocked` authentication as unresolved. Do not call it compatible,
+8. Treat `blocked` authentication as unresolved. Do not call it compatible,
    successful, or failed provider behavior, and do not invent login commands.
-8. Never put credentials, tokens, or unrestricted provider output in a brief,
+9. Never put credentials, tokens, or unrestricted provider output in a brief,
    option, receipt, or agent message.
-9. Permission modes select provider-native behavior, not an independent sandbox.
+10. Permission modes select provider-native behavior, not an independent sandbox.
    Providers load their own configuration and extensions. If a task is rejected,
    report delegate's evidence; do not assume the user's configuration is faulty
    or remove MCP servers, plugins, settings, or credentials to make it pass.
-10. The model chooses ordinary-task fan-out by issuing independent `dispatch`
+11. The model chooses ordinary-task fan-out by issuing independent `dispatch`
     commands concurrently. The private supervisor does not impose a task-count
     or CPU-based limit. Use this for independent investigation, debate, review,
     or provider comparison. Concurrent write tasks must use separate workspaces
@@ -162,6 +171,8 @@ Use an existing task brief when one is supplied. Otherwise create a bounded
 brief file that contains the requested work and its acceptance criteria. Keep
 the state root outside the workspace and provider-writable trees (which can
 include the system temporary directory). Use `DELEGATE_ROOT` when supplied.
+Pass a regular file path for `--brief`, not shell process substitution such as
+`<(...)` or an ephemeral `/dev/fd/...` path.
 
 Run path preparation and dispatch in **one shell/tool invocation**, as shown
 below. Shell variables may disappear between tool calls. For later commands,
@@ -190,7 +201,10 @@ when waiting, replying, steering, or continuing.
 
 Use automatic selection unless the user named a destination.
 For a named harness or provider resolved in step 2, replace `--auto` with `--provider PROVIDER_ID`; never
-combine the two:
+combine the two.
+
+Capture the dispatch exit code with `if`, as below. This prints the response
+even when dispatch fails and the surrounding shell has `set -e` enabled.
 
 ```sh
 WORKSPACE="$PWD"
@@ -200,13 +214,17 @@ cat >"$BRIEF" <<'EOF'
 Describe the delegated task, the files or behavior to change, and the checks
 that must pass. Keep the response concise and report validation evidence.
 EOF
-delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
+printf 'Saved response: %s\n' "$RESPONSE"
+if delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" dispatch --auto \
   --brief "$BRIEF" \
   --cwd "$WORKSPACE" \
   --permission read-only \
   --budget 30m \
-  --json >"$RESPONSE"
-dispatch_exit=$?
+  --json >"$RESPONSE"; then
+  dispatch_exit=0
+else
+  dispatch_exit=$?
+fi
 cat "$RESPONSE"
 printf '\nDispatch exit: %s; saved response: %s\n' "$dispatch_exit" "$RESPONSE"
 ```

package/skills/agent-integration/evals/routing.json

@@ -199,6 +199,32 @@
       ],
       "split": "validation"
     },
+    {
+      "name": "recheck-recoverable",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md without editing. If the terminal result is rejected with failure.next_action=recheck, recheck the same task once and report only the verified recovered answer.",
+      "external": true,
+      "provider": "codex:exec",
+      "fixture_scenario": "recoverable-rejection",
+      "holdout": true,
+      "split": "validation"
+    },
+    {
+      "name": "recheck-still-rejected",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md without editing. If the terminal result is rejected with failure.next_action=recheck, recheck the same task once and report the rejection without using raw output as an answer.",
+      "external": true,
+      "provider": "codex:exec",
+      "fixture_scenario": "still-rejected-recheck",
+      "holdout": true,
+      "split": "validation"
+    },
+    {
+      "name": "external-collaboration-holdout",
+      "prompt": "Ask a separate Codex CLI session to review pricing.py against README.md and report its finding without editing.",
+      "external": true,
+      "provider": "codex:exec",
+      "holdout": true,
+      "split": "validation"
+    },
     {
       "name": "requested-model-effort",
       "prompt": "Ask a separate Codex CLI session to review pricing.py without edits. Use model gpt-5.6-luna and effort max, preserving both choices.",

package/skills/agent-integration/references/command-reference.md

@@ -13,6 +13,7 @@ All paths passed to `--root`, `--cwd`, and `--brief` must be absolute. Add
 | `delegate dispatch --auto ... --json` | Select and admit one bounded turn | Yes, at most once |
 | `delegate status TASK --json` | Reconcile and observe task state | No provider launch |
 | `delegate collect TASK --watch 5s --json` | Read or wait for publication | No provider launch |
+| `delegate recheck TASK --json` | Reassess eligible rejected evidence offline | No provider launch; original outcome unchanged |
 | `delegate continue --task TASK ... --json` | Create an exact-session successor | Yes, at most once for the successor |
 | `delegate reply TASK --request ID --answers FILE --id MESSAGE_ID --json` | Answer a pending native question | No new launch |
 | `delegate steer TASK --brief FILE --id MESSAGE_ID --json` | Guide a supported active turn | No new launch |

package/skills/agent-integration/references/result-handling.md

@@ -15,8 +15,9 @@ the same as a successful provider result.
    permits a linked successor even when no outcome has been published.
 4. If `publication` is committed and `outcome.verdict` is committed, return
    the result and its payload/evidence descriptors.
-5. If `outcome.verdict` is rejected, report a terminal rejected result with its
-   refusal and evidence. Do not retry automatically.
+5. If `outcome.verdict` is rejected and `failure.next_action` is `recheck`,
+   follow [offline recovery](#offline-recovery) once. Otherwise report the
+   terminal rejection with its diagnostic and evidence. Do not redispatch.
 6. If `pending.kind` is `interaction`, handle the returned questions using
    [interaction guidance](interaction.md) before waiting again. Otherwise, if
    `liveness` is queued or running or publication is pending, observe the same
@@ -44,3 +45,29 @@ checks static readiness; runtime verification requires the supervised probe.
 Versions and help are observations, not semantic-version allowlists.
 Authentication is a separate live gate (`not_run`, `passed`, or `blocked`).
 Report a blocked prerequisite without inventing a login command or retrying.
+
+## Offline recovery
+
+When Delegate returns `failure.next_action: "recheck"`, use the same root and
+exact task ID:
+
+```sh
+delegate --root "${DELEGATE_ROOT:-$HOME/delegation-state}" recheck TASK_ID --json
+```
+
+This command checks the already sealed evidence with an explicitly compatible
+new interpreter. It does not run the provider, contact a service, spend model
+tokens, or change the original outcome.
+
+- Exit `0` with `recheck.status: "recovered"`: use only the answer descriptor
+  returned for that recheck. Report that the answer was recovered from saved
+  evidence. The original `publication` remains `rejected`; do not call the
+  original task committed or use recovery to infer continuation permission.
+- Exit `4` with `recheck.status: "rejected"`: report the diagnostic and stop.
+- Exit `1` or `2`, or any response without a verified recovered answer:
+  report the error and stop. Do not read raw streams as a substitute answer,
+  invent a result path, run a provider directly, or launch a replacement task.
+
+Keep the assessment ID and source/target descriptors with the result. Do not
+loop on the same recheck. A separate user request is required for further
+troubleshooting or a new provider task.