@cleocode/skills 2026.10.18 → 2026.10.19

package/package.json

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

package/skills/ct-cleo/SKILL.md

@@ -2,14 +2,14 @@
 name: ct-cleo
 description: CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.
 metadata:
-  version: 2.24.13
+  version: 2.24.15
   tier: core
   install: harness
   covers:
     - packages/cleo/src/cli/commands/session.ts
     - packages/cleo/src/cli/commands/focus.ts
     - packages/cleo/src/cli/commands/sticky.ts
-  lastReviewed: 2026-10-13
+  lastReviewed: 2026-10-16
   stability: stable
 ---
 

package/skills/ct-dev-workflow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ct-dev-workflow
 description: Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.
-version: 3.1.22
+version: 3.1.25
 protocol: contribution
 dependencies: []
 sharedResources:
@@ -14,7 +14,7 @@ compatibility:
   - gemini-cli
 license: MIT
 metadata:
-  version: 3.1.22
+  version: 3.1.25
   tier: core
   install: harness
   covers:
@@ -107,7 +107,11 @@ only on a parentless first commit (T13582); a later commit with that subject, or
 longer or different subject, still needs a task ID. A template change adds the
 previously shipped hash to `legacy-hashes.json` so installed copies refresh.
 It probes CLEO_PROJECT_HOOK_V1 before invoking the implemented CLI adapter;
-missing or incompatible runners warn and allow. Verify nested checkout paths, linked
+missing or incompatible runners warn and allow. `cleo hook run --probe -- execution`
+answers EXEC or INERT (older builds answer V1; stable builds before 2026.10.17 are
+inert). Every ungated push, including a hooks-inert `cleo` first on PATH, prints one
+pre-push stderr line `WARNING: push NOT gated by project hooks: <reason>`, flagging a
+checkout whose activation is on (T13774). Verify nested checkout paths, linked
 worktrees, custom hook paths, historical release bodies and corrupt receipts
 with focused Git fixtures before changing this delivery path.
 
@@ -334,9 +338,15 @@ Linux `Unit Tests` shard green (a docs-only push that skipped the tests does
 not count). It sets `skip-macos-tests=true` when the newest completed nightly
 or `macos-main.yml` (main-push, never cancelled mid-run, pending pushes coalesce;
 T13143, T13187) run with macOS jobs for
-one of those commits is green. The SHA travels as `verified-sha`, and the
-workflow ignores the skips if it checks out another commit or `verified-sha` is
-empty. Otherwise the 8 Linux and 8 macOS test shards run, and the reason names
+one of those commits is green. A `ci.yml` push run still queued or in progress
+is polled for up to 10 minutes first (T13823). The SHA travels as
+`verified-sha` and the proving run's id as `reused-ci-run`; the workflow
+ignores the skips if it checks out another commit or `verified-sha` is empty,
+and re-reads the reused run from the API (push to main, success, every Linux
+shard green, same tree: the exact commit, or one it extends only by
+whole-path-allowlisted plan, changeset `.md` and CHANGELOG.md files; T13825)
+before it skips the Linux shards, naming the run in the
+summary and the bump-PR body. Otherwise the 8 Linux and 8 macOS test shards run, and the reason names
 the newest main commit that has a green macOS run. The decision is in the run
 summary.
 

package/skills/ct-documentor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ct-documentor
 description: Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Carries the CLEO writing and review guides as references and coordinates ct-spec-writer and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.
-version: 3.25.3
+version: 3.25.4
 protocol: null
 dependencies:
   - ct-spec-writer
@@ -16,13 +16,13 @@ compatibility:
   - gemini-cli
 license: MIT
 metadata:
-  version: 3.25.3
+  version: 3.25.4
   tier: core
   install: harness
   covers:
     - packages/cleo/src/cli/commands/docs.ts
     - packages/contracts/src/docs-taxonomy.ts
-  lastReviewed: 2026-10-15
+  lastReviewed: 2026-10-16
   stability: stable
 ---
 
