@cleocode/skills 2026.10.5 → 2026.10.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cleocode/skills",
-  "version": "2026.10.5",
+  "version": "2026.10.6",
   "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.7
+  version: 2.24.8
   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-04
+  lastReviewed: 2026-10-10
   stability: stable
 ---
 
@@ -176,9 +176,9 @@ and inspect it before explicit resume. Repeating the add is not a recovery step.
 The original two-second maintenance budget covers preparation through verification;
 timer expiry does not preempt synchronous SQLite work.
 
-Verify storage with `cleo docs fetch <slug>` and its JSON `data.bytesBase64` plus
-`data.metadata.sha256`. Keep canonical storage success, optional projection
-verification, and installed-provider workflow verification as separate evidence.
+Verify storage with `cleo docs fetch <slug>` and its JSON `data.content` (text docs,
+T13352; binary docs carry `data.bytesBase64`) plus `data.metadata.sha256`. Keep
+canonical storage success, optional projection verification, and installed-provider workflow verification as separate evidence.
 
 ## Acceptance input and historical evidence
 

package/skills/ct-codebase-mapper/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ct-codebase-mapper
-version: 2.1.2
+version: 2.2.0
 description: Orient in an unfamiliar or large codebase with CLEO's code-intelligence graph (cleo nexus) and project map (cleo map). Use before planning or editing unfamiliar code, for brownfield onboarding, to find what a change would break, or to map a project's structure, communities and execution flows. Triggers on "map the codebase", "understand this project", "what calls X", "what would break", "brownfield analysis", "project structure".
 protocol: null
 dependencies: []
@@ -17,13 +17,13 @@ triggers:
   - project structure
   - blast radius
 metadata:
-  version: 2.1.2
+  version: 2.2.0
   tier: on-demand
   install: harness
   covers:
     - packages/cleo/src/cli/commands/nexus.ts
     - packages/cleo/src/cli/commands/map.ts
-  lastReviewed: 2026-10-04
+  lastReviewed: 2026-10-10
   stability: stable
 ---
 
@@ -50,6 +50,19 @@ Queries auto-refresh up to 25 stale files; beyond that they warn
 rebuilds). An empty or stale index gives confident-looking but incomplete
 answers — say which you relied on.
 
+`assessment.referenceCount` is how many static references the graph could not
+resolve, so known callers are incomplete. Inspect them a page at a time:
+
+```bash
+cleo nexus status --references                                  # per-kind counts + first 20
+cleo nexus status --references --reference-kind unresolved --references-limit 500
+cleo nexus status --references --references-offset <referencesPage.nextOffset>
+```
+
+`referencesByKind` counts the whole list; `referencesPage` holds one page
+(max 5000). The full list is never returned in one call; it is named in
+`_withheld.references` with its size.
+
 Project-scoped queries use the declared portable project id. `--project-id`
 may name that id or a recorded, unambiguous legacy alias; an alias warns
 `W_NEXUS_LEGACY_PROJECT_ID`. A foreign or colliding id is refused: run the

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.17.5
+version: 3.17.6
 protocol: null
 dependencies:
   - ct-spec-writer
@@ -16,13 +16,13 @@ compatibility:
   - gemini-cli
 license: MIT
 metadata:
-  version: 3.17.5
+  version: 3.17.6
   tier: core
   install: harness
   covers:
     - packages/cleo/src/cli/commands/docs.ts
     - packages/contracts/src/docs-taxonomy.ts
-  lastReviewed: 2026-10-04
+  lastReviewed: 2026-10-10
   stability: stable
 ---
 
@@ -65,8 +65,9 @@ legacy discovery verbs only when `list` is insufficient.
 
 After `cleo docs add`, retain the canonical attachment ID and SHA-256, then use
 `cleo docs fetch <slug>` to verify the accepted bytes. For exact-byte checks,
-decode `data.bytesBase64` from the JSON response and compare its digest with
-`data.metadata.sha256`; rendered content can add a trailing newline.
+hash the UTF-8 bytes of `data.content` from the JSON response (text docs, T13352;
+binary docs carry `data.bytesBase64` to decode instead) and compare its digest
+with `data.metadata.sha256`; rendered content can add a trailing newline.
 
 The add result's `projection` reports captured project identity/root, coverage,
 diagnostics, the original deadline, and any durable `jobId` or verified receipt.

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

@@ -7,7 +7,7 @@ adrRefs:
   - ADR-063
   - ADR-065
 metadata:
-  version: 3.2.0
+  version: 3.2.1
   tier: on-demand
   install: harness
   covers:
@@ -15,7 +15,7 @@ metadata:
     - packages/core/src/validation/protocols/protocols-markdown/release.md
     - packages/cleo/src/cli/commands/release.ts
   loomStage: release
-  lastReviewed: 2026-10-04
+  lastReviewed: 2026-10-09
   stability: stable
 ---
 
@@ -33,7 +33,7 @@ Owns the canonical 4-verb release pipeline established by SPEC-T9345 and finalis
 
 | Step | Verb / Workflow | Owns transition | Notes |
 |-----:|------------------|------------------|-------|
-| 1 | `cleo release plan <ver> --epic <id>` | _(none)_ → `planned` | Builds the Release Plan envelope; auto-writes `CHANGELOG.md` (T10105 closes the silent-skip gap) |
+| 1 | `cleo release plan <ver> --epic <id>` | _(none)_ → `planned` | Builds the Release Plan envelope; auto-writes `CHANGELOG.md` (T10105 closes the silent-skip gap). stdout is the one envelope, and the readiness report goes to stderr (T13322). A `--tasks` plan records `epicId: null`, and each task keeps its own `epicAncestor` (T13323) |
 | 2 | `cleo release open <ver>` | `planned` → `pr-opened` | Dispatches `release-prepare.yml` with the plan's sha256 once the plan is verified on the default branch, plus the verified preflight skips; the workflow cuts the branch + opens the PR |
 | 3 | _(GHA)_ `release-prepare.yml` → PR merge | `pr-opened` → `pr-merged` | Owned by CI; verify via `cleo release pr-status <ver>` |
 | 4 | `git tag -a v<ver> -m "Release v<ver>" && git push origin v<ver>` | `pr-merged` → `tag-pushed` | Explicit tag after the release PR merges — `auto-tag-on-release-merge.yml` is retired (T10434, ADR-087); the tag push triggers `release.yml` |

package/skills/manifest.json

@@ -226,7 +226,7 @@
     },
     {
       "name": "ct-cleo",
-      "version": "2.24.7",
+      "version": "2.24.8",
       "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,
@@ -302,7 +302,7 @@
     },
     {
       "name": "ct-codebase-mapper",
-      "version": "2.1.2",
+      "version": "2.2.0",
       "description": "Orient in an unfamiliar or large codebase with CLEO's code-intelligence graph (cleo nexus) and project map (cleo map). Use before planning or editing unfamiliar code, for brownfield onboarding, to find what a change would break, or to map a project's structure, communities and execution flows. Triggers on \"map the codebase\", \"understand this project\", \"what calls X\", \"what would break\", \"brownfield analysis\", \"project structure\".",
       "path": "skills/ct-codebase-mapper",
       "tier": 1,
@@ -642,7 +642,7 @@
     },
     {
       "name": "ct-documentor",
-      "version": "3.17.5",
+      "version": "3.17.6",
       "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,
@@ -1150,7 +1150,7 @@
     },
     {
       "name": "ct-release-orchestrator",
-      "version": "3.2.0",
+      "version": "3.2.1",
       "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,