@cleocode/skills 2026.11.1-canary.2 → 2026.11.1-canary.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # @cleocode/skills
2
2
 
3
+ > Part of [CLEO](https://github.com/kryptobaseddev/cleo#readme). Start with the root README; run `cleo <command> --help` for any command.
4
+
3
5
  CLEO skill definitions - bundled capabilities for AI agents.
4
6
 
5
7
  ## Overview
@@ -61,7 +63,7 @@ installability and every documented `cleo` command honest.
61
63
  | **ct-epic-architect** | Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. |
62
64
  | **ct-ivt-looper** | Runs a project-agnostic autonomous Implement-then-Validate-then-Test compliance loop on any git worktree. |
63
65
  | **ct-provenance-keeper** | Generates in-toto v1 attestations, SLSA-level provenance records, SBOMs (CycloneDX or SPDX), and sigstore/cosi… |
64
- | **ct-release-orchestrator** | Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo rele… |
66
+ | **ct-release-orchestrator** | Orchestrates CLEO releases: `cleo release cut <version>` tags the newest main commit with green CI, and release.yml writes the CHANGELOG from changesets and publishes. |
65
67
  | **ct-research-agent** | Multi-source research and investigation combining web search, documentation lookup via Context7, and codebase … |
66
68
  | **ct-spec-writer** | Technical specification writing using RFC 2119 language for clear, unambiguous requirements. |
67
69
  | **ct-validator** | Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cleocode/skills",
3
- "version": "2026.11.1-canary.2",
3
+ "version": "2026.11.1-canary.4",
4
4
  "description": "CLEO skill definitions - bundled with CLEO monorepo",
5
5
  "main": "index.js",
6
6
  "types": "index.d.ts",
@@ -2,14 +2,14 @@
2
2
  name: ct-cleo
3
3
  description: CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.
4
4
  metadata:
5
- version: 2.25.1
5
+ version: 2.25.5
6
6
  tier: core
7
7
  install: harness
8
8
  covers:
9
9
  - packages/cleo/src/cli/commands/session.ts
10
10
  - packages/cleo/src/cli/commands/focus.ts
11
11
  - packages/cleo/src/cli/commands/sticky.ts
12
- lastReviewed: 2026-10-28
12
+ lastReviewed: 2026-11-02
13
13
  stability: stable
14
14
  ---
15
15
 
@@ -31,6 +31,12 @@ Use CLI (`cleo`) for all memory operations.
31
31
 
32
32
  - `cleo memory find "{current-topic}" --limit 10`
33
33
  - Avoid re-doing work that's already been completed
34
+ - `cleo memory find "{current-topic}"` also searches the docs store, ranked
35
+ with the BRAIN hits (a full-text index, so it is fast); `--no-docs` leaves
36
+ docs out, `--type doc` searches docs alone, and `--type <brain-type> --docs`
37
+ adds them to one BRAIN table. Only current docs come back: a match on a
38
+ superseded doc returns the doc that replaced it (`replaces` names the old
39
+ slug). Read one with `cleo docs fetch <slug>`.
34
40
 
35
41
  ### After Completing Significant Work
36
42
 
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-dev-workflow
3
3
  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.
4
- version: 3.4.0
4
+ version: 3.4.2
5
5
  protocol: contribution
6
6
  dependencies: []
7
7
  sharedResources:
@@ -14,7 +14,7 @@ compatibility:
14
14
  - gemini-cli
15
15
  license: MIT
16
16
  metadata:
17
- version: 3.4.0
17
+ version: 3.4.2
18
18
  tier: core
19
19
  install: harness
20
20
  covers:
@@ -26,7 +26,7 @@ metadata:
26
26
  - packages/core/src/hooks.ts
27
27
  - packages/core/templates/git-hooks/**
28
28
  - packages/contracts/src/git-hooks.ts
29
- lastReviewed: 2026-10-29
29
+ lastReviewed: 2026-11-02
30
30
  stability: stable
31
31
  ---
32
32
 
@@ -106,9 +106,18 @@ only on a parentless first commit (T13582); a later commit with that subject, or
106
106
  longer or different subject, still needs a task ID. A template change adds the
107
107
  previously shipped hash to `legacy-hashes.json` so installed copies refresh.
108
108
 
109
+ The managed pre-commit refuses CLEO runtime state staged at ANY path (T14189):
110
+ `cleo.db`/`brain.db`/`tasks.db` and their WAL sidecars by name, a `project-info.json`
111
+ naming a `"projectId"`, and `.cleo/config.json` or a byte-identical copy. It lists the
112
+ paths and `git reset -q -- <paths>`; `cleo doctor` runs the same rule (`staged_cleo_state`).
113
+ This repository's `.githooks/pre-commit` calls the template rather than copying it.
114
+
109
115
  `cleo init` and `cleo upgrade` no longer seed the CleoOS hub (Pi extensions, CANT
110
116
  workflows, justfile) into the global CLEO home (T13994, ADR-098); only the deprecated
111
117
  `cleo admin scaffold-hub` still does.
118
+ On a project with no tasks, `cleo init`'s next steps start with the root saga
119
+ (`cleo saga create --title ... --acceptance ...`), the only node allowed without a parent; the
120
+ first `cleo add` refusal names the same command (T14186).
112
121
  It probes CLEO_PROJECT_HOOK_V1 before invoking the implemented CLI adapter;
113
122
  missing or incompatible runners warn and allow. `cleo hook run --probe -- execution`
114
123
  answers EXEC or INERT (older builds answer V1; stable builds before 2026.10.17 are
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-documentor
3
3
  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.
4
- version: 3.33.0
4
+ version: 3.38.0
5
5
  protocol: null
6
6
  dependencies:
7
7
  - ct-spec-writer
@@ -16,13 +16,13 @@ compatibility:
16
16
  - gemini-cli
17
17
  license: MIT
18
18
  metadata:
19
- version: 3.33.0
19
+ version: 3.38.0
20
20
  tier: core
21
21
  install: harness
22
22
  covers:
23
23
  - packages/cleo/src/cli/commands/docs.ts
24
24
  - packages/contracts/src/docs-taxonomy.ts
25
- lastReviewed: 2026-10-28
25
+ lastReviewed: 2026-11-02
26
26
  stability: stable
27
27
  ---
28
28
 
@@ -87,7 +87,11 @@ referenced elsewhere; absolute paths and other devices' paths are only
87
87
  reported. Each pruned row is first appended to
88
88
  `.cleo/audit/docs-publications-prune.jsonl`, and stale mirrors are only
89
89
  reported (republish, or ingest the edit with `cleo docs update`). Use it for store
90
- hygiene checks; it never edits doc content.
90
+ hygiene checks; it never edits doc content. `--apply` runs every repair class
91
+ at once; on a live shared store, scope it with `--only <class,…>` (T14174), for
92
+ example `cleo docs doctor --apply --only publication-ledger-drift`. The dry run's
93
+ `repairCounts` shows planned repairs per class, and an unknown class is refused
94
+ with the valid list.
91
95
 
92
96
  `cleo docs migrate` (T13360) imports legacy docs + history into the re-keyed
93
97
  conduit store inside the migration safety harness (pre-step backup, verified
@@ -729,9 +733,14 @@ cleo docs publish --for T1234 --to docs/feature-x.md
729
733
  Atomic tmp-then-rename. The published file ships in the next commit; the
730
734
  SSoT blob remains canonical and continues to track future versions.
731
735
 
732
- `--to` must resolve under the project root (a relative path resolves there)
733
- or inside a registered canonical task worktree; anything else is refused with
734
- `E_VALIDATION_ERROR` and nothing is created. `--dry-run` runs the same checks
736
+ `--to` must resolve under the project root or inside a registered worktree at
737
+ the project's canonical CLEO location (`<cleoHome>/worktrees/<hash>/<name>`,
738
+ any name); anything else is refused with `E_VALIDATION_ERROR` and nothing is
739
+ created. Run from such a worktree, a relative `--to` lands in that worktree, not
740
+ the root checkout, and the publication ledger records the repo-relative path
741
+ the merge makes true (T14135). `cleo docs status` reads a mirror the root
742
+ checkout has not pulled from the default branch, and reports one that sits only
743
+ in an unmerged worktree as `pending-merge`. `--dry-run` runs the same checks
735
744
  and writes nothing, so a dry run that passes means the real run will.
736
745
 
737
746
  ### Fetch the doc back by slug
@@ -827,9 +836,18 @@ cleo docs modernize --store # stored docs: re-kind
827
836
  Ambiguous classify and merge calls are judged by System One
828
837
  (`docs.modernize.classify`, `docs.modernize.merge`; rule fallback when it is
829
838
  unreachable) and recorded on each plan row. Apply stores survivors, folds
830
- duplicates in, supersedes the removed docs, rewrites relative links to
831
- `[[slug]]` wikilinks (recorded as `links-to` graph edges) and keeps every
832
- replaced byte under `.cleo/modernize/<runId>/` for rollback.
839
+ duplicates in, supersedes the removed docs, re-points relative markdown links
840
+ at the new paths (they still render on GitHub; `--wikilinks` opts into
841
+ `[[slug]]` instead), records every link as a `links-to` graph edge, edits a
842
+ file the plan marks `keep`, or a markdown file under the root that an
843
+ `--exclude` kept out of the plan, only by re-pointing the hrefs the plan lists
844
+ as `linkFixes` (`link-fix` rows, so apply never does more than the dry run
845
+ showed, and an excluded file never reaches the store). Links from tracked
846
+ markdown outside the root (the repo README, AGENTS.md, package READMEs) get
847
+ the same treatment as `base: repo` link-fix rows; CHANGELOG files,
848
+ `.changeset/` and `.cleo/` are history or state and are never rewritten. It
849
+ keeps every replaced byte under
850
+ `.cleo/modernize/<runId>/` for rollback.
833
851
 
834
852
  ---
835
853
 
@@ -2,7 +2,7 @@
2
2
  name: ct-orchestrator
3
3
  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."
4
4
  metadata:
5
- version: 4.2.0
5
+ version: 4.2.1
6
6
  tier: core
7
7
  install: harness
8
8
  covers:
@@ -254,6 +254,12 @@ no CONDUIT subscription; `cleo orchestrate spawn <taskId> --lead-mbx <you>` name
254
254
  mailbox in it. `cleo conduit` and the `conduit-*` sub-commands of `cleo orchestrate` are
255
255
  deprecated (T13982) and leave in the next release; do not build on them.
256
256
 
257
+ **Attached documents are budgeted (T14190).** A spawn prompt's `## Task Documents` section
258
+ inlines the task's attached text documents up to 16,000 characters of prose
259
+ (`orchestration.spawnDocBudgetChars` sets it). Past that, each document is named by its
260
+ exact ref (name and SHA-256) with `cleo docs fetch <ref>`, and the section lists every
261
+ document it left out. A worker reads one with that command when its task needs it.
262
+
257
263
  ### 3. Execute the Work
258
264
 
259
265
  ```
@@ -7,7 +7,7 @@ adrRefs:
7
7
  - ADR-063
8
8
  - ADR-065
9
9
  metadata:
10
- version: 3.5.0
10
+ version: 3.7.0
11
11
  tier: on-demand
12
12
  install: harness
13
13
  covers:
@@ -17,7 +17,7 @@ metadata:
17
17
  - packages/core/src/release/cut.ts
18
18
  - packages/core/src/release/authorization.ts
19
19
  loomStage: release
20
- lastReviewed: 2026-11-01
20
+ lastReviewed: 2026-11-03
21
21
  stability: stable
22
22
  ---
23
23
 
@@ -64,6 +64,10 @@ cleo release cut v2026.10.28 --sha <sha> --lead lead.md --yes # the printed co
64
64
 
65
65
  **Confirmation (D11212).** Nothing is tagged without `--yes`; without it the cut reports and prints the exact confirm command, pinned to the previewed sha. With `--yes`, an active standing release authorization covering the version, or the `release.agentCut` setting, allows the tag (an agent); otherwise the cut asks on the controlling terminal (`/dev/tty`) and tags only when the version is typed exactly, refusing with `E_RELEASE_NOT_AUTHORIZED` (and naming the scope to grant) when there is no terminal. The typed confirmation stops casual misuse only: a caller that drives a pseudo-terminal can still type the version. The audit row records `allowedBy` (`tty-confirm`, `authorization:<id>` or `setting:release.agentCut=<level>@<scope>`).
66
66
 
67
+ **Previous tag (T14173).** The notes, the CHANGELOG section (`write-changelog`) and `release reconcile` start from the newest reachable lower tag whose GitHub Release published; a tag whose `release.yml` run failed before creating its release (a failed canary) is skipped, so its changesets and tasks land in the next release. A stable cut also skips every prerelease tag. When `gh` cannot read a release (auth, network), cut and `write-changelog` refuse rather than guess; reconcile keeps the tag.
68
+
69
+ **Release in flight (T14184).** The cut lists `release.yml` runs not yet completed for a lower release tag (`inFlight`, plus a warning in the dry run). Until such a run creates its GitHub Release, the previous-tag pick skips that tag, so a real cut refuses with `E_RELEASE_IN_FLIGHT` naming each run; wait for them, or pass `--allow-in-flight` to cut now and repeat their entries in these notes.
70
+
67
71
  **Agent cut setting (T14170, D11221).** `release.agentCut` is `off` (default), `canary`, `prerelease` or `stable`; an agent sets it with `cleo config set release.agentCut canary --scope global`, with no terminal or owner password. Each level covers its own scope and every narrower one: `canary` covers `-canary.N`, `prerelease` any prerelease, `stable` everything. A project value (even `off`) shadows the global one. A cut it allows reports `allowedBy`, a warning naming the setting, and an audit row with `scope` and `settingSource`; when it does not cover the version and there is no terminal, the refusal names the exact `cleo config set` command.
68
72
 
69
73
  **Standing authorization (T14141, D11215).** The owner grants it at a terminal with the owner-auth password: `cleo release authorize --scope canary|prerelease|stable|<version> --expires 7d --reason "<why>" [--uses <n>]` (at most 30d; no use limit unless `--uses`). It is signed with the enrolled owner key (`cleo config owner-enroll`), stored in `.cleo/release-authorizations.json` and the global store, recorded as an owner decision, and audited in `.cleo/audit/release-authorizations.jsonl`. `cleo release authorize --list` shows each grant's state; `--revoke <id>` (owner password too) ends one now with a signed revocation, and the revocation count is sealed in `.cleo/owner-settings.json` (commit it). An edited, unsigned or one-sided grant is ignored; an edited, unsigned or shortened revocation list makes every grant tampered (fail closed). `cleo doctor` reports both. A cut it allows carries `Authorized-by: <id>` in the tag message.
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: ct-task-executor
3
3
  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.
4
- version: 2.9.0
4
+ version: 2.9.1
5
5
  protocol: implementation
6
6
  adrRefs:
7
7
  - ADR-070
@@ -17,7 +17,7 @@ compatibility:
17
17
  - gemini-cli
18
18
  license: MIT
19
19
  metadata:
20
- version: 2.9.0
20
+ version: 2.9.1
21
21
  tier: core
22
22
  install: harness
23
23
  covers:
@@ -29,7 +29,7 @@ metadata:
29
29
  - packages/core/src/validation/protocols/cant/implementation.cant
30
30
  - packages/core/src/validation/protocols/protocols-markdown/implementation.md
31
31
  loomStage: implementation
32
- lastReviewed: 2026-10-28
32
+ lastReviewed: 2026-11-02
33
33
  stability: stable
34
34
  ---
35
35
 
@@ -223,7 +223,7 @@ Record it with `cleo docs add {{TASK_ID}} --content - --type note --slug {{TOPIC
223
223
 
224
224
  ## Acceptance Criteria Verification
225
225
 
226
- Record each criterion's changed artifacts and actual verification results. A merged PR closes the tasks its body names (`Closes:`) when `CI` is green on its exact head and an independent reviewer recorded `met` for each AC (`cleo review verdict`); the PR text alone never satisfies an AC (ADR-099). Hand-recorded atoms are for no-PR work: use `pr:<number>;files:<changed-path>` for implementation (`pr:<component>@<integration>` when your PR merged into an integration branch) and actual result atoms for test/review gates, with explicit `satisfies:T1234#AC1` links for canonical criteria. The PR must relate to the task; documentation-only changes cannot prove a code fix. Research and documentation tasks may use appropriately scoped documentary evidence: they owe `verification.requiredGatesByKind` (default: the required gates without `testsPassed`/`qaPassed`), but once their work touches any non-document path they owe the full code gates, whatever their kind or labels. Fetch the merge commit before claiming its artifact bytes were inspected. Criterion edits require fresh evidence. A completed child does not establish that its parent's independent criteria were met. `cleo verify <id> --all` sets every required gate at once and still requires `--evidence`; bare `--all` is rejected with `E_EVIDENCE_MISSING`. A failing `tool:<name>` reason names the resolved command and its source, so check that command before retrying. To adopt a native typecheck or lint run for `qaPassed` without re-running it, record one `qa-run:<receipt.json>` per check (`cleo verify --help` lists the receipt shape). A change with unit and e2e tests can record both runs in one write, `test-run:<vitest.json>;test-run:<playwright.json>` (Playwright `--reporter=json`): their passing test files cover the change together. Rust and Python suites record `test-run:` from a JUnit XML report (cargo nextest, pytest `--junitxml`) or libtest JSON lines (`cargo test -- --format json`).
226
+ Record each criterion's changed artifacts and actual verification results. A merged PR closes the tasks its body names (`Closes:`) when `CI` is green on its exact head and an independent reviewer recorded `met` for each AC (`cleo review verdict`); the PR text alone never satisfies an AC (ADR-099). Hand-recorded atoms are for no-PR work: use `pr:<number>;files:<changed-path>` for implementation (`pr:<component>@<integration>` when your PR merged into an integration branch) and actual result atoms for test/review gates, with explicit `satisfies:T1234#AC1` links for canonical criteria. The PR must relate to the task; documentation-only changes cannot prove a code fix. Research and documentation tasks may use appropriately scoped documentary evidence: they owe `verification.requiredGatesByKind` (default: the required gates without `testsPassed`/`qaPassed`), but once their work touches any non-document path they owe the full code gates, whatever their kind or labels. Fetch the merge commit before claiming its artifact bytes were inspected. Criterion edits require fresh evidence. A criterion of a code task that an owner decision or a stored document meets is covered with a receipt, never a waiver: `cleo verify <id> --criterion --evidence 'decision:<id>;satisfies:<id>#AC<n>'` binds only that criterion and sets no gate; a criterion naming a code path is refused. A completed child does not establish that its parent's independent criteria were met. `cleo verify <id> --all` sets every required gate at once and still requires `--evidence`; bare `--all` is rejected with `E_EVIDENCE_MISSING`. A failing `tool:<name>` reason names the resolved command and its source, so check that command before retrying. To adopt a native typecheck or lint run for `qaPassed` without re-running it, record one `qa-run:<receipt.json>` per check (`cleo verify --help` lists the receipt shape). A change with unit and e2e tests can record both runs in one write, `test-run:<vitest.json>;test-run:<playwright.json>` (Playwright `--reporter=json`): their passing test files cover the change together. Rust and Python suites record `test-run:` from a JUnit XML report (cargo nextest, pytest `--junitxml`) or libtest JSON lines (`cargo test -- --format json`).
227
227
 
228
228
 
229
229
  | Criterion | Status | Notes |
@@ -226,7 +226,7 @@
226
226
  },
227
227
  {
228
228
  "name": "ct-cleo",
229
- "version": "2.25.1",
229
+ "version": "2.25.5",
230
230
  "description": "CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.",
231
231
  "path": "skills/ct-cleo",
232
232
  "tier": 0,
@@ -566,7 +566,7 @@
566
566
  },
567
567
  {
568
568
  "name": "ct-dev-workflow",
569
- "version": "3.4.0",
569
+ "version": "3.4.2",
570
570
  "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.",
571
571
  "path": "skills/ct-dev-workflow",
572
572
  "tier": 0,
@@ -642,7 +642,7 @@
642
642
  },
643
643
  {
644
644
  "name": "ct-documentor",
645
- "version": "3.33.0",
645
+ "version": "3.38.0",
646
646
  "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.",
647
647
  "path": "skills/ct-documentor",
648
648
  "tier": 0,
@@ -1001,7 +1001,7 @@
1001
1001
  },
1002
1002
  {
1003
1003
  "name": "ct-orchestrator",
1004
- "version": "4.2.0",
1004
+ "version": "4.2.1",
1005
1005
  "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.",
1006
1006
  "path": "skills/ct-orchestrator",
1007
1007
  "tier": 0,
@@ -1167,7 +1167,7 @@
1167
1167
  },
1168
1168
  {
1169
1169
  "name": "ct-release-orchestrator",
1170
- "version": "3.5.0",
1170
+ "version": "3.7.0",
1171
1171
  "description": "Orchestrates CLEO releases. Default (T14102): cleo release cut {version} tags the newest main commit with green CI, and release.yml writes the CHANGELOG from changesets, publishes, and opens an auto-merging CHANGELOG + version PR; cleo release reconcile records provenance. The SPEC-T9345 4-verb pipeline (cleo release plan, cleo release open, PR + tag) stays one release as a fallback (T14114). 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.",
1172
1172
  "path": "skills/ct-release-orchestrator",
1173
1173
  "tier": 1,
@@ -1489,7 +1489,7 @@
1489
1489
  },
1490
1490
  {
1491
1491
  "name": "ct-task-executor",
1492
- "version": "2.9.0",
1492
+ "version": "2.9.1",
1493
1493
  "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.",
1494
1494
  "path": "skills/ct-task-executor",
1495
1495
  "tier": 0,