@@ -134,6 +134,11 @@ filesystem write through the docs SSoT (see "Coordinator Pattern" below).
 ct-documentor is a router. It dispatches each doc-type to its owning skill,
 and every owner writes through `cleo docs add` — not raw filesystem writes.
 
+Argument order (T13726): OWNER-ID is the first positional and the file the second —
+`cleo docs add T123 ./doc.md`, never `cleo docs add ./doc.md`. A path in the owner slot,
+reversed positionals, a missing source or a missing file each fail with the corrected command
+in `error.fix`.
+
 | Doc Type | Owner Skill | SSoT Command |
 |----------|-------------|--------------|
 | `spec` (REQ-XXX requirements) | `ct-spec-writer` | `cleo docs add <ownerId> <path> --type spec --slug spec-<feature>` |

package/skills/ct-release-orchestrator/SKILL.md

@@ -7,7 +7,7 @@ adrRefs:
   - ADR-063
   - ADR-065
 metadata:
-  version: 3.2.6
+  version: 3.2.7
   tier: on-demand
   install: harness
   covers:
@@ -49,7 +49,9 @@ Owns the canonical 4-verb release pipeline established by SPEC-T9345 and finalis
 
 ## Core Principle
 
-> Each verb owns exactly one state transition. No verb performs more than one mutation. Multi-step orchestration uses `ship-e2e-smoke` (validator) — never compose the verbs into a custom script.
+> Each verb owns exactly one state transition. No verb performs more than one mutation. Multi-step orchestration uses `ship-e2e-smoke` (validator) — never compose the verbs into a custom script. The one sanctioned end-to-end runner is `scripts/release-run.mjs` (below).
+
+**Single release PR (T13825, owner choice 2026-10-16).** `node scripts/release-run.mjs <ver> --epic <id> --notes-review <file> [--execute]` runs plan → independent notes review (`{"reviewer","notesSha256","approved":true}` by someone other than the operator, for the plan's exact `meta.releaseNotes`) → `release/plan-<ver>` (one commit, plan + CHANGELOG.md, on the default branch's HEAD, made through the GitHub API) → `cleo release open <ver> --ref release/plan-<ver>` → waits for release-prepare and the bump PR's dispatched `CI` on its exact head → version-only assert against the merge-base → `gh pr merge --admin --merge --match-head-commit` plus the `.cleo/audit/force-bypass.jsonl` line → explicit `git tag -a` on the merge commit and push. The bump PR carries the plan and the bump. Dry-run by default; every step resumes on re-run. `--ref` alone dispatches on any plan branch; preflight skips carry over only when it adds release-plan files alone.
 
 ## Canonical Pipeline
 

package/skills/manifest.json

@@ -226,7 +226,7 @@
     },
     {
       "name": "ct-cleo",
-      "version": "2.24.13",
+      "version": "2.24.15",
       "description": "CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.",
       "path": "skills/ct-cleo",
       "tier": 0,
@@ -566,7 +566,7 @@
     },
     {
       "name": "ct-dev-workflow",
-      "version": "3.1.22",
+      "version": "3.1.25",
       "description": "Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.",
       "path": "skills/ct-dev-workflow",
       "tier": 0,
@@ -642,7 +642,7 @@
     },
     {
       "name": "ct-documentor",
-      "version": "3.25.3",
+      "version": "3.25.4",
       "description": "Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Carries the CLEO writing and review guides as references and coordinates ct-spec-writer and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.",
       "path": "skills/ct-documentor",
       "tier": 0,
@@ -1168,7 +1168,7 @@
     },
     {
       "name": "ct-release-orchestrator",
-      "version": "3.2.6",
+      "version": "3.2.7",
       "description": "Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo release open, then PR + GHA tag workflow, then cleo release reconcile. The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline end-to-end (dry-run by default). The full verb-to-state map is in docs/release/verb-matrix.md. Use when shipping a new version, validating the release pipeline end-to-end, or promoting a completed epic to released status.",
       "path": "skills/ct-release-orchestrator",
       "tier": 1,