@codedrifters/configulator 0.0.287 → 0.0.288

package/lib/index.mjs

@@ -11853,10 +11853,33 @@ function renderPipelineSkillBody(task, lines) {
     "filter issues by `type:*` or phase label. Each invocation runs the",
     `target sub-agent's full end-to-end cycle exactly once.`,
     "",
-    `Run \`.claude/agents/${task.agent}.md\` and follow its workflow`,
-    "from start to finish. The sub-agent is responsible for picking the",
-    "next unit of work, delegating implementation to other workers as",
-    "needed, and exiting cleanly.",
+    "## Depth-0 execution contract",
+    "",
+    "**You \u2014 the scheduled-task session \u2014 are the pipeline manager.**",
+    "Do **not** spawn the target sub-agent via the `Agent` tool. The",
+    "Claude Code runtime forbids nested sub-agent spawning: a depth-1",
+    "sub-agent cannot invoke `Agent` to reach depth-2, so a pipeline",
+    "manager that delegates to other workers must run at depth-0 (this",
+    "scheduled-task session). See",
+    '<https://code.claude.com/docs/en/sub-agents> \u2014 *"Subagents cannot',
+    "spawn other subagents. If your workflow requires nested delegation,",
+    'use Skills or chain subagents from the main conversation."*',
+    "",
+    "Therefore:",
+    "",
+    `1. **Read \`.claude/agents/${task.agent}.md\` in this session** and`,
+    "   execute its phase pipeline directly. Treat the agent file as a",
+    "   workflow runbook the scheduled-task session follows step-by-step,",
+    "   not as a sub-agent to spawn.",
+    "2. **Use the `Agent` tool (with the `subagent_type` parameter set",
+    "   to the target worker name) to delegate one tier down.** From",
+    "   depth-0, you can spawn a depth-1 sub-agent (e.g. `issue-worker`,",
+    "   `pr-reviewer`) for the implementation, review, or merge step the",
+    "   pipeline calls out.",
+    "3. **Never spawn the pipeline manager itself as a sub-agent.** Do",
+    `   not call \`Agent(subagent_type: "${task.agent}", ...)\`. That`,
+    "   would put the pipeline manager at depth-1 and break every",
+    "   subsequent delegation step.",
     "",
     "## Recommended model",
     "",
@@ -13278,7 +13301,6 @@ var orchestratorSubAgent = {
   description: "End-to-end pipeline manager that runs one full cycle every invocation: pre-flight PR merge \u2192 triage \u2192 maintenance \u2192 queue scan \u2192 delegate the picked issue to the issue-worker \u2192 cleanup",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 100,
-  canDelegateToAgents: ["issue-worker", "pr-reviewer"],
   platforms: { cursor: { exclude: true } },
   prompt: [
     "# Orchestrator Agent",
@@ -13659,7 +13681,6 @@ var issueWorkerSubAgent = {
   description: "Selects the next ready issue from the queue, claims it, and implements the change end-to-end following repository conventions",
   model: AGENT_MODEL.POWERFUL,
   maxTurns: 100,
-  canDelegateToAgents: [],
   platforms: { cursor: { exclude: true } },
   prompt: [
     "# Issue Worker",
@@ -14088,7 +14109,13 @@ var ORCHESTRATOR_CONVENTIONS_PREAMBLE = [
   "- The queue scan reads only `priority:*` and `status:*` labels \u2014 type-routing (which typed agent handles a given `type:*` label) is the `issue-worker`'s concern, not the orchestrator's. The orchestrator's funnel-tier sort is a tie-breaker on `priority:*`, not a routing decision.",
   "- Priority order: critical > high > medium > low > trivial, then **funnel tier asc** (lower tier wins ties), then FIFO by issue number",
   "- Stale thresholds: 72h for in-progress, 168h for blocked",
-  "- Flagged issues get `status:needs-attention` \u2014 they are not auto-reset"
+  "- Flagged issues get `status:needs-attention` \u2014 they are not auto-reset",
+  "",
+  "## Depth-0 invocation requirement",
+  "",
+  'The orchestrator agent **must run as the top-level (depth-0) session** when its Phase G needs to delegate work to the `issue-worker` sub-agent. The Claude Code harness forbids nested sub-agent spawning \u2014 *"Subagents cannot spawn other subagents. If your workflow requires nested delegation, use Skills or chain subagents from the main conversation."* (see <https://code.claude.com/docs/en/sub-agents>). If the orchestrator itself were spawned as a depth-1 sub-agent (e.g. via `Agent(subagent_type: "orchestrator")` from another session), the `Agent` tool needed to reach the `issue-worker` at depth-2 would not be available and Phase G would silently abort.',
+  "",
+  'Practical implication for scheduled-task wiring: the `worker-orchestrator` scheduled task\'s `SKILL.md` instructs the **scheduled-task session itself** to read `.claude/agents/orchestrator.md` and execute its phase pipeline in-session, then use the `Agent` tool to delegate the picked work item to `issue-worker` (depth-1). The scheduled task does **not** call `Agent(subagent_type: "orchestrator")` \u2014 that would put the orchestrator at depth-1 and break the chain.'
 ].join("\n");
 function buildOrchestratorConventionsContent(tiers, scopeGate = resolveScopeGate(), runRatio = resolveRunRatio(), preflight = resolvePreflightPr(), scheduledTasks = resolveScheduledTasks(), unblockDependents = resolveUnblockDependents()) {
   return [
@@ -27260,12 +27287,6 @@ var ClaudeRenderer = class _ClaudeRenderer {
       if (agent.platforms?.claude?.memory) {
         lines.push(`memory: ${agent.platforms.claude.memory}`);
       }
-      if (agent.canDelegateToAgents && agent.canDelegateToAgents.length > 0) {
-        lines.push(`canDelegateToAgents:`);
-        for (const delegateName of agent.canDelegateToAgents) {
-          lines.push(`  - "${delegateName}"`);
-        }
-      }
       lines.push("---");
       lines.push("");
       lines.push(...agent.prompt.split("\n"));