@cleocode/skills 2026.10.23 → 2026.10.24

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cleocode/skills",
-  "version": "2026.10.23",
+  "version": "2026.10.24",
   "description": "CLEO skill definitions - bundled with CLEO monorepo",
   "main": "index.js",
   "types": "index.d.ts",

package/skills/ct-orchestrator/SKILL.md

@@ -2,7 +2,7 @@
 name: ct-orchestrator
 description: "Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to \"orchestrate\", \"orchestrator mode\", \"run as orchestrator\", \"delegate to subagents\", \"coordinate agents\", \"spawn subagents\", \"multi-agent workflow\", \"context-protected workflow\", \"agent farm\", \"HITL orchestration\", \"pipeline management\", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime."
 metadata:
-  version: 4.1.3
+  version: 4.1.4
   tier: core
   install: harness
   covers:
@@ -384,6 +384,13 @@ cleo verify <taskId> --gate qaPassed   --evidence "ci:<pr>"   # merged + evidenc
 cleo complete <taskId>
 ```
 
+`cleo complete` merges a worker's `task/<id>` branch into the local default
+branch only when CLEO provisioned its worktree and the main checkout is on that
+branch with no uncommitted tracked changes; otherwise it skips or refuses, never
+switches the checkout and never pushes. Check `integration` in
+`cleo done <taskId> --plan` first; pass `--no-integrate` (or set
+`CLEO_NO_AUTO_WORKTREE_COMPLETE=1`) when the branch lands through a PR.
+
 Never re-run a worker's full suite to "double-check": a worker's
 `tool:test-affected` or `tool:test` result for the same tree and the
 same resource limits is a cache hit, and once the PR merges, a project that sets `evidence.ciSatisfies`

package/skills/ct-task-executor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ct-task-executor
 description: General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.
-version: 2.8.6
+version: 2.8.7
 protocol: implementation
 adrRefs:
   - ADR-070
@@ -17,7 +17,7 @@ compatibility:
   - gemini-cli
 license: MIT
 metadata:
-  version: 2.8.6
+  version: 2.8.7
   tier: core
   install: harness
   covers:
@@ -29,7 +29,7 @@ metadata:
     - packages/core/src/validation/protocols/cant/implementation.cant
     - packages/core/src/validation/protocols/protocols-markdown/implementation.md
   loomStage: implementation
-  lastReviewed: 2026-10-24
+  lastReviewed: 2026-10-25
   stability: stable
 ---
 
@@ -148,6 +148,13 @@ A database or service started for a test run must not outlive it. A `docker run`
 4. **Complete task** - Mark task done in task system. `cleo done <id> --pr <n>` completes
    through PR `<n>`: the plan and the completion judge a scoped test run against the same
    merge commit, so a ready plan is not refused by a different carrier.
+   Completion merges the task branch into the local default branch only for a worktree
+   CLEO provisioned, only when the main checkout is already on that branch with no
+   uncommitted tracked changes, and never pushes; a hand-made `task/<id>` branch is
+   skipped. `cleo done <id> --plan` shows the decision under `integration`
+   (`merge`/`skip`/`refuse` and why); `cleo complete --no-integrate` or
+   `CLEO_NO_AUTO_WORKTREE_COMPLETE=1` leaves branch and worktree untouched, and the
+   envelope's `integration` reports what happened.
 
 ---
 

package/skills/manifest.json

@@ -1001,7 +1001,7 @@
     },
     {
       "name": "ct-orchestrator",
-      "version": "4.1.3",
+      "version": "4.1.4",
       "description": "Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to \\\"orchestrate\\\", \\\"orchestrator mode\\\", \\\"run as orchestrator\\\", \\\"delegate to subagents\\\", \\\"coordinate agents\\\", \\\"spawn subagents\\\", \\\"multi-agent workflow\\\", \\\"context-protected workflow\\\", \\\"agent farm\\\", \\\"HITL orchestration\\\", \\\"pipeline management\\\", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.",
       "path": "skills/ct-orchestrator",
       "tier": 0,
@@ -1489,7 +1489,7 @@
     },
     {
       "name": "ct-task-executor",
-      "version": "2.8.6",
+      "version": "2.8.7",
       "description": "General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.",
       "path": "skills/ct-task-executor",
       "tier": 0